How to fix error 0x80073712 in Windows 11/10

Last updated on 

0x80073712 means "The component store is in an inconsistent state." Windows keeps a local repository of all its system components in the WinSxS folder, and something in there got corrupted. You'll mostly see this when trying to install updates, but it also shows up when running DISM or enabling Windows features.

Why this happens

  • A previous update got interrupted mid-install (power loss, forced reboot, crash)
  • Disk errors corrupted files inside the component store
  • Manual cleanup tools removed files Windows still needed
  • Third-party "system optimizers" deleted things they shouldn't have
  • A failed servicing stack update left the store half-finished

1. Run the Windows Update troubleshooter

Worth trying first. It actually resolves some component store issues on its own.

Windows 11: Settings → System → Troubleshoot → Other troubleshooters, click Run next to Windows Update.

Windows 10: Settings → Update & Security → Troubleshoot → Additional troubleshooters, pick Windows Update.

Reboot after it finishes and retry the update.

2. Run DISM to repair the component store

This is the actual fix for 0x80073712 most of the time. DISM scans the component store and pulls fresh copies of corrupted files from Microsoft's servers.

Open Command Prompt as admin and run these in order:

DISM /Online /Cleanup-Image /CheckHealth

Quick check. If it reports problems, run the full scan:

DISM /Online /Cleanup-Image /ScanHealth

ScanHealth takes a while. If it finds corruption, repair it:

DISM /Online /Cleanup-Image /RestoreHealth

RestoreHealth downloads replacement files from Microsoft, so you need internet. It can take 15-30 minutes depending on how much is broken. Don't interrupt it.

Reboot when it's done and try the update again.

3. If DISM fails, point it at a Windows image

Sometimes the component store is damaged badly enough that DISM can't pull what it needs from Windows Update. You can give it a clean Windows image instead.

Download the Windows 11 or 10 ISO from Microsoft's download page. Mount it by double-clicking the ISO file and note the drive letter it gets (usually D: or E:).

Then run:

DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim /LimitAccess

Replace D: with whatever drive letter the mounted ISO got. /LimitAccess tells DISM to skip Windows Update entirely and only use the local image.

4. Run SFC after DISM

DISM fixes the component store. SFC fixes individual system files using that store. Order matters here, fix the store first, then the files.

sfc /scannow

If SFC finds and repairs anything, reboot and run it one more time to make sure it's clean. Then retry your update.

5. Reset Windows Update components

If the update still fails after repairing the store, the update cache might be messed up too. Same process as with most update errors. Open Command Prompt as admin.

Stop the services:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver

Rename the cache folders:

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old

Start them back up:

net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Reboot and check for updates. Delete the .old folders once the update goes through.

6. Check the disk for errors

If the component store keeps getting corrupted, the disk itself might be failing. Run a full check:

chkdsk C: /f /r

It'll ask to schedule it for the next reboot since it can't check the system drive while Windows is running. Type Y, reboot, let it do its thing. This takes a while on larger drives. If chkdsk finds bad sectors, go back and run DISM and SFC again afterward.

7. Manually clear the pending updates list

Sometimes a corrupted pending update entry keeps triggering the error even after everything else is fixed. You can clear it through the registry.

Open Registry Editor (Win+R, type regedit) and navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing

Look for a key called SessionsPending. If it exists, change the value of Exclusive inside it to 0. Then find and delete the PackagesPending key if it's there.

Reboot after making these changes. Only touch exactly what's described here, this part of the registry is not a place to experiment.

Last resort: in-place upgrade

If nothing above worked, the component store is too far gone for repair tools. Download the Windows Media Creation Tool from Microsoft. Run it, choose "Upgrade this PC now", keep your files and apps. This reinstalls Windows on top of itself without wiping your data, and you get a completely fresh component store in the process.

Check for updates after the upgrade finishes. The error should be gone.