This is due to a non-essential piece of Atlas having an issue with the new ASP.NET Integration mode. This is fixed in a subsequent release by removing the module from the Atlas web.config file (you probably got it when you migrated the Atlas configuration, bringing this module over from the httpModules...