Windows 11 KB5089573 Install Failure Fix June 2026 Patch

What is KB5089573?

KB5089573 is the Windows 11 cumulative update Microsoft is shipping as part of the June 9, 2026 Patch Tuesday release. It supersedes the original out-of-band KB5089573 OOB that rolled to a smaller ring on May 26 and, critically, ships the corrected servicing-stack code path that finally resolves the EFI System Partition (ESP) full failures users hit when KB5089549 first deployed in May 2026. Devices receive winver build 26100.4789 (24H2) or 26200.2347 (25H2) after a successful install.

Despite the fix, the update still requires roughly 6–8 MB of free space inside the ESP to write its smaller bootloader payload, and devices that never freed the partition after KB5089549 rolled back will see KB5089573 itself fail with 0x800f0922, 0x80073712, or 0x80240069. The patch also pulls a paired Known Issue Rollback (KIR) policy that suppresses the original failing code path on devices that pulled KB5089549 but rolled back — that KIR is distributed gradually via Microsoft's CDN over 3–10 days, so retrying immediately after the patch lands sometimes succeeds and sometimes does not.

When does it occur?

• Windows Update shows KB5089573 as "Download pending" or stalls at 0% for over 30 minutes
• Install reaches 35–36% during the post-reboot servicing screen, then rolls back with 0x800f0922
• wusa.exe install returns ERROR_INSTALL_FAILURE 0x80073712 or ERROR_NOT_FOUND 0x80070490
• winver still reports build 26100.4750 or lower after the install supposedly completed
• The device is on a 100 MB ESP with Winre.wim consuming most of the partition
• WSUS or Intune push the cumulative without the matching SSU KB5089569, breaking the staging step

Common causes

• The ESP still has under 8 MB free because KB5089549 left half-staged bootloader files behind
• The KIR policy file Windows.Servicing.KB5089573.KIR.xml has not yet propagated to the device
• The matching servicing stack update KB5089569 is missing — required on WSUS-managed devices
• C:\Windows\SoftwareDistribution\Download\ contains a corrupted package from a prior KB5089549 retry
• BitLocker is in an inconsistent suspend/resume state, blocking BCD regeneration on first boot
• A third-party EFI loader (rEFInd, Clover, Ubuntu shim, GRUB) is still occupying ESP space
• Group Policy on managed laptops is blocking the KIR XML from being written to the Machine policy store

Step-by-step fixes

1. Confirm the install actually failed. Open elevated PowerShell and run:

   Get-HotFix | Where-Object { $_.HotFixID -eq 'KB5089573' }
   winver

If Get-HotFix returns a row and winver shows 26100.4789 (24H2) or 26200.2347 (25H2), the patch is in — Windows Update is just showing stale status. Run wuauclt /resetauthorization /detectnow to refresh.

1. Free space inside the ESP before retrying. From elevated CMD:

   diskpart
   list disk
   select disk 0
   list partition
   select partition 1
   assign letter=S
   exit
   dir S:\

If "bytes free" is under 8 MB, delete safe regeneratable files:

   del /F /Q S:\EFI\Microsoft\Boot\Fonts\*.ttf
   del /F /Q S:\EFI\Microsoft\Boot\*.bak
   del /F /Q S:\EFI\Microsoft\Boot\BCD.LOG*
   del /F /Q S:\EFI\Microsoft\Recovery\BCD.LOG*

Windows regenerates these on next boot. Expect 6–15 MB reclaimed.

1. Reset Windows Update components to wipe leftover KB5089549 stage data:

   net stop wuauserv && net stop cryptSvc && net stop bits && net stop msiserver
   ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
   ren C:\Windows\System32\catroot2 catroot2.old
   net start wuauserv && net start cryptSvc && net start bits && net start msiserver

Then wuauclt /resetauthorization /detectnow and trigger a new scan from Settings.

1. Install the matching SSU first if you are on WSUS or Intune. Approve and stage KB5089569 (2026-06 Servicing Stack Update for Windows 11) before KB5089573 — without it, the cumulative will never finish the post-reboot stage. Verify with: Get-HotFix | Where-Object { $_.HotFixID -eq 'KB5089569' }.

1. Manually install the KB5089573 MSU from the Microsoft Update Catalog if Windows Update keeps stalling. Visit catalog.update.microsoft.com, search "KB5089573", pick 2026-06 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (or 25H2 / ARM64 variant), then run:

   wusa.exe C:\Users\<you>\Downloads\windows11.0-kb5089573-x64.msu /quiet /norestart /log:C:\kb5089573.log
   shutdown /r /t 60

Inspect C:\kb5089573.log if it fails — look for CBS_E_INSTALLERS_FAILED (ESP full) or 0x80073712 (component store corruption).

1. Force the KIR policy instead of waiting for gradual rollout. From elevated PowerShell:

   gpupdate /target:computer /force
   wuauclt /resetauthorization /detectnow
   UsoClient StartInteractiveScan

Then verify the Machine policy was updated within the last 5 minutes: Get-Item C:\Windows\System32\GroupPolicy\Machine\Registry.pol | Select-Object LastWriteTime.

1. Suspend BitLocker for one reboot before retrying so the firmware does not demand the 48-digit recovery key after BCD regeneration: manage-bde -protectors -disable C: -RebootCount 1. The protector re-enables automatically after the next reboot.

1. Remove orphaned third-party EFI loaders if you no longer dual-boot. Run bcdedit /enum firmware, identify entries for ubuntu, refind, clover, etc., delete them with bcdedit /delete {guid}, then remove their folders from S:\EFI\ after a system image backup. This often reclaims 2–6 MB on long-lived dual-boot installs.

If it still doesn't work

If KB5089573 keeps failing after ESP cleanup, the component store is the next suspect. Run DISM /Online /Cleanup-Image /AnalyzeComponentStore, then DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase, and finish with sfc /scannow. If DISM returns 0x800f081f, mount the latest Windows 11 24H2 ISO from software-download.microsoft.com and repair against it: DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:D:\sources\install.wim:1 /LimitAccess.

Enterprise admins should confirm both KB5089569 (SSU) and KB5089573 (LCU) are approved together in WSUS — missing the SSU is the single biggest cause of repeat rollback in managed environments. As a last resort, an in-place repair install via setup.exe /auto upgrade from the mounted ISO will rewrite the servicing stack while preserving installed apps and files.