Microsoft fixes KB5089549 Windows security update install issues

MICROSOFT FIXES KB5089549 WINDOWS SECURITY UPDATE INSTALL ISSUES

OverviewMicrosoft has addressed a previously reported problem that prevented the May 2026 Windows 11 security update from installing on certain devices. The issue manifested as installation failures and 0x800f0922 errors, with many systems rolling back the update during the reboot phase. The root cause was traced to insufficient free space on the EFI System Partition (ESP). Devices with very limited ESP space—typically 10 MB or less—could experience the reboot failure around 35–36% completion, resulting in the familiar rollback message and accompanying log entries such as SpaceCheck and ServicingBootFiles failed.

What happened and why

• The failure occurred during the deployment of the May 2026 security update for Windows 11, identified as KB5089549.
• The limiting factor was free space on the EFI System Partition (ESP), a critical but small partition used during the boot process and servicing operations.
• On affected machines, the update would begin, proceed through initial phases, and stall at the reboot, triggering a rollback with a message indicating that “Something didn't go as planned. Undoing changes.”
• Logs associated with the rollback commonly referenced SpaceCheck and ServicingBootFiles failed, pointing to inadequate ESP space as the bottleneck.
• Microsoft’s guidance highlighted that devices with 10 MB or less of free ESP space were particularly vulnerable to this behavior.

Scope and symptoms

• The primary symptom was a failed installation that rolled back, leaving the system with no update applied.
• Users might see a rollback screen and a notification that the process could not complete.
• Logs in the update history or event viewer could show SpaceCheck failures or ServicingBootFiles errors, which helped identify the ESP space issue as the cause.
• The problem was not caused by a faulty update package alone, but by the combination of the update’s requirements and the constrained ESP space on certain devices.

How the issue was resolved

• A resolution was introduced with the release of the KB5089573 preview cumulative update, which included the necessary fixes for the ESP space constraint and related reboot failures.
• Microsoft subsequently indicated that the June Patch Tuesday updates would include the fix for all users who install the latest cumulative update, ensuring broad availability of the remediation.
• For devices already running the May 26, 2026 update (KB5089573) or newer, a workaround was not required to complete installation or continue receiving protection.
• The May 26, 2026 update (KB5089573) introduced a broader set of changes, delivering improvements to performance and reliability alongside the specific fix for the ESP space issue.

What to expect after the fix

• Systems that install KB5089573 or later should no longer encounter the 0x800f0922 error tied to ESP space during the May 2026 update process.
• The update experience improves, particularly for devices with previously constrained ESP space, as the known issue has been addressed in the released updates.
• Enterprise administrators can anticipate a more straightforward deployment path, with less need for remediation workarounds once the updated cumulative update is applied.

Interim workarounds and deployment options

• Known Issue Rollback (KIR) is a Windows feature that allows reversing buggy updates pushed via Windows Update. This option provides a way to protect systems by rolling back problematic updates while continuing to maintain security protections.
• In enterprise environments, administrators can configure Known Issue Rollback via Group Policy to manage deployments and reversals of specific updates as needed.
• It is important to note that, with the availability of the resolved update, using a rollback is typically unnecessary for devices already receiving the corrected releases, but it remains a tool for environments where updates are delayed or managed differently.

Context and related developments

• Earlier in the month, Microsoft acknowledged related issues tied to April 2026 security updates that affected certain backup applications using a vulnerable driver, and subsequently issued fixes to address those compatibility concerns.
• Additional measures around Windows Autopatch included fixes for scenarios where driver updates restricted by administrative policies could be deployed on Autopatch-managed devices, particularly across the European Union.
• A broader set of changes accompanying the May 26 release, including performance and reliability improvements, underscored Microsoft’s ongoing effort to stabilize Windows 11 update experiences across versions 25H2 and 24H2.

Enterprise guidance and deployment notes

• For IT teams, the primary takeaway is that installing the latest available cumulative update (KB5089573 or later) should mitigate the ESP space-related installation failures encountered with KB5089549.
• If an environment relies on delaying updates or testing before deployment, monitoring for the KB5089573 release and planning upgrades accordingly will reduce exposure to the ESP-related rollback issue.
• Known Issue Rollback and Group Policy deployment of known issue policies remain viable tools for managing updates in complex or restricted networks, ensuring devices remain protected while avoiding disruption from faulty updates.

Closing summaryThe May 2026 Windows 11 security update faced a notable installation hurdle tied to limited ESP space on some devices. With the release of the corresponding fix in the KB5089573 family and related June updates, affected systems should be able to complete installation without the prior rollback behavior. This remediation aligns with Microsoft’s broader objective of delivering stable, reliable security updates while offering administrators clear pathways to manage deployments across diverse environments.