Fixes / Windows · Checked

Windows Update error 0x80073712: what it means and how to fix it

Short answer

Error 0x80073712 (ERROR_SXS_COMPONENT_STORE_CORRUPT) means that Windows Update found damaged or missing files in the component store (the WinSxS folder), which it needs to install updates. The most reliable fix is to open Command Prompt as administrator and run DISM.exe /Online /Cleanup-image /Restorehealth, then sfc /scannow. After that, restart and run Windows Update again.

What this message means

Microsoft lists 0x80073712 as ERROR_SXS_COMPONENT_STORE_CORRUPT: "The component store is in an inconsistent state." The component store is the C:\Windows\WinSxS folder plus related servicing registry data. Every cumulative, security and feature update is built from the files it holds. If a file or manifest in the store is damaged or missing, the update fails during installation, often after it has already downloaded. The error does not mean your personal files are at risk. It means Windows cannot service itself until the store is repaired. The fix is almost always a repair with DISM, or a reinstall of Windows over itself that keeps your apps and files.

Common causes

CauseHow to tell
Corrupted or missing files in the component store (WinSxS)The same update (for example a monthly KB cumulative update) fails with 0x80073712 on every attempt. DISM /ScanHealth reports "The component store is repairable", and C:\Windows\Logs\CBS\CBS.log shows lines like "CSI Payload Corrupt" or "CBS MUM Missing".
An earlier update was interrupted (power loss, forced shutdown, crash during install)The error started right after a restart that hung on "Working on updates" or after a shutdown during an update. Update history shows a failed or partially installed update just before it.
Damaged or incomplete files in the Windows Update download cacheThe update downloads to 100% and then fails at the install stage, and running DISM alone does not change the result. Other updates may fail with the same or similar codes.
Third-party antivirus or endpoint security locking or blocking system filesThe error appears on a work PC with tools such as CrowdStrike, or on a home PC with a non-Microsoft antivirus. Updates succeed when that software is paused, or when the same update is tried on a clean install.
Disk errors or a failing drive corrupting system filesSFC keeps finding new corruption after repairs, the PC has other crashes or slowdowns, or chkdsk reports bad sectors. Drive health tools show warnings.

How to fix it

1. Repair the component store with DISM, then run SFC

  1. Open Start, type Command Prompt, right-click it and choose Run as administrator. Select Yes at the prompt.
  2. Stay connected to the internet (DISM downloads clean files from Windows Update). Type DISM.exe /Online /Cleanup-image /Restorehealth and press Enter. It can take 10 to 30 minutes and may appear stuck at 20% or 62%. Let it finish.
  3. Wait for "The restore operation completed successfully."
  4. Type sfc /scannow and press Enter. Wait for it to reach 100%.
  5. Restart the PC, then go to Settings > Windows Update and select Check for updates.

2. Run the Windows Update troubleshooter

Windows 11 and Windows 10 (menu paths differ)

  1. Windows 11: go to Start > Settings > System > Troubleshoot > Other troubleshooters. Next to Windows Update, select Run.
  2. Windows 10: go to Start > Settings > Update & Security > Troubleshoot > Additional troubleshooters, then select Windows Update > Run the troubleshooter.
  3. Let it apply any fixes it finds, then restart the PC.
  4. Check for updates again. If it still fails with 0x80073712, go on to the next fix.

3. Reset the Windows Update cache

  1. Open Command Prompt as administrator.
  2. Run these one at a time: net stop bits, then net stop wuauserv
  3. Run: ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak
  4. Run: ren %systemroot%\system32\catroot2 catroot2.bak (if you get "access denied", run net stop cryptsvc first and net start cryptsvc afterwards).
  5. Run: net start bits, then net start wuauserv
  6. Restart and check for updates. Windows rebuilds both folders automatically. Your update history list may look empty afterwards, which is normal.

4. Use "Fix problems using Windows Update" (reinstall current version)

Windows 11 with the February 2024 optional update or later. Not available on Windows 10.

  1. Go to Start > Settings > System > Recovery.
  2. Under Fix problems using Windows Update, select Reinstall now.
  3. Choose whether to allow an automatic restart 15 minutes after installation, then select OK.
  4. Windows downloads and installs a repair copy of your current version. It keeps your apps, files and settings.
  5. Keep the PC plugged in and online until it finishes, then run Windows Update again.

5. Do an in-place repair upgrade from Microsoft's installation media

Windows 11 (ISO or Installation Assistant) and Windows 10 (Media Creation Tool). Use this when the Reinstall now button is missing or greyed out.

  1. Back up important files first.
  2. Go to microsoft.com/software-download/windows11 (or windows10) and download the ISO for your edition and language.
  3. Right-click the ISO and choose Mount, then run setup.exe from the new drive.
  4. When asked what to keep, choose Keep personal files and apps.
  5. Let setup finish (about 30 to 90 minutes and several restarts), then run Windows Update.

6. Repair DISM from a local source when it fails with 0x800f081f

For IT staff, or when the PC cannot reach Windows Update

  1. Mount a Windows ISO whose version and build match the installed system, and note the drive letter (for example D:).
  2. Run: DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:D:\sources\install.wim:1 /LimitAccess (change the index to match your edition. Use install.esd with ESD: if that is the file in the ISO).
  3. If it still fails, open C:\Windows\Logs\CBS\CBS.log and find the corrupt component names and their build numbers (for example 10.0.26100.xxxx).
  4. Download the matching KB from the Microsoft Update Catalog, extract it to C:\temp\Source, and run DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\temp\Source\ /LimitAccess
  5. Confirm with DISM /Online /Cleanup-Image /ScanHealth, then run Windows Update.

Next time, skip the search

Crade is an AI assistant for Mac and Windows that sees your screen. When a message like this pops up, ask “what does this mean?” and it explains the exact error in front of you, step by step.

Download Crade

Still not fixed?

If DISM keeps failing and neither Reinstall now nor an in-place upgrade from the ISO works, run chkdsk C: /scan and check the drive's health, because a failing disk will keep corrupting files. On a work or school PC, contact IT before making changes. Group Policy may block the repair options, and security software such as CrowdStrike may need an exception. For a home PC, back up your files and use Settings > System > Recovery > Reset this PC with the Cloud download option. You can also contact Microsoft Support through the Get Help app and attach C:\Windows\Logs\CBS\CBS.log.

Questions people ask

Is error 0x80073712 dangerous or a sign of a virus?

Usually not. It means Windows' own update component store is damaged, often after an interrupted update. The real risk is that you stop receiving security patches until it is fixed.

Will fixing 0x80073712 delete my files or apps?

No. DISM, SFC, resetting the update cache, Reinstall now and an in-place upgrade with Keep personal files and apps all keep your data. Only Reset this PC can remove apps, so back up before using it.

DISM says the source files could not be found (0x800f081f). What now?

DISM could not get clean copies of the damaged files. Point it at a mounted ISO of the same Windows build with /Source and /LimitAccess, or skip DISM and use Reinstall now or an in-place upgrade.

Can I just install the failing update manually from the Microsoft Update Catalog?

You can try, but installing the .msu uses the same damaged component store, so it usually fails with the same code. Repair the store first, then install the update.

Why does the error keep coming back after SFC says it fixed everything?

SFC repairs protected system files using the component store. If the store itself is corrupt, SFC cannot fix the underlying problem. Run DISM /RestoreHealth before SFC, and check the disk if corruption keeps returning.

Sources

Related errors