Windows & BSOD · high

How to fix Windows Update Error 0x80073712

Windows & BSOD troubleshooting guide

What this error means

Windows Update cannot install an update because the component store is damaged. The component store (the WinSxS folder) holds the files Windows uses to install updates and features, and Microsoft names this code ERROR_SXS_COMPONENT_STORE_CORRUPT: the store is in an inconsistent state. It usually follows an interrupted update, a forced shutdown or disk errors. Windows can normally repair the store itself with DISM, either online or from installation media. The same repair applies to 0x80073701 (ERROR_SXS_ASSEMBLY_MISSING) and 0x800F0984 (PSFX_E_MATCHING_BINARY_MISSING), which Microsoft also lists as component store corruption errors.

Updated

Applies to
Windows 11 and Windows 10
Difficulty
Intermediate
Before changes
Low; the repair commands only replace damaged Windows files

Reviewed by Matyáš Rada · Documentation checked: 2026-10-31 · Checked against Microsoft's documentation on fixing Windows Update corruption errors; not tested on every configuration.

Before you begin

You need an administrator account and, for the DISM steps, an internet connection or a Windows ISO of the same version. Back up important files if the PC has had disk errors. If Windows cannot start, see the startup guide.

Work through these checks

0 of 7 complete
01Restart and run the Windows Update troubleshooter

A pending restart from an earlier update can leave the store temporarily inconsistent.

  1. Restart the PC (use Restart, not Shut down) and try Windows Update again.
  2. On Windows 11, open Settings > System > Troubleshoot > Other troubleshooters and select Run next to Windows Update. On Windows 10, use Settings > Update & Security > Troubleshoot > Additional troubleshooters.
What to expect

The update installs.

If it does not help

If it fails again with 0x80073712, repair the store in step 2.

Browse related errors
02Repair the component store with DISM

This is Microsoft's documented fix for this code: DISM downloads clean copies of damaged files from Windows Update.

  1. Right-click Start and open Terminal (Admin).
  2. Run DISM.exe /Online /Cleanup-image /Restorehealth and wait; it can stay at one percentage for several minutes.
  3. Run sfc /scannow.
  4. Restart and run Windows Update again.
What to expect

DISM reports "The restore operation completed successfully" and the update installs.

If it does not help

If DISM fails, often with 0x800f081f, it could not get clean files; use installation media in step 3.

Browse related errors
03Repair it from Windows installation media

Microsoft documents using a working Windows installation or installation files as the repair source when Windows Update cannot provide them.

  1. Download the ISO for your Windows version and language from Microsoft's software download page, right-click it and choose Mount. Note its drive letter, for example D:.
  2. Run dism /Get-WimInfo /WimFile:D:\sources\install.wim and note the Index of your edition (for example Windows 11 Pro).
  3. Run DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:D:\sources\install.wim:6 /LimitAccess, replacing 6 with your index.
  4. Run sfc /scannow, restart and try Windows Update.

The ISO must be the same Windows version (for example 24H2) and language as the installed system.

What to expect

DISM completes the repair using the files from the ISO.

If it does not help

If the folder has install.esd instead of install.wim, use that file name and ESD: instead of WIM:. The 0x800F081F guide on this site covers this repair in more detail.

Browse related errors
04Clear the Windows Update cache

Damaged downloaded update files and update metadata can keep the error coming back after the store is repaired.

  1. Search for cmd, right-click Command Prompt and choose Run as administrator. Run net stop wuauserv, net stop bits and net stop cryptsvc.
  2. Run ren %systemroot%\SoftwareDistribution\Download Download.bak and ren %systemroot%\SoftwareDistribution\DataStore DataStore.bak.
  3. Run ren %systemroot%\system32\catroot2 catroot2.bak.
  4. Run net start cryptsvc, net start bits and net start wuauserv, then check for updates.

Use Command Prompt for these commands; %systemroot% does not work in PowerShell.

What to expect

Windows Update downloads the update again from scratch.

If it does not help

The update history in Settings may look empty afterwards; installed updates are not affected.

Browse related errors
05Check the drive and free space

Disk errors are a common reason the store gets damaged, and updates need free space to install.

  1. In Terminal (Admin), run chkdsk C: /scan. If it reports problems, run chkdsk C: /f and allow it to run at the next restart.
  2. If C: is nearly full, free up space in Settings > System > Storage > Cleanup recommendations.
What to expect

No file system errors and enough free space.

If it does not help

If the drive reports errors repeatedly, back up and check its health in the maker's tool.

Browse related errors
06Install the update manually

Installing the update package directly can work even when the automatic installation fails.

  1. In Settings > Windows Update > Update history, note the KB number of the failed update.
  2. Search for that KB number on the Microsoft Update Catalog (catalog.update.microsoft.com) and download the version for your system (usually x64).
  3. Run the downloaded .msu file and restart.

Download updates only from Microsoft.

What to expect

The update installs and appears in the update history.

If it does not help

If the manual installation fails with the same code, go to step 7.

Browse related errors
07Repair Windows with an in-place upgrade

An in-place upgrade replaces the whole component store with a clean copy and keeps your files and apps.

  1. Mount the Windows ISO from step 3.
  2. Run setup.exe from it and choose to keep personal files and apps.
  3. After it finishes, run Windows Update.

Back up important files before starting.

What to expect

Windows is reinstalled over itself and updates install normally.

If it does not help

If even setup fails, back up your files and do a clean installation.

Browse related errors

Possible causes

  • Damaged files in the component store (WinSxS)
  • An earlier update that was interrupted or did not finish
  • Power loss or a forced shutdown during an update
  • File system errors on the system drive
  • Security software removing or locking system files

Sources & further reading