Windows · Windows Server · medium · Core Windows faults

0x80073712 / 0x800f081f — component store corruption or missing source

Windows Update or a feature install cannot find the payload it needs. Either the component store is damaged, or the source it would repair from is unreachable.

What you see

Updates fail with 0x80073712 or 0x80073701. Adding .NET 3.5 or another optional feature fails with 0x800f081f. CBS.log shows entries about a missing payload or a corrupt manifest.

What is actually wrong

The WinSxS component store is missing or has a damaged copy of a file. DISM normally repairs it from Windows Update, so this also appears on machines with restricted internet, WSUS pointing at the wrong place, or an ISO of the wrong build.

Codes and articles

0x800737120x800f081f0x800f08310x80073701CBS_E_SOURCE_MISSINGKB947821

Fixes (2)

Repair the component store from Windows Update

Elevated PowerShell15–40 minuteslow riskreversible

The machine can reach Windows Update. Run the steps in this order — SFC before a successful DISM repair often cannot fix anything, because SFC repairs from the very store that is damaged.

Check whether the store reports damage.
PowerShell
```
DISM /Online /Cleanup-Image /ScanHealth
```
Repair it. This is the slow one — it can sit at 20% for several minutes without being stuck.
PowerShell
```
DISM /Online /Cleanup-Image /RestoreHealth
```
RestoreHealth pulls known-good copies of the damaged components from Windows Update and rebuilds the store.
Now run the system file check, which repairs from the store you just fixed.
PowerShell
```
sfc /scannow
```
Restart, then retry the update or the feature install.

Confirm it workedScanHealth reports no component store corruption.

PowerShell

DISM /Online /Cleanup-Image /ScanHealth

If you need to undo itNone needed — these operations repair in place and do not remove installed software.

Repair from a mounted ISO instead

Elevated PowerShell20–40 minuteslow riskreversible

No path to Windows Update, or WSUS is intercepting and does not carry the payload. The ISO build must match the installed build.

Download the ISO for exactly the build installed. Check what that is first.
PowerShell
```
Get-ComputerInfo -Property OsName, OsVersion, OsBuildNumber
```
DISM refuses a source from a different build, and a mismatched source is the most common reason this fix appears not to work.
Mount the ISO and note the drive letter it gets.
PowerShell
```
Mount-DiskImage -ImagePath C:\iso\windows.iso
```
Point DISM at install.wim inside it. Index 1 is usually correct; check with Get-WindowsImage if the repair reports the wrong edition.
PowerShell
```
DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:E:\sources\install.wim:1 /LimitAccess
```
/LimitAccess stops DISM falling back to Windows Update, which is what makes the failure explicit rather than silent.
Run SFC afterwards.
PowerShell
```
sfc /scannow
```

Unmount the ISO.

PowerShell

Dismount-DiskImage -ImagePath C:\iso\windows.iso

Confirm it workedThe feature installs, or the update applies. CBS.log has no new payload-missing entries.

PowerShell

Select-String -Path C:\Windows\Logs\CBS\CBS.log -Pattern 'payload|corrupt' | Select-Object -Last 20

If you need to undo itNone needed.

Reference

Repair a Windows Image — Microsoft Learn ↗

Related faults

Where this stops. This write-up was written and checked by hand. It says what each step changes, how to confirm it worked and how to reverse it, and anything destructive is flagged before you reach it. If it does not match what your machine is doing, search the Support Centre for the exact code or message — and when something needs a person, get in touch.