Windows Update Error 0x80073712: Repair Missing System Files

A cumulative or security update fails with 0x80073712 — “Some files needed to install the update are missing” (ERROR_SXS_COMPONENT_STORE_CORRUPT). It means the component store (WinSxS) is damaged, so the updater can’t assemble the package.

Why the usual one-liner falls short: the standard advice is DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow. That’s correct — if the PC can reach Windows Update to pull replacement files. When the store itself is corrupt or the machine is offline/WSUS-managed, RestoreHealth errors out, and people loop on it. The reliable fix is giving DISM a clean repair source.

Fix 1: Standard repair (try once)

Admin Command Prompt:

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

Reboot, retry the update. Still 0x80073712? Don’t repeat — give it a source.

Fix 2: Repair from a matching Windows image

1. Download the Windows ISO that matches your build (same version, e.g. 23H2/24H2) and mount it (say it becomes D:).
2. Repair against it, blocking Windows Update so it uses your source:

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

   For a WIM source, change both the prefix to WIM: and the filename to install.wim. Replace the drive and image index with the verified source for your edition, language, architecture and Windows version; a generic index 1 is not necessarily your edition. The source must have the required servicing files/update level.
3. Reboot, run sfc /scannow, then retry the update.

Fix 3: Reset Windows Update components

If the store repairs but the update still won’t apply, clear the download cache. Admin Command Prompt:

net stop wuauserv
net stop bits
net stop cryptsvc
ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
ren %systemroot%\System32\catroot2 catroot2.old
net start wuauserv
net start bits
net start cryptsvc

Reboot and retry.

Fix 4: Match the corruption to a KB (advanced)

If DISM /Online /Cleanup-Image /RestoreHealth reports specific corrupt files in CBS.log, note your current build (UBR), find the matching KB on the Microsoft Update Catalog, and run DISM against that extracted payload — the targeted approach for stubborn store corruption.

These cache commands are for administrator Command Prompt in the installed Windows session. Save work first. If a service does not stop, a folder remains locked or the .old destination already exists, inspect the error before continuing; preserve existing backups. Restart stopped services afterward. Do not use these percent-variable commands from PowerShell or WinRE.

FAQ

Will an in-place upgrade fix it? Yes — running setup.exe from the matching ISO (“Keep apps and files”) rebuilds the component store and is the dependable last resort if DISM /Source won’t.

0x80073712 vs 0x800f0831? Same family (store corruption). 0x800f0831 names a missing package; for that path see 0x800f0831 fix.

Sources: Microsoft Learn — Stop Cryptographic Services before renaming catroot2, Microsoft Learn — Fix Windows Update errors (component store / DISM)