Windows 11 KB5094126 June 2026 Install Error 0x80073712 / 0x800f0993

What is the KB5094126 install error?

KB5094126 is the June 10, 2026 Windows 11 Patch Tuesday cumulative update for versions 24H2 and 25H2. After installation kicks off, the update gets to roughly 30%–96% and then rolls back with one of two codes: 0x80073712 (ERROR_SXS_COMPONENT_STORE_CORRUPT) or 0x800f0993 (CBS_E_INVALID_PACKAGE_FROM_OEM). The download finishes, but the component-based servicing stack refuses to commit the payload to the WinSxS store.

Microsoft has confirmed both codes disproportionately hit machines that were upgraded to 24H2 or 25H2 from Windows 10 22H2/21H2 or Windows 11 23H2 — clean installs of 24H2/25H2 are largely unaffected. The leftover manifests from the previous feature update are the load-bearing trigger.

When does it occur?

• During Windows Update install of KB5094126 after the device restarts.
• When manually running the offline MSU from the Microsoft Update Catalog.
• After a feature-update jump from 23H2 → 24H2 or 24H2 → 25H2 within the last 6 months.
• On OEM laptops with custom recovery partitions (HP, Dell, Lenovo Vantage builds).
• When the WinSxS component store has an unflushed pending operation from a prior update.
• On systems with less than 8 GB free on the System Reserved/EFI partition.

Common causes

• Corrupted entries in the WinSxS component store from an earlier upgrade.
• Pending .mum or .cat manifests left over from KB5089549, KB5089573, or KB5077181.
• The Windows Update database in C:\Windows\SoftwareDistribution\DataStore is locked.
• EFI System Partition (ESP) under 100 MB free, blocking boot-critical staging.
• OEM customization package conflict (HP CMSL, Dell Command Update, Lenovo Vantage).
• Third-party antivirus filter driver (ESET, Bitdefender, Kaspersky) intercepting wusa.exe.
• Pending .NET runtime install left in a half-committed state.

Step-by-step fixes

1. Confirm your build. Open Run (Win+R), type winver, hit Enter. You need to be on Build 26100.x (24H2) or 26200.x (25H2). If you're still on 22631.x (23H2) this KB is not for you.
2. Run the DISM + SFC repair sequence. Open PowerShell as Administrator and run, in order: DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase, then DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. Reboot, then retry the update. This resolves the 0x80073712 component store corruption in roughly 70% of cases.
3. Reset the Windows Update stack. In an elevated PowerShell: net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver, then ren C:\Windows\SoftwareDistribution SoftwareDistribution.old, ren C:\Windows\System32\catroot2 catroot2.old, then restart all four services. Try the install again.
4. Clear the EFI partition. Run mountvol Y: /s, then check free space with dir Y:\EFI. If under 100 MB free, delete obsolete language packs in Y:\EFI\Microsoft\Boot\Fonts\ you do not need, then mountvol Y: /d.
5. Disable third-party AV temporarily. Right-click the tray icon for ESET / Bitdefender / Kaspersky / Norton → Disable protection for 1 hour. Re-run Windows Update. Re-enable immediately after.
6. Install the SSU first, then the LCU. Grab KB5063945 (the matching June 2026 Servicing Stack Update) from the Microsoft Update Catalog. Install it first with wusa.exe windows10.0-kb5063945-x64.msu /quiet, reboot, then install KB5094126.
7. Run the Windows Update troubleshooter (new agent). Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run. The 25H2 agent now ships with a specific KB5094126 mitigation rule.
8. In-place repair upgrade. Download the current Windows 11 ISO from microsoft.com/software-download/windows11, mount it, run setup.exe from inside the mounted ISO, choose "Keep personal files and apps." This rebuilds the component store while preserving your data.

If it still doesn't work

If all eight steps fail, the WinSxS store likely has unrecoverable corruption from a partially-applied prior update. Boot into Safe Mode (Settings → System → Recovery → Advanced startup), then run Dism /Online /Cleanup-Image /AnalyzeComponentStore and check the "Component Store Cleanup Recommended" line. If it says "Yes" but /StartComponentCleanup won't run, you need to capture the CBS log: copy C:\Windows\Logs\CBS\CBS.log to your desktop and search for the first [SR] or [CSI] line containing 0x80073712 — the package GUID listed is the corrupt entry. Microsoft's Support page for KB5094126 (microsoft.com/help/5094126) has the OEM-specific escalation contacts.