Fix Error 0x80073712 on Windows 10 PC

Error 0x80073712 on Windows 10 means that a required Windows component or system file is missing or corrupted, usually during a Windows Update. The most reliable fix is to run the built-in DISM and SFC tools in a specific order, then restart and try the update again.

What Causes Error 0x80073712?

This error code is tied to the Windows Component Store (WinSxS), a hidden folder that holds all system files, DLLs, and components needed for updates and feature installations. When Windows Update tries to modify or add a component, it checks that the source files in the component store are intact. If a file is missing, damaged, or has been altered by a third-party cleanup tool, the update fails and you see 0x80073712.

Common triggers include:

Interrupted updates (power loss, forced shutdown, or network drop)
Disk space exhaustion on the system drive
Antivirus or security software that quarantines system files
Manual deletion of files in the WinSxS folder (which you should never do)
Corrupted update cache or pending.xml file

Before You Start: Backup and Check Disk Space

Creating a restore point or backup is a good safety step before running system repairs, though the built-in tools are generally safe. Also, ensure your system drive (usually C:) has at least 10-15 GB of free space. Updates need room to stage files and roll back if something goes wrong. If disk space is low, delete temporary files using the Storage Sense feature (Settings > System > Storage) or the Disk Cleanup utility.

Step-by-Step: Run DISM First, Then SFC

Run these commands in an elevated Command Prompt. To open it, right-click the Start button and select Command Prompt (Admin) or Windows PowerShell (Admin).

Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This repairs the component store using Windows Update as the source. It can take 15-30 minutes.
When DISM finishes (it may say “The restore operation completed successfully”), run sfc /scannow. This scans all protected system files and replaces corrupted ones.
Restart your PC and attempt the Windows Update again.

If DISM fails because Windows Update itself is broken, you can point it to a local source, like a Windows 10 ISO or installation media. Mount the ISO, note the drive letter (e.g., E:), and run:

DISM /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim /LimitAccess

If you only have an install.esd file, you’ll need to extract the index number first using DISM /Get-WimInfo /WimFile:E:\sources\install.esd, then use that index in the source path.

If SFC and DISM Don’t Fix It

Sometimes the corruption is deeper, or the update cache itself is problematic. Try these in order:

Reset Windows Update components – Stop the BITS, Windows Update, and Cryptographic services, rename the SoftwareDistribution and Catroot2 folders, then restart the services. This clears the update cache. There are many scripts online, but you can do it manually with these commands in an admin Command Prompt:

net stop wuauserv
net stop cryptSvc
net stop bits
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old
net start wuauserv
net start cryptSvc
net start bits

Run the Windows Update Troubleshooter – Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters, select Windows Update, and run it.
Use the Media Creation Tool to upgrade in place – Download the Windows 10 Media Creation Tool from Microsoft, run it, and choose “Upgrade this PC now.” This reinstalls Windows while keeping your files and apps, and it often fixes stubborn update issues.
Perform a repair install – If the above fails, a repair install (using the ISO or Media Creation Tool) is the next step. It’s not a full reset; it preserves personal files and installed programs.

Common Mistakes and Misconceptions

Many users run SFC first and only once. SFC alone often can’t fix the underlying component store corruption; DISM must run first. Also, running SFC multiple times without DISM won’t help if the source files are damaged.

Another misconception is that deleting the WinSxS folder will free space and solve the problem. It won’t – it will break Windows completely. Use the built-in Disk Cleanup or the DISM /StartComponentCleanup command instead (run in admin Command Prompt) to safely remove superseded components.

Some third-party “system cleaner” tools may claim to fix this error, but they often cause further corruption. Stick with the built-in tools.

When to Consider a Full Reset

If you’ve tried DISM, SFC, resetting update components, and the in-place upgrade, and the error persists, a full reset may be the last option. Go to Settings > Update & Security > Recovery > Reset this PC. You can choose to keep your personal files, but you’ll need to reinstall applications. This is a drastic step, so try everything else first.

Frequently Asked Questions

Will error 0x80073712 damage my PC?

No, it only prevents updates from installing. Your PC remains usable, but you won’t receive security patches until the issue is resolved, so it’s best to fix it promptly.

How long does DISM take?

Typically 15-30 minutes, but it can take longer on slow systems or if the component store is severely corrupted. Let it finish; don’t interrupt it.

Can I run SFC in Safe Mode?

Yes, but it’s not necessary. If SFC fails in normal mode, running it in Safe Mode (with Networking) can sometimes help if a driver or service is interfering.

What if DISM says “The source files could not be found”?

That means it can’t reach Windows Update or the local source is invalid. Ensure your internet is working, or use the /Source option with a valid install.wim from an ISO.

Is there a way to prevent this error in the future?

Keep your system drive with adequate free space, avoid forcibly shutting down during updates, and don’t use third-party cleaners that touch system files. Also, run Windows Update regularly to keep components fresh.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →