Fix Windows Update Error 0x80073712 in Windows 11

Error 0x80073712 is Windows telling you it reached for a file it needed to install an update and the file was not there, or was damaged. It is annoying, but it is one of the most repairable update errors, because the fix is almost always to rebuild the component store rather than to reinstall Windows.

Key takeaways

• The error points to a damaged or missing file in the component store, not a broken PC.
• DISM then SFC, in that order, repairs the store and the protected system files that depend on it.
• Resetting Windows Update components clears a stuck download cache that keeps re-triggering the failure.
• A specific 2026 preview update caused a wave of this error; KB5086672 is the direct patch for that case.
• You rarely need to reinstall Windows to clear 0x80073712.

What causes error 0x80073712

The component store, kept in the WinSxS folder, holds the building blocks Windows uses to install and repair features and updates. When one of those manifests or payload files is missing or corrupted, any update that references it fails and returns 0x80073712. Common triggers include an interrupted previous update, disk corruption, aggressive third-party cleanup tools that deleted WinSxS contents, or a bad patch that Microsoft later pulled.

In early 2026 the error spiked because a Windows 11 preview cumulative update shipped with an installation flaw on some 24H2 and 25H2 devices. Microsoft responded with an out-of-band cumulative update, KB5086672, that specifically corrects that failure. If your error started right after installing a March 2026 preview build, check for and install that update before doing anything else.

First, try the built-in repair path

Before touching the command line, let Windows try to fix itself. The Update troubleshooter resets a surprising number of update problems on its own.

Go to Settings, System, Troubleshoot, Other troubleshooters, then run the Windows Update troubleshooter and restart. If the same error returns, move on to the component repair below, which is the part that actually clears most cases of 0x80073712.

Repair the component store with DISM and SFC

This is the core fix. DISM repairs the component store itself, and SFC then repairs the protected system files that draw from it. Run them in this order, because SFC pulls its known-good copies from the store that DISM just repaired.

1. Right-click Start and open Terminal (Admin) or Command Prompt (Admin).
2. Run DISM /Online /Cleanup-Image /RestoreHealth and wait; it can pause near 20 percent for several minutes, which is normal.
3. When it finishes, run sfc /scannow and let it complete.
4. Restart the PC.
5. Go back to Windows Update and try the update again.

If DISM reports it cannot find source files, it needs a clean copy of the components. You can point it at a mounted Windows 11 ISO with /Source: , or simply make sure you are online so it can pull from Windows Update.

Reset Windows Update components

If the store checks out clean but the update still fails, the download cache is likely stuck. Stopping the services, clearing the cache folders, and restarting forces Windows to fetch a fresh copy of the update.

1. In an admin terminal, stop the services: net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver.
2. Rename the cache folders: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old.
3. Restart the services with the matching net start commands.
4. Restart the PC and retry the update.

Match the symptom to the fix

Symptom	Likely cause	Fix
Error appeared after a March 2026 preview build	Known flawed cumulative update	Install out-of-band update KB5086672
DISM reports corruption found and repaired	Damaged component store	Run sfc /scannow, then retry the update
Update downloads then fails at install	Stuck update cache	Reset Windows Update components
DISM cannot find source files	Component payload missing	Point DISM at a mounted Windows 11 ISO
Repeated failures across many updates	Disk corruption	Run chkdsk C: /scan, then repeat DISM and SFC

What to do right now

Work through these in order and stop when updates install cleanly:

• Check Windows Update and install any newer cumulative update, including KB5086672 if it is offered.
• Run the Windows Update troubleshooter and restart.
• Run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow, then restart.
• If it still fails, reset the Windows Update components by clearing SoftwareDistribution and catroot2.
• Run chkdsk C: /scan to rule out disk corruption before assuming a hardware problem.

If updates trigger a boot failure instead of a simple error code, our guide to fixing the Inaccessible Boot Device BSOD covers recovery. And if a different update code stops you at the recovery partition, see the fix for Windows Update error 0x80070643.

Frequently asked questions

Will I lose my files fixing this error?

No. DISM, SFC, and resetting update components repair system files and caches only. They do not touch your documents, photos, or installed apps. A reinstall would be the only step that risks data, and it is almost never needed for 0x80073712.

How long does DISM RestoreHealth take?

Usually 10 to 20 minutes, though it can run longer on a slow disk or a heavily corrupted store. It commonly appears frozen around 20 percent; leave it alone and let it finish rather than closing the window.

What if DISM cannot find the source files?

That means the component payload it needs is missing. Download the matching Windows 11 ISO, mount it, and rerun DISM with the /Source: switch pointing at the mounted install.wim. Being online during the repair also lets DISM pull from Windows Update.

Is KB5086672 relevant if my error started earlier?

Only if the error traces to the specific March 2026 preview build it was made to fix. If your error predates that, the store repair and update reset steps are your path. Installing the latest cumulative update is still worthwhile regardless.