What the error means
Microsoft's name for 0x80073712 is ERROR_SXS_COMPONENT_STORE_CORRUPT, described as "The component store is in an inconsistent state." The component store is the collection of Windows components, mainly in the WinSxS folder, that Windows Update reads from and writes to every time it installs or replaces a system file. When the store's records do not match what is actually on disk, servicing cannot work out what to change, and the update stops.
Microsoft's consumer upgrade page puts it more simply: "A file needed by Windows Update is likely damaged or missing." Its Windows 10 update page groups the code with corrupted or missing system files and incomplete downloads. Every Microsoft page that lists the code points to the same repair, DISM, so this is one of the clearer update errors to act on.
The code is closely related to 0x800f081f. If DISM fails to repair the store because it cannot find clean files, it usually reports 0x800f081f, and the fix moves on to giving DISM a repair source.
Common causes
- A component damaged by an interrupted update, a sudden power loss or a forced shutdown during servicing.
- An earlier update that only partly installed, leaving the store's records out of step with its files.
- Disk errors that damaged files under the WinSxS folder.
- An incomplete download, which Microsoft lists alongside corruption for this code on Windows 10.
How to fix it
1. Run DISM to repair the component store
This is the fix Microsoft gives directly for 0x80073712. Open Command Prompt as administrator: open Start, type Command Prompt, right-click it and select Run as administrator. Then run:
DISM.exe /Online /Cleanup-image /RestorehealthStay connected to the internet. DISM works best when it can reach Windows Update to fetch replacement files, and it can take several minutes. Wait for "The restore operation completed successfully". If no confirmation appears, Microsoft says to run the command again.
2. Run System File Checker
When DISM succeeds, run SFC in the same window so the protected system files are checked against the repaired store. Let it reach 100%, close the window and run Windows Update again.
sfc /scannow3. Run the Windows Update troubleshooter
Microsoft's Windows 10 page pairs SFC with the troubleshooter for this code. On Windows 10 open Settings, Update & Security, Troubleshoot, Additional troubleshooters, select Windows Update and Run the troubleshooter. On Windows 11 the path is Settings, System, Troubleshoot, Other troubleshooters, Windows Update, Run. Then check for updates.
4. If DISM cannot finish, give it a source and read the log
If the restore operation does not complete, the log at %windir%\Logs\CBS\CBS.log lists each problem it found, marked as fixed or not. For a PC that cannot reach Windows Update, Microsoft documents running DISM against a working installation of the same Windows version:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:\\<servername>\c$\windows /LimitAccessMicrosoft's advanced procedure goes one level further. Find the build number in the corrupt entry, match it to a KB number in the Windows update history, download that update from the Microsoft Update Catalog, extract its files to a folder and use that folder as the source. Confirm the result with DISM /Online /Cleanup-Image /ScanHealth.
If nothing works
If DISM still cannot repair the store, even with a matching source, you are near the end of the documented options. Microsoft's troubleshooting page lists chkdsk /f C: from an elevated prompt to repair disk errors, which is worth running before you give up, and ends with a clean installation of Windows as the last resort. Back up your files before either step.
What we checked
On 2026-11-19 we read three Microsoft pages that list 0x80073712. The upgrade and installation errors page on support.microsoft.com says a file needed by Windows Update is likely damaged or missing and gives the DISM command. The Microsoft Learn article on fixing Windows Update corruption names it ERROR_SXS_COMPONENT_STORE_CORRUPT and documents DISM, SFC, repair sources and the CBS.log procedure. The Windows Update troubleshooting page groups it with corrupted or missing system files and recommends SFC and the troubleshooter. We did not reproduce the error.
Last checked: 2026-11-19.