Windows Update component-store corruption: DISM and SFC repair path
Use this path for servicing errors such as 0x800F081F, 0x800F0831 and 0x80073712 when component-store repair is relevant.
- Record the exact hexadecimal error and failing update.
- Run the Windows Update troubleshooter first.
- Restart and retry once after the troubleshooter.
- Use DISM/SFC when the error maps to component-store corruption or missing servicing content.
What this problem usually means
Microsoft’s current Windows Update troubleshooting documentation maps several CBS/servicing errors to component-store corruption or missing repair source content. These errors deserve a component-repair branch rather than generic cache deletion as the default answer.
Work from the narrowest fix to the broader one.
Repair the Windows component image with DISM
Medium riskWhy this belongs here: Microsoft maps these component-store errors to DISM RestoreHealth as a standard mitigation.
- Open Windows Terminal or Command Prompt as administrator.
- Run DISM RestoreHealth and wait for completion.
- Do not interrupt the repair operation.
DISM.exe /Online /Cleanup-Image /RestoreHealthRun SFC after DISM completes
Medium riskWhy this belongs here: SFC checks protected system files after the component repair source has been addressed.
- In the elevated terminal, run SFC.
- Wait for verification to complete.
- Restart Windows before trying the update again.
sfc /scannowUse a matching repair source only when DISM requires it
Medium riskWhy this belongs here: 0x800F081F can indicate that the source required for repair cannot be found; a random image/source can make troubleshooting worse.
- Record the DISM error instead of repeatedly rerunning the same command.
- Verify the installed Windows edition/build before choosing external installation media as a repair source.
- Use Microsoft’s servicing guidance for a matching source or move to the supported reinstall-repair path.
When this guide stops being the right path
If the error is access denied, disk corruption, network delivery or another non-component-store class, use the error-specific record instead of forcing DISM into every update failure.
If the problem is still not fixed
If component repair repeatedly fails, the Windows 11 “Fix problems using Windows Update” reinstall option can be a supported next stage on eligible systems because it reinstalls the same Windows version while preserving apps, files and settings.
Sources reviewed for this page
Primary technical guidance is preferred. A source supports the scope stated here; it does not imply that every possible cause is covered.