← ClaudeAtlas

0x80073712-windows-update-component-st-027af8b220bff22elisted

Fixes Windows Update error 0x80073712, where the component store is corrupt and updates cannot stage. Use when DISM reports store corruption alongside update failures. Not for a download-only failure on a store that DISM reports as healthy.
Vectle/skills · ★ 0 · Web & Frontend · score 65
Install: claude install-skill Vectle/skills
## TL;DR Error 0x80073712 is a clear component store corruption verdict: a manifest or catalog the update needs is missing or damaged. Repair in order - DISM RestoreHealth with a matching source if online repair stalls, then SFC, then the update again. If DISM reports the store is not repairable, stop patching attempts and plan an in-place repair install or restore, because further update retries cannot succeed. ```text 0x80073712 windows update component store corrupt how to fix ``` ## Use this when - Updates fail with 0x80073712 and DISM CheckHealth flags the store as repairable or corrupt. - CBS.log shows missing manifest or catalog entries for installed packages. - Several unrelated updates fail with the same code, pointing below individual packages. ## Not for this skill when - Only one optional feature or language pack fails to add. That can be a source availability issue rather than store corruption. - The store checks clean and one KB fails with a different code. Follow that code instead. ## Steps 1. Back up anything critical on the machine and record the Windows build and edition, because store corruption repairs and any fallback repair install both depend on matching the current release exactly. Verify: a backup exists and the build and edition are documented before servicing changes begin 2. Run DISM CheckHealth, ScanHealth, and RestoreHealth in that order from an elevated terminal, saving the DISM.log after each stage. Note whether ScanHealth calls the store r