Quick fix: Open Terminal (Admin) and run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow, then retry Windows Update — error 0x80073712 means a system file is missing or corrupted, and DISM downloads a clean replacement.

Windows Update fails with error code 0x80073712. The error message reads “Some update files are missing or have problems.” You retry; same error. The underlying meaning of this specific code is that the Windows component store (WinSxS) has a manifest pointing to a file that doesn’t exist or is corrupted — preventing the update from completing.

Symptom: Windows Update fails with error 0x80073712 (ERROR_SXS_COMPONENT_STORE_CORRUPT).
Affects: Windows 11 (and Windows 10) with corrupted WinSxS / system files.
Fix time: ~30 minutes.

What causes this

The 0x80073712 hex code maps to ERROR_SXS_COMPONENT_STORE_CORRUPT. The WinSxS component store has a manifest that references files that should exist but don’t — typically because an antivirus quarantined them, a disk error truncated them, or a previous failed update left orphaned references. Windows Update can’t apply patches to files that aren’t there.

The fix is to repair the component store (DISM) and then the active system files (sfc), then retry the update.

Method 1: Run DISM RestoreHealth followed by sfc

The standard repair pair. Works for most 0x80073712 cases.

Open Terminal (Admin) from the Start right-click menu.

Run DISM in three stages:

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

The RestoreHealth step downloads replacement components from Microsoft. Requires internet. Takes 10-20 minutes.
If RestoreHealth fails with a similar 0x80073712 (because too many components are missing for online repair), use Method 2.
After DISM completes, run System File Checker:
```
sfc /scannow
```
This takes another 10-20 minutes. The second pass should report no integrity violations.
Reboot.
Open Settings → Windows Update → Check for updates. The previously-failing update should now apply.

If the update still fails after this combination, the corruption is deeper — proceed to Method 2.

Method 2: Use a Windows 11 install image as the repair source

For deeper corruption where online RestoreHealth can’t fix everything.

Download the Windows 11 ISO matching your current version from microsoft.com/software-download/windows11. Use the Disk Image option.
Right-click the downloaded ISO → Mount. A virtual drive appears (note its letter — e.g., F:).
The ISO contains sources\install.wim (or install.esd for compressed images).

If it’s an .esd file, convert to .wim first:

DISM /Get-WimInfo /WimFile:F:\sources\install.esd
DISM /Export-Image /SourceImageFile:F:\sources\install.esd /SourceIndex:1 /DestinationImageFile:C:\install.wim /Compress:max /CheckIntegrity

Run RestoreHealth with the local image as source:
```
DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:F:\sources\install.wim:1 /LimitAccess
```
(Adjust F: to your mounted ISO drive letter; use C:\install.wim if you converted in step 4.)
The /LimitAccess flag prevents Windows Update from being used as a fallback source — important when Windows Update itself is broken.
Run sfc /scannow afterward.
Reboot, retry Windows Update.

This is the right move when the online image source has its own issues; using a local known-good ISO bypasses them.

Method 3: Reset Windows Update components and retry

Use when DISM and sfc both report success but the same update still fails.

Open Terminal (Admin).

Reset the entire Windows Update component stack:

net stop wuauserv
net stop bits
net stop cryptsvc
Rename-Item C:\Windows\SoftwareDistribution C:\Windows\SoftwareDistribution.old -ErrorAction SilentlyContinue
Rename-Item C:\Windows\System32\catroot2 C:\Windows\System32\catroot2.old -ErrorAction SilentlyContinue
net start wuauserv
net start bits
net start cryptsvc

Reboot.
Open Settings → Windows Update → Check for updates. Windows rebuilds its update state from scratch.
If the update still fails with 0x80073712, try installing the specific KB manually via the Microsoft Update Catalog (catalog.update.microsoft.com).

The two renamed folders rebuild themselves on next Windows Update access, clearing any stale state.

How to verify the fix worked

Run sfc /scannow from elevated Terminal. Result: “Windows Resource Protection did not find any integrity violations.”
Run DISM /Online /Cleanup-Image /CheckHealth. Result: “No component store corruption detected.”
Open Settings → Windows Update and click Check for updates. The previously-failing update installs successfully.
After reboot, Update history shows the KB as Successfully installed.

If none of these work

If 0x80073712 persists after DISM, sfc, ISO-based repair, and Windows Update component reset, the install’s WinSxS is too damaged for in-place repair. In-place upgrade install: mount the Windows 11 ISO and run setup.exe from within Windows. Choose Keep personal files and apps. This reinstalls Windows on top of the current install while preserving everything — it fixes WinSxS corruption that no other method can. Takes 30-45 minutes. Personal files and most apps survive. For chronic corruption that returns after in-place upgrade, check storage health (CrystalDiskInfo for SSDs, SMART status) — failing storage causes silent file corruption that DISM and sfc can’t permanently fix. Replacing the drive plus a fresh install is the durable solution.

Bottom line: Error 0x80073712 means missing or corrupted component store files — DISM RestoreHealth downloads replacements, sfc fixes active system files, and Update components reset clears stale state. Most cases resolve with these three steps.