How Do I Fix Windows Update Error 0x80073712?

Issue type: Windows Update error — 0x80073712 (ERROR_SXS_COMPONENT_STORE_CORRUPT)

SEO focus: If you are looking for windows update error 0x80073712, this guide starts with the fastest diagnosis, then moves to the exact fix that matches the symptom.

Short answer: Error 0x80073712 means the Windows Component Based Servicing (CBS) store has missing or corrupted files. Windows Update relies on this store to install components. The fix is DISM /RestoreHealth — run it first, then SFC. If DISM can’t reach Windows Update servers, point it to a local Windows ISO instead.

Windows Update Error 0X80073712: Quick Diagnosis

The CBS store is Windows’ central database for all installable components. When it’s corrupted, any update that touches system components will fail with 0x80073712. To see the specific error, check the CBS log directly:
Open File Explorer and navigate to: C:WindowsLogsCBSCBS.log
Open it in Notepad and use Ctrl + F to search for “corrupt” or “missing.” Look for entries near the time your update failed. The log records which specific component file is damaged, which helps confirm the cause. If DISM fixes it, you don’t need to act on the log — it’s just for confirmation.

What to do first

1. Run DISM to scan and repair the component store. Open Command Prompt as Administrator and start with a quick health check:
   DISM /Online /Cleanup-Image /CheckHealth
   If it reports “The component store is repairable,” proceed to the actual repair:
   DISM /Online /Cleanup-Image /RestoreHealth
   This downloads replacement files from Windows Update and repairs the store. It takes 15–45 minutes. Do not interrupt it.
2. After DISM completes successfully, run SFC:
   sfc /scannow
   Restart your PC after SFC finishes.
3. Run the Windows Update Troubleshooter:
   Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run
4. Clear the update cache to remove any partially downloaded corrupted files:
   net stop wuauserv
net stop bits
ren C:WindowsSoftwareDistribution SoftwareDistribution.old
net start wuauserv
net start bits
   Then go to Settings > Windows Update and check for updates again.
5. If DISM /RestoreHealth fails with “The source files could not be found,” it can’t reach Windows Update servers. Download a Windows 11 ISO from Microsoft’s website (the same version and build as your current system). Mount it by double-clicking, then run:
   DISM /Online /Cleanup-Image /RestoreHealth /Source:D:Sourcesinstall.wim /LimitAccess
   Replace D: with the actual drive letter of the mounted ISO.
6. After a successful DISM run using the ISO, run sfc /scannow again and restart.

Common mistake

Running DISM /Cleanup-Image /CheckHealth and, when it says “No component store corruption detected,” stopping there. This command only reads an internal flag — it doesn’t scan every file in the store. If Windows Update is still reporting 0x80073712, run /RestoreHealth regardless of what /CheckHealth says. The flag can be clean while actual files in the store are missing or damaged.

Best next step

If DISM /RestoreHealth fails both online and with a local ISO, and the CBS log shows widespread corruption, the component store is beyond online repair. At this point, run the Media Creation Tool and choose “Upgrade this PC now.” This performs an in-place upgrade that fully rebuilds the Windows image and component store without removing your files or applications. It’s the cleanest path when DISM can’t complete the repair.

Official reference: For official update guidance, check Microsoft’s Windows Update FAQ before using advanced repair steps.

Quick Q&A

How long does DISM /RestoreHealth actually take?

Typically 15–45 minutes, depending on how many files need to be replaced and your internet connection speed. During the repair, DISM downloads replacement files directly from Windows Update. The progress percentage may stay at 20% for a long time before jumping — that’s normal. Don’t cancel it.

DISM says “The source files could not be found” even though I’m connected to the internet. What’s wrong?

Windows Update servers might be temporarily unreachable, or a firewall or proxy is blocking DISM’s outbound connection. Try again later, or use the local Windows ISO method described above. If you’re on a corporate network, your IT policy may block DISM’s server access — the ISO method is the reliable alternative in that case.

Can installing a third-party application cause 0x80073712?

Yes. Applications that install system-level components or modify the Windows registry heavily — such as certain virtualization tools, driver packages, or poorly written system utilities — can corrupt CBS store entries. If the error appeared right after installing something, try uninstalling it first, then run DISM.