0X80073712
What it means
A file Windows needs for the update is missing or corrupted in the component store.
Quick fix steps
- Run "DISM /Online /Cleanup-Image /RestoreHealth" from an admin Command Prompt.
- Follow up with "sfc /scannow" to repair system files.
- Restart and retry the update.
For the full step-by-step walkthrough, see An Update Keeps Failing and Reinstalling.
Frequently Asked Questions
Is this different from a normal "file corrupted" error?
It's more specific — this points to a component in the Windows servicing store (the system that tracks what's installed) being damaged, which is exactly what DISM /RestoreHealth is designed to repair.
Do I need internet access for the DISM fix to work?
By default, yes — DISM pulls replacement files from Windows Update. Without internet access, you'd need to specify a Windows installation source manually instead.
Other error codes
0X80070002 — File Not Found
Windows Update can't find a file it expects, usually because the update cache is corrupted or a required file was deleted.
0X8024402F — Update Client Received Invalid Response
Windows Update can't properly connect to Microsoft's update servers — usually a network, proxy, or DNS issue rather than anything wrong with the update itself.
0X800F0922 — Update Failed to Install (SSL/Reserved Space)
Often caused by low disk space, a VPN interfering with the connection, or an .NET Framework update conflict.
0X80070003 — Path Not Found
Similar to 0x80070002 — Windows Update can't locate an expected file path, usually from a corrupted update cache.