"This issue affects devices with limited free space on the EFI System Partition (ESP), especially when the device has 10 MB or less space available," Microsoft said.
How the installation fails: error codes, rollback, and logs
Microsoft confirmed that the May 2026 Windows 11 security update (KB5089549) can fail to install on some systems, producing 0x800f0922 errors and an automatic rollback. On affected devices the installation can "proceed through the initial phases but fail during the reboot phase at approximately 35–36% completion," the company said. When the update rolls back users see the message "Something didn't go as planned. Undoing changes."
Microsoft pointed to log entries that operators may find on impacted machines, including "SpaceCheck: Insufficient free space", "ServicingBootFiles failed. Error = 0x70", and "SpaceCheck: <value> used by third-party/OEM files outside of Microsoft boot directories." Those entries identify the installation blocker in machine logs.
Root cause: insufficient free space on the EFI System Partition (ESP)
The company attributes the problem to limited free space on the EFI System Partition (ESP). Microsoft specifically flagged devices with 10 MB or less available on the ESP as being especially susceptible. Because the update fails during the reboot phase, affected systems do not complete the cumulative update and the installer triggers the undo/rollback sequence.
Mitigation: Known Issue Rollback and Group Policy steps
While Microsoft continues working to resolve the problem, it advised affected customers to mitigate the issue using the Known Issue Rollback, a Windows feature that reverses buggy updates pushed via Windows Update. For enterprise-managed environments the company provided a manual path: administrators can install and configure a Group Policy to mitigate the failure.
Microsoft instructed administrators directly: "You will need to install and configure the Group Policy for your version of Windows to resolve this issue," adding that "You will also need to restart your device(s) to apply the group policy setting. Note that the Group Policy will temporarily disable the change causing this issue." Microsoft points admins to its support website for further guidance on deploying and configuring Known Issue Rollback group policies.
How enterprise-managed environments should respond
In environments where IT controls Windows updates, the company’s guidance is unambiguous: apply the Known Issue Rollback group policy appropriate to your Windows version and restart devices to ensure the policy takes effect. The Group Policy acts as a temporary disablement of the change producing the install failures, allowing managed fleets to avoid interrupted updates while Microsoft works on a permanent resolution.
Related recent Windows update problems
KB5089549 was released "last week," Microsoft said, as part of a larger roll of dozens of bug fixes, security patches, and improvements. That release also included a fix for a separate known issue that caused some Windows 11 systems to boot into BitLocker recovery after installing April 2026 security updates. Earlier in May the company also addressed a Windows Autopatch bug that caused driver updates restricted by administrative policies to be deployed on some Autopatch-managed Windows devices across the European Union, and confirmed that the April 2026 security updates were causing failures in third-party backup applications that used a vulnerable driver.
What this means for technologists, enterprises, and end users
- Technologists and security teams: look for the 0x800f0922 error and the cited log entries ("SpaceCheck: Insufficient free space", "ServicingBootFiles failed. Error = 0x70") during troubleshooting, and confirm whether ESP free space is 10 MB or less before proceeding with local remediation.
- Enterprise IT and procurement leaders: deploy the Known Issue Rollback Group Policy recommended by Microsoft for your Windows version and schedule the required device restarts to apply the setting across managed fleets.
- End users and small IT shops: expect automatic rollback messages ("Undoing changes") on affected installs and follow Microsoft’s guidance or contact your IT support if updates repeatedly fail; Microsoft’s support site contains the step-by-step Known Issue Rollback deployment guidance referenced by the company.
Microsoft is still working to resolve the root problem while offering a temporary rollback solution and a Group Policy mitigant for managed environments. For operators and administrators the immediate task is clear: monitor logs for the specified failure messages, confirm ESP free space conditions highlighted by Microsoft, and apply the Known Issue Rollback or Group Policy as recommended until a permanent fix is issued.
