Windows 11 24H2 May 2026 Update Error 0x800f0922 & 0x80073712 Fix

What are Windows 11 24H2 May 2026 update errors 0x800f0922 and 0x80073712?

The Windows 11 May 2026 Patch Tuesday rollup (KB5089549, released May 13, 2026) for versions 24H2 and 25H2 is failing on a significant minority of PCs with one of two error codes that share a root cause in the component store:

• 0x800f0922 (CBS_E_INSTALLERS_FAILED) — a generic installer-failure code that, in May 2026, almost always means either a full EFI System Partition or a corrupt servicing stack. Microsoft confirmed the EFI-partition variant on May 16, 2026.
• 0x80073712 (ERROR_SXS_COMPONENT_STORE_CORRUPT) — Component-Based Servicing manifest is missing or hash-mismatched, often because a prior cumulative update was interrupted by a power loss or BSOD.

Both errors abort the install during the post-download reboot at 35-40% progress with *"We couldn't complete the updates. Undoing changes."* The fix sequence below is the order that actually works — most online guides list DISM and SFC out of order, or skip the critical CheckHealth/ScanHealth step before RestoreHealth, which is why those guides fail.

When does it occur?

• During the reboot phase of KB5089549 install on Windows 11 24H2 or 25H2
• On systems with under 100 MB on the EFI System Partition (ESP)
• After a prior cumulative update was interrupted (power loss, BSOD, hard reboot)
• On machines that have been imaged or upgraded across multiple feature updates
• When the SoftwareDistribution folder contains partial or corrupt downloads
• On Hyper-V hosts where the Servicing Stack Update (SSU) is pinned to an older build

Common causes

• Full or near-full EFI System Partition — KB5089549 needs 10 MB free; OEM ESPs from 2017 and earlier often have under 5 MB
• Corrupt component store (C:\Windows\WinSxS) — missing or hash-mismatched manifests trigger 0x80073712 directly
• Stale SoftwareDistribution cache — a partially downloaded payload from a prior failed install poisons retries
• BITS or Windows Update service in a stuck state after a prior cancelled install
• Pending reboot from an older update still queued in the servicing stack
• Third-party security software (especially endpoint EDR) holding Trustedinstaller.exe handles
• Missing or outdated Servicing Stack Update (SSU) — the May 2026 cycle requires SSU build 26100.4500 or later

Step-by-step fixes

1. Capture the exact failure context before you change anything — Open an elevated PowerShell and run:

   Get-WinEvent -LogName Setup -MaxEvents 30 | Format-List TimeCreated,Id,Message
   Get-Content C:\Windows\Logs\CBS\CBS.log | Select-String "0x800f0922","0x80073712" | Select-Object -Last 20

If you see MoSetup entries citing SYSTEM partition near the failure, it's the ESP variant — jump to step 2. If you see CBS Failed entries referencing WinSxS or Package_, you have component-store corruption — start at step 4.

1. Free space on the EFI System Partition if relevant — In elevated PowerShell:

   mountvol S: /S
   Get-PSDrive S | Select-Object Used,Free
   Remove-Item "S:\EFI\Microsoft\Boot\Fonts\*.ttf" -Force
   Remove-Item "S:\EFI\Microsoft\Boot\*.bak" -Force
   Remove-Item "S:\EFI\Microsoft\Boot\BCD.LOG*" -Force
   mountvol S: /D

You need at least 10 MB free on S: after this. If still below 10 MB, see our dedicated [KB5089549 EFI partition guide](/en/errors/windows-11-kb5089549-install-error-0x800f0922).

1. Reset the Windows Update components in the correct order — From elevated PowerShell, run this block as a single sequence:

   Stop-Service -Name wuauserv,cryptSvc,bits,msiserver -Force
   Rename-Item C:\Windows\SoftwareDistribution SoftwareDistribution.old -ErrorAction SilentlyContinue
   Rename-Item C:\Windows\System32\catroot2 catroot2.old -ErrorAction SilentlyContinue
   Start-Service -Name wuauserv,cryptSvc,bits,msiserver

This clears the poisoned download cache. Order matters: stop all four services *before* renaming, otherwise the rename will fail silently.

1. Run the component-store repair sequence — in this exact order. This is where 90% of online guides go wrong. Run each as a separate command in elevated PowerShell and wait for completion before the next:

   DISM /Online /Cleanup-Image /CheckHealth
   DISM /Online /Cleanup-Image /ScanHealth
   DISM /Online /Cleanup-Image /RestoreHealth
   sfc /scannow

CheckHealth reads the flags, ScanHealth performs the full integrity check (5-15 minutes), RestoreHealth pulls fresh manifests from Windows Update or your side-by-side source (15-45 minutes). sfc /scannow runs last because it depends on a healthy component store to do its repairs. Reversing the order makes SFC fail with "Windows Resource Protection could not perform the requested operation."

1. Update the Servicing Stack Update (SSU) manually — Browse to catalog.update.microsoft.com, search "Servicing Stack Update Windows 11 24H2 May 2026", download the .msu matching your architecture (x64 or ARM64), and double-click to install. Reboot. The SSU must be on build 26100.4500 or later for KB5089549 to install. This single step resolves a large share of 0x80073712 failures.

1. Clean up superseded components after repair — Once DISM/SFC report clean, run:

   DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase

This permanently removes the older versions of every component superseded by previous cumulative updates (10-60 minutes). It frees 2-10 GB and ensures the May 2026 installer doesn't trip over a stale manifest pointer.

1. Temporarily disable third-party security software — Endpoint protection (CrowdStrike, SentinelOne, Defender for Endpoint, Sophos, Bitdefender) routinely holds open handles on TrustedInstaller.exe and wuaueng.dll, blocking the install. Open the security agent's console, set protection to Manual / Disabled / Snooze for 1 hour, install the update, then re-enable. Do not uninstall — the install will succeed without you needing to.

1. Re-trigger the update and verify the build — Settings → Windows Update → Check for updates → Download & install. The install should now pass the 36% reboot point and complete. Verify with winver — you should see OS Build 26100.4751 (24H2) or OS Build 26200.2310 (25H2). If winver reports the old build, the install silently rolled back again — go to step 9 in "If it still doesn't work."

If it still doesn't work

If the rollback continues after all eight steps, you almost certainly have a corrupt CBS package manifest that DISM cannot self-repair from Windows Update. Mount the matching Windows 11 24H2 ISO from https://www.microsoft.com/software-download/windows11 and use it as a known-good DISM source:

DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:D:\sources\install.wim:1 /LimitAccess

(Replace D: with the drive letter where you mounted the ISO and 1 with the index for your edition — Get-WindowsImage -ImagePath D:\sources\install.wim lists them.) If even that fails, perform an in-place upgrade by running setup.exe from the mounted ISO and choosing Keep personal files and apps. This rebuilds the servicing stack and the WinSxS store while preserving your installed programs.

For BitLocker-protected systems, suspend protection before re-running the update to avoid being prompted for the recovery key after the post-reboot phase:

manage-bde -protectors -disable C: -RebootCount 2

If you are still stuck, post your C:\Windows\Logs\CBS\CBS.log (last 200 lines) and the output of winver to the [Microsoft Q&A Windows Update forum](https://learn.microsoft.com/en-us/answers/tags/238/windows-11) — Microsoft engineers actively triage 24H2/25H2 May 2026 issues there. For related cumulative-update failures, see our deep dives on [KB5089549 EFI partition errors](/en/errors/windows-11-kb5089549-install-error-0x800f0922) and [generic 0x800f0922 fixes](/en/errors/windows-update-error-0x800f0922-windows-11).