Error 0x80073712 means Windows has detected a problem with its component store.
Microsoft identifies the error as ERROR_SXS_COMPONENT_STORE_CORRUPT and describes it as:
“The component store is in an inconsistent state.” [R1]
This is more specific than a generic “Windows Update failed” message. It tells us that Windows cannot reliably use part of the system data it needs to service or update the operating system.
What is the component store?
The Windows component store is mainly located in the WinSxS folder inside the Windows directory.
It contains Windows components and servicing information used for tasks such as:
- installing Windows updates;
- enabling or disabling Windows features;
- repairing Windows after corruption;
- uninstalling some updates; and
- maintaining different versions of Windows components. [R2]
The component store is therefore part of Windows itself. It is not an ordinary cache that should be emptied manually.
Do not delete files from C:\Windows\WinSxS to try to fix this error.
Does 0x80073712 mean one particular file is broken?
No.
The code identifies an inconsistent component store, but it does not by itself identify the exact damaged or missing component.
Windows servicing logs can contain more specific information about the package or component that failed. For ordinary troubleshooting, however, the first useful question is whether Windows can repair the component store using its supported servicing tools.
What does DISM do?
DISM — Deployment Image Servicing and Management — is a Windows servicing tool.
For this problem, its RestoreHealth operation scans the Windows image for component-store corruption and performs repair operations automatically. [R3]
Microsoft's Windows Update repair guidance recommends:
DISM.exe /Online /Cleanup-Image /RestoreHealth
for Windows Update failures caused by servicing corruption. After DISM completes successfully, Microsoft recommends running System File Checker (sfc /scannow) and then trying Windows Update again. [R1]
DISM repairs the component store. SFC can then use the repaired Windows component data when checking protected system files.
Why can DISM take a long time?
RestoreHealth is not only checking whether a Windows Update download exists.
It examines the Windows image for component-store corruption and, when necessary, obtains known-good repair files. Microsoft states that the operation can take several minutes. [R3]
For an online Windows installation, DISM can use Windows Update as a repair source when another source is not specified. [R1] [R3]
The total time therefore depends on the condition of the component store, the work required to repair it, the PC's storage performance, and whether repair files need to be obtained from Windows Update.
A percentage indicator appearing to remain unchanged for a while does not by itself prove that DISM has failed.
What if DISM cannot repair it?
DISM itself may fail if it cannot obtain the files needed for repair.
Microsoft supports specifying another repair source containing known-good Windows files. [R3]
That is a different problem from simply rerunning the same command repeatedly. If repair files cannot be found, the next error code and the DISM/CBS evidence should determine the next step.
For example, error 0x800F081F means the repair source files could not be found and should be handled as a separate finding.
If the component store remains damaged after supported repair attempts, a more substantial Windows repair may be required.
Could the update itself be the problem?
Possibly.
An occurrence of 0x80073712 should not automatically be interpreted as proof that the user damaged Windows.
Microsoft has documented individual Windows updates that could themselves fail with 0x80073712 on some devices and later supplied a resolution through another update. [R4]
If the error appears only with one particular update, its Microsoft release notes and known-issues section should therefore be checked before escalating to major repair work.
What should I do now?
- Note which Windows update failed and whether other updates also fail.
- Restart Windows once if a restart is already pending.
- Run the supported Windows component-store repair using DISM RestoreHealth.
- Allow the operation to finish even if progress appears slow.
- If DISM completes successfully, run System File Checker as recommended by Microsoft. [R1]
- Restart the PC.
- Retry the original Windows update.
- If DISM fails, use its own error code and repair-source evidence to decide the next step rather than repeatedly rerunning it.
- If only one specific update fails, check Microsoft's release notes for a known issue affecting that update.
See also: windows-update-keeps-failing
A successful repair means the component-store repair completes successfully and the original Windows update can then install.
A DISM process merely reaching 100%, without a successful repair result or a successful retry of the original update, is not by itself proof that the incident is resolved.