Fix Windows Update Errors 0x80073712 and 0x800f0993: A Practical Troubleshooting Guide

If you’ve been staring at a failed Windows 11 update screen showing either 0x80073712 or 0x800f0993, you’re not alone. These two error codes have been cropping up more frequently in community reports, and they demand fundamentally different approaches. One requires a surgical repair of the system image; the other needs you to play detective with the update package itself.

What the error codes reveal

Windows Update errors are cryptic by design, but these two stand apart. Error 0x80073712 points to a corrupted component store — the vast Windows Side-by-Side (WinSxS) repository that holds every system file needed for installation and servicing. When this store is damaged, any attempt to install updates can fail with this code. Think of it as a broken spare-parts bin: Windows can’t find the correct files to swap in during an update.

Error 0x800f0993, by contrast, is typically about the update package itself. It usually signals that the specific cumulative or feature update can’t be processed because it’s incomplete, has a messed-up digital signature, or is missing a prerequisite. In many cases, the operating system itself is fine, but the delivery of the update went sideways.

Why you’re seeing these errors now

Windows 11’s servicing model relies on cumulative updates that arrive monthly. Each update touches dozens of system files, and even a tiny hiccup during download or installation can cascade into trouble. The component store is particularly vulnerable because it sits at the heart of every update transaction — a single flipped bit from a power outage or a faulty driver can leave it inconsistent.

Error 0x800f0993 tends to spike when a new update first rolls out and servers are under strain, leading to incomplete downloads. It also appears if you’re using a metered connection that interrupts the download, or if a pre-existing prerequisite — like a servicing stack update (SSU) — was never applied. Microsoft sometimes requires specific SSUs before a cumulative update can install, and the Windows Update engine may not always highlight that dependency clearly.

Many users have reported these errors after attempting to install the latest Patch Tuesday updates for Windows 11, versions 22H2 and 23H2. While Microsoft hasn’t issued a specific advisory for either code, the patterns in forums like Microsoft Answers and Reddit suggest they are widespread enough to warrant a structured repair workflow.

How to fix error 0x80073712

When the component store is corrupt, your primary weapon is the Deployment Image Servicing and Management (DISM) tool. It can scan the store and repair it using a known-good source — either Windows Update itself or a local installation media.

Run DISM and SFC

Open Windows Terminal as Administrator and execute the following commands sequentially.

1. Repair the component store:
   DISM /Online /Cleanup-Image /RestoreHealth
   This command can take 10–30 minutes. It will download any needed files from Windows Update by default. If you’re offline or the download fails, you can specify a local source using /Source with a mounted ISO or an online image.

2. Verify system file integrity:
   SFC /scannow
   System File Checker double-checks that critical files are in place and corrects them using the now-repaired store.

3. Restart and try Windows Update again.

If DISM fails

Sometimes DISM itself gets stuck. If you see error 0x800f081f (“The source files could not be found”), you’ll need to provide a local repair source.

• Download the Windows 11 ISO that matches your installed version and architecture from Microsoft’s official site.
• Mount the ISO (right-click, Mount).
• Note the drive letter assigned (e.g., D:).
• Run DISM with the /Source option:
  DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim /LimitAccess
  Replace D: with your actual drive letter.

After a successful DISM repair, retry the update. This resolves 0x80073712 in the vast majority of cases. If it doesn’t, a deeper disk check is warranted — open a command prompt and run chkdsk C: /f /r to fix file system errors that might be sabotaging the component store.

How to fix error 0x800f0993

Because this error is update-specific, you’ll need to pinpoint exactly which update failed and examine its prerequisites.

Identify the failed KB

• Go to Settings > Windows Update > Update history.
• Under “Quality Updates,” look for a recently failed entry. The KB number is listed there (e.g., KB5034123).
• If nothing appears, open Event Viewer, navigate to Windows Logs > System, filter for Source: WindowsUpdateClient, and look for error events that mention the KB.

Download and install manually

Often, the automatic delivery is the problem. A manual download from the Microsoft Update Catalog bypasses any delivery glitches.

1. Head to catalog.update.microsoft.com.
2. Search for the KB number.
3. Download the correct version for your system (x64 or ARM64, usually).
4. Double-click the .msu file to install.

If the installation fails again, the missing prerequisite theory gains weight.

Check for prerequisites

Some cumulative updates demand a specific Servicing Stack Update. Look at the KB article for the failing update — Microsoft’s support pages for each KB note mandatory prerequisites near the top. Install any listed prerequisite manually, then retry the main update.

Reset Windows Update components

A corrupted local cache can also cause 0x800f0993. Reset the update mechanism:

• Open Command Prompt as Administrator and run these commands:
  net stop wuauserv net stop cryptSvc net stop bits net stop msiserver ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 catroot2.old net start wuauserv net start cryptSvc net start bits net start msiserver
• Restart and try Windows Update again.

Use the Windows Update Troubleshooter

Windows includes a built-in troubleshooter that can detect and fix delivery issues. Go to Settings > System > Troubleshoot > Other troubleshooters, run the Windows Update one. It’s not magic, but it can clean up leftover files.

Last resort: In-place upgrade repair

If both errors remain stubborn, an in-place upgrade repair installs Windows 11 over itself while keeping your apps and files. This refreshes the entire servicing stack and component store.

• Download the Windows 11 Installation Assistant or an ISO from Microsoft.
• Run Setup.exe.
• Choose Keep personal files and apps.

The process takes about an hour and fixes both 0x80073712 and 0x800f0993 by replacing every system file.

What to do if nothing works

If you’ve exhausted all the steps and still hit a wall, consider a clean install as a nuclear option. Back up your data, create a USB installer with the Media Creation Tool, and start from scratch. It’s drastic, but it guarantees a fresh servicing state.

Outlook

Microsoft rarely comments on individual update error codes, but each monthly update tweaks the servicing engine. Future Windows 11 releases may quietly improve resilience against component store corruption and better handle prerequisite checks. For now, knowing which code means what — and having the right repair sequence — can turn hours of frustration into a 30-minute fix. Keep this guide bookmarked; the next Patch Tuesday inevitably brings new codes, but the underlying strategies rarely change.