Has anyone run into widespread September update failures on Windows 11 25H2? The August update installed normally, but every machine in the fleet now fails the September update, including the later out-of-band release. The CBS logs mention a WLAN-AutoConfig manifest failure, although that may be a symptom rather than the actual cause. The installation reaches the reboot stage, progresses partway, and then rolls back. I know error 0x800f0922 is often associated with an undersized EFI system partition, and I have already tried expanding that partition. I have also run DISM using installation-media sources, reset the Windows Update cache, and attempted an in-place upgrade. I am trying to determine whether this is a faulty update, a servicing-stack or component-store problem, or something common across the fleet before resorting to reimaging.
3 Answers
Before focusing too heavily on the WLAN-AutoConfig manifest entry, verify the exact operating-system version and build involved. The issue is affecting Windows 11 25H2 across the fleet, and the repeated failure of both the regular and out-of-band updates suggests the CBS message may be a secondary symptom rather than the root cause.
There has been a noticeable increase in failed updates recently, and the September releases seem especially problematic. Since the failure is happening across the entire fleet and the machines roll back after reboot, this may be a broader servicing issue rather than one corrupted installation.
That is what I am trying to establish. I have not found much about this exact failure pattern, so I am unsure whether the update is bad or whether something common in our servicing environment is being exposed by it.
Since the update reaches the reboot phase and then reverses the changes, check the system and default user profiles for signs of missing user.dat files. That can sometimes help identify a profile or servicing problem connected to the rollback.
It does ask for the reboot, reaches a certain percentage, and then rolls back. Can you explain what specific files or paths I should check and how they would relate to this error?
The affected systems are all running Windows 11 25H2. I have updated the details with the partition change, DISM repairs, update-cache reset, installation-media sources, and in-place upgrade attempts I have already tried.