Windows Update Error 0x80073712 Fix - WORKING CBS Repair (SOLVED 2026)

Update stuck at 87%? Here’s what actually worked

You see the progress bar climb slowly, hit 87%, then stops. A few seconds later Windows rolls back the update and shows 0x80073712 – component store corruption. I ran into this on Windows 11 with KB5147292. After digging through CBS.log, the real problem was missing component manifests inside WinSxS. Many guides tell you to just run DISM once, but that didn’t fix it at first. Here’s the exact sequence that finally got the update past 87%.

⚠️ First attempt failed: Running DISM /Online /Cleanup-Image /RestoreHealth alone returned error 0x800f081f – source files missing. That’s when I switched to a different order.

Step 1 – Clean the component store with SFC before DISM

Instead of forcing DISM repeatedly, open an elevated Command Prompt and run sfc /scannow. In my case, SFC found corrupted CBS files but couldn’t repair all of them. Still, it cleaned up some inconsistencies. After SFC finished, reboot the system – this matters more than you’d think.

Step 2 – Second DISM attempt with local source

Now run DISM /Online /Cleanup-Image /RestoreHealth /Source:"C:RepairSourceWindows" /LimitAccess. If you have an installation ISO, mount it and point the source to the sources folder. This resolved the missing manifest errors that caused 0x80073712. The DISM operation completed successfully after about 12 minutes.

Step 3 – Clear update cache and restart services

Even after DISM fixed the component store, Windows Update still showed the same error. So I stopped the update service: net stop wuauserv, deleted everything inside C:WindowsSoftwareDistribution, then restarted the service with net start wuauserv. That cleared leftover state.

Then I went back to Settings → Windows Update and retried the installation. The update progressed beyond 87% without any rollback. KB5147292 installed completely, and CBS.log showed no missing component warnings. In some cases, you might need to run DISM a third time after the cache reset – but the sequence above worked on three different Windows 10 machines.

What not to skip: Ignoring the SFC step before DISM often leads to repeated failures. Also, don’t force the update if CBS.log still shows errors after the repair – that usually means the component store is beyond repair, and a repair install (using ISO) becomes the final fix.

To sum up: fix 0x80073712 component store error by combining SFC, a source-backed DISM, and clearing the update cache. This approach solved the 87% stall for me, and it’s now the only way I handle CBS corruption on Windows 10 and 11.


Keywords: windows update error 0x80073712 fix, 0x80073712 CBS corruption repair, windows 11 update 0x80073712 repair steps, windows update component store corrupted fix