Windows 11 May update installation problems brought Patch Tuesday to a grinding halt for thousands of users and IT administrators worldwide in May 2026. The culprit was KB5089549, Microsoft’s monthly security update for Windows 11 versions 24H2 and 25H2, which repeatedly failed mid-installation and rolled back — leaving machines unpatched and admins scrambling for answers. The good news: Microsoft has now confirmed the root cause and released a verified fix.
What Is KB5089549 and Why Did It Matter?
KB5089549 is Microsoft’s May 12, 2026 cumulative security update, targeting OS builds 26200.8457 and 26100.8457. It bundled critical security patches, quality improvements, and platform fixes intended for all Windows 11 devices. Because it carried security-critical payloads, leaving it uninstalled meant exposed endpoints — a serious concern for both home users and enterprise fleets alike.
Under normal circumstances the update would download, stage its files, reboot, apply changes to the system partition, and return to Windows. Instead, a significant proportion of machines halted at roughly 35% of the installation phase and rolled back automatically, generating a pair of error codes that quickly became familiar to IT teams everywhere.
The Root Cause of May Update Install Failures
The KB5089549 install error trace pointed consistently to error code 0x800f0922, and in some domain environments to 0x80240009. Microsoft officially confirmed the trigger: the EFI System Partition (ESP) on affected devices had less than 10 MB of free space remaining. The update’s staging process needs temporary headroom on the ESP to write boot-critical files during the transition. When that space doesn’t exist, the operation fails cleanly and reverts — which is why most users saw an automatic rollback rather than a corrupted system.
- Error 0x800f0922 — insufficient EFI System Partition space (primary cause)
- Error 0x80240009 — Windows Update download timeout, seen mainly on Windows Server 2016/2019/2022 domain controllers
- Slow internet / network degradation — a secondary complaint reported on Windows 11 25H2 after successfully installing the update
- Unbootable state (rare) — a small number of users on the Microsoft Tech Community reported a failure to boot after the update, requiring recovery mode
The ESP space issue is not new — it has surfaced with previous Patch Tuesdays — but the May 2026 update needed slightly more scratch space than earlier cumulative updates, exposing devices that had just enough room for previous patches but not this one.
Which Devices Were Affected by KB5089549 Install Errors?
Not every Windows 11 machine ran into KB5089549 install errors. The failure pattern was narrowed to specific hardware and configuration profiles:
- Devices where the EFI System Partition was created at the Windows default size of 100 MB and had accumulated language packs, UEFI firmware blobs, or BitLocker metadata over time
- OEM systems — particularly older laptops from major manufacturers — where the ESP was provisioned smaller than Microsoft’s recommended minimum
- Machines that had previously received large firmware updates delivered through Windows Update, which deposit files directly on the ESP
- Windows Server domain controllers running 2016, 2019, and 2022 encountering the 0x80240009 download timeout variant
Consumer PCs purchased in the last two to three years with a freshly-provisioned 260 MB ESP were largely unaffected, which explains why the failure rate felt inconsistent and hard to predict before the root cause was pinpointed.
Microsoft’s Official Fix: KB5089573 Preview Update
Microsoft resolved the Windows 11 update fix on May 26, 2026, releasing KB5089573 — a preview cumulative update targeting OS builds 26200.8524 and 26100.8524. According to the official Microsoft support article for KB5089573, this update directly addresses the 0x800f0922 install failure by adjusting how the staging process interacts with the ESP and by padding ESP registry values to create adequate headroom.
The full, non-preview version of this fix is scheduled for inclusion in the June 2026 Patch Tuesday rollout, meaning organisations that wait for the standard monthly cadence will receive it automatically. Those who cannot afford to leave their fleet unpatched until then should deploy KB5089573 proactively.
How to Deploy the Windows 11 Update Fix Safely
Applying the resolution is straightforward, but the approach differs depending on whether your device is already failing or just at risk. Follow these steps:
Option 1 — Install KB5089573 via Windows Update (Recommended)
- Open Settings → Windows Update.
- Click Check for updates — KB5089573 should appear as an available preview update.
- Click Download and install and allow the device to restart.
- After reboot, return to Windows Update and install KB5089549 if it is still listed as pending — it should now complete without error.
Option 2 — Manual Catalogue Download
- Visit the Microsoft Update Catalogue and search for KB5089573.
- Download the correct .msu file for your architecture (x64 or ARM64).
- Run the installer with administrator rights and restart when prompted.
- Re-run Windows Update to confirm KB5089549 is now installed.
Option 3 — Registry ESP Padding (Manual Workaround)
For IT administrators needing to unblock specific machines before the cumulative update can be staged, Microsoft published a registry-based mitigation that instructs the update engine to reclaim ESP space. Details of the exact registry path were circulated in the Neowin coverage of the confirmed Windows Update bug. Apply with caution on production machines and test on a pilot group first.
What IT Admins Should Do Right Now
If you manage Windows 11 May update installation problems across a fleet, the priority order is clear:
- Audit ESP free space on all managed endpoints using a script that reads partition sizes via
Get-Partitionin PowerShell or via SCCM/Intune compliance policies. - Prioritise KB5089573 deployment through WSUS, Intune, or your RMM tool — approve the preview update immediately rather than waiting for June.
- Check domain controllers separately — the 0x80240009 error on Server 2016/2019/2022 may require a re-run of Windows Update rather than the ESP fix, but confirm by reviewing event logs first.
- Document any unbootable machines and follow Microsoft’s recovery guidance (boot to Windows Recovery Environment → Startup Repair) before applying patches.
- Set a compliance deadline for June Patch Tuesday to ensure KB5089549 is fully deployed fleet-wide once the fix ships in the main channel.
For our detailed walkthrough of the 0x800f0922 error specifically — including a step-by-step registry fix and manual install guide — see our dedicated article on fixing the Windows 11 update 0x800f0922 error on KB5089549.
Will This Happen Again? Lessons from May 2026
The May 2026 episode is a useful reminder that the EFI System Partition is a finite resource that accumulates data quietly over a device’s lifetime. Microsoft has acknowledged the pattern and the KB5089573 fix includes changes intended to make future updates more resilient to low-ESP conditions. However, the underlying hardware limitation — a 100 MB partition that OEMs have been shipping for over a decade — will not disappear overnight.
Proactive ESP maintenance is the long-term answer. Running cleanmgr or using third-party partition tools to trim stale boot files reduces the risk of hitting the 10 MB threshold with a future update. Microsoft’s own guidance recommends a minimum of 260 MB for the ESP on new deployments, a standard that is already built into Windows 11’s out-of-box setup on supported hardware.
If your current Windows 11 licence is due for a refresh — or you are migrating a machine from Windows 10 ahead of the October 2026 end-of-support deadline — you can pick up a genuine Windows 11 Pro Retail key from Shop Key Online from just €17.95, with instant email delivery and free lifetime activation support included.
FAQ: Windows 11 May Update Installation Problems
What error code do Windows 11 May update installation problems produce?
The most common error is 0x800f0922, caused by insufficient free space on the EFI System Partition. A secondary error, 0x80240009, has been reported mainly on Windows Server domain controllers and is related to download timeout changes introduced earlier in 2026. Both codes cause the update to roll back automatically, leaving the system intact but unpatched.
Has Microsoft officially confirmed the KB5089549 install error?
Yes. Microsoft confirmed the issue publicly and documented it on the support page for KB5089549 (OS Builds 26200.8457 and 26100.8457). The company identified low EFI System Partition space as the root cause and released preview update KB5089573 on May 26, 2026 as the resolution, with the permanent fix entering the standard channel via June 2026 Patch Tuesday.
Is my PC safe if KB5089549 failed to install?
A failed install means your system reverted to its previous state — it did not partially apply the patch. Your PC is not corrupted, but it remains without the May 2026 security updates. You should prioritise deploying KB5089573 (which carries the same security payloads) as soon as possible to close the vulnerability window. Running without a current cumulative update leaves known security gaps unaddressed.
Do I need to reinstall Windows 11 to fix the May update install failures?
No. A full reinstall is not required and should be a last resort. The fix is to install KB5089573 via Windows Update or the Microsoft Update Catalogue, which resolves the ESP space issue and allows KB5089549’s security content to install correctly. Only the rare unbootable-state cases require Windows Recovery Environment intervention, and even those do not typically need a full OS reinstall.
Will the Windows 11 update fix arrive automatically?
The permanent fix is built into the June 2026 Patch Tuesday cumulative update, which will reach all devices through the standard Windows Update channel. If your device is set to receive updates automatically and you do not manually defer them, the June update will resolve the installation failure without any manual intervention. The May 26 KB5089573 preview is optional but recommended for those who want the fix immediately.
How can I check if my EFI System Partition has enough free space?
Open PowerShell as administrator and run Get-Partition | Where-Object {$_.GptType -eq '{c12a7328-f81f-11d2-ba4b-00a0c93ec93b}'} | Select-Object -ExpandProperty Size to identify the ESP. Then use Disk Management or a tool like MiniTool Partition Wizard to check free space. If the partition has less than 10 MB free, clear stale boot entries or firmware blobs before attempting to re-run Windows Update.
