Drooid Logo
Back to story perspectives

Full Breakdown

Microsoft Issues Emergency Patch for Windows 11 May 2026 Update Failure

5/17/2026, 3:55:58 AM

Failed KB5089549 Installation on Low-Space Devices

Microsoft released the Windows 11 May 2026 security update (KB5089549) on May 12. Within three days the company warned that the update may fail on PCs whose EFI System Partition (ESP) lacks sufficient free space. The error typically appears at 35–36 % of the restart, showing “Something didn’t go as planned. Undoing changes,” then rolling back or preventing boot.

Technical Cause and Impact

The ESP, a hidden 100 MB partition that stores boot files, can shrink below 10 MB after firmware updates, OEM files, or multiple OS installations. Windows logs “SpaceCheck: Insufficient free space ServicingBootFiles failed. Error = 0x70.” Reported error codes include 0x800f0922, 0x80240069, 0x80240031, and 0x70. Affected PCs may enter boot loops, run slower, or become unbootable. The update also provides Secure Boot certificates required before the June 2026 deadline.

Conflicting Reports & Gaps

Source 1 attributes the installation failure primarily to limited memory availability, while Source 2 identifies insufficient EFI partition space as the direct cause. No source clarifies which factor predominates, leaving uncertainty about the root trigger.

Official Response

Microsoft confirmed the storage-related issue and began rolling out an emergency server-side patch. It recommends the Known Issue Rollback (KIR) mechanism, which automatically reverts the update on affected PCs, and advises multiple restarts to speed the fix. Microsoft added that the resolution has already propagated to consumer and non-managed business devices and that no further bugs have been identified.

User Feedback & Criticism

Users reported restart cycles, boot loops, and the Windows troubleshooter could not detect the problem. One user said the update “forces me to retry the installation,” while another noted it appeared to install fully before the system “found a problem and not to worry it would try to recover/roll back the update.” These reports highlight frustration with the lack of a simple manual fix.

Verbatim Quotes

  • “This issue is mitigated using Known Issue Rollback (KIR),” — Microsoft, Official Statement
  • “The resolution has already propagated automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply more quickly.” — Microsoft, Official Statement
  • “Something didn’t go as planned. Undoing changes.” — Windows 11 UI message

Next Steps

Microsoft’s emergency update is being pushed to all Windows 11 devices via Windows Update. Users should verify ESP free space with PowerShell (`Get-Partition | Where-Object GptType -eq 'c12a7328-f81f-11d2-ba4b-00a0c93ec93b' | Get-Volume | Format-List Size, SizeRemaining`). If free space is below 10 MB, expanding the ESP via the registry is optional, but the server-side patch should resolve the issue without manual changes. Monitor update status and restart as recommended until the Secure Boot deadline passes.