Fix Windows 11 Update Errors 0x80073712 and 0x800f0993 on 24H2 and 25H2

If your June 2026 cumulative update keeps failing with error 0x80073712 or 0x800f0993, you are not alone. Microsoft has confirmed that a subset of Windows 11 PCs cannot install monthly updates, and there is an official fix you can run yourself.

The errors come from a damaged component store left behind by an in-place upgrade, not failing hardware, so a few DISM commands almost always clear it.

Key takeaways

• Both errors trace to a corrupted servicing (component) store, usually on PCs that were upgraded rather than clean-installed.
• The primary fix is removing the leftover rollup package with DISM.
• If removal fails, repair the store with DISM /RestoreHealth then sfc /scannow, budget 15 to 30 minutes.
• Clearing the SoftwareDistribution cache resets a stalled download.
• An in-place upgrade (repair install) is the documented last resort and preserves files and apps.

Who is affected

Microsoft says the problem hits a small percentage of devices that took an upgrade path rather than a clean install. Specifically, machines originally on Windows 10 (versions 22H2 or 21H2) or Windows 11 version 23H2, later upgraded to Windows 11 version 24H2 or 25H2, may fail to install the latest cumulative update.

On affected systems, Windows Update downloads the package but the install rolls back, leaving one of these error codes in the update history.

The fixes form a clear ladder from least to most disruptive. Try them in this order and stop when the update installs:

Fix	When to use it	Time	Data risk
DISM remove-package	First, the official mitigation	~5 min	None
RestoreHealth + sfc	If the package is not found or removal fails	15-30 min	None
Clear SoftwareDistribution	If the download stalls after a store repair	~5 min	None
In-place upgrade	Last resort, store still corrupt	30-60 min	Low (back up first)

What the error codes mean

• 0x80073712 is ERROR_SXS_COMPONENT_STORE_CORRUPT. The Windows servicing store, which tracks every installed component, has become inconsistent, so the system cannot validate new packages.
• 0x800f0993 is a servicing-stack failure tied to the update engine's handling of PSFX, Microsoft's differential (patch-based) update technology. It usually appears alongside 0x80073712 when Windows hits a corrupt manifest or missing catalog during install.

The official fix: remove the affected package

Microsoft's primary mitigation is to remove the leftover rollup package with DISM. You will need an elevated Command Prompt.

1. Click Start, type cmd, right-click Command Prompt, and choose Run as administrator.
2. Run the following command exactly as written:

dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10

3. Wait for DISM to finish, then reboot when prompted.
4. Open Settings > Windows Update and click Check for updates. The cumulative update should now install.

If removal does not work: repair the component store

When package removal does not clear the error, repair the servicing store directly. In the same elevated Command Prompt, run these in order and let each complete:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

RestoreHealth scans the store and replaces corrupted files with good copies pulled from Windows Update, typically taking 15 to 30 minutes depending on your connection and the level of corruption. sfc /scannow then checks protected system files against that repaired store. Reboot and try the update again.

If RestoreHealth itself fails (a common outcome on a badly corrupted store with code 0x800f081f), it usually means Windows cannot find good replacement files online. The fix is to point DISM at a known-good source instead. Mount a matching Windows 11 ISO (the same edition and version as your install), note the drive letter it gets, and run DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:X:\sources\install.wim:1 /LimitAccess, replacing X with that drive letter. This forces DISM to repair from the ISO's clean component store rather than Windows Update, which sidesteps the chicken-and-egg problem of a broken update engine trying to download its own repair files. Once that succeeds, re-run sfc /scannow and try the cumulative update again.

Clear the update cache as a follow-up

If the update still stalls, reset the Windows Update components. Run these one at a time in the elevated prompt:

net stop wuauserv
net stop bits
ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
net start wuauserv
net start bits

This forces Windows to rebuild its download cache. Check for updates one more time. If a different code such as 0x800f0922 appears instead, that one is usually a full EFI partition rather than store corruption, our guide to update error 0x800f0922 and the EFI partition trap covers it.

Last resort: in-place upgrade

If none of the above works, Microsoft's documented fallback is an in-place upgrade (sometimes called a repair install). Download the Windows 11 Installation Assistant or the latest ISO from Microsoft, run setup.exe from inside Windows, and choose to keep personal files and apps. This rebuilds system files without wiping your data and almost always clears stubborn servicing-store corruption.

A note on the related Recycle Bin bug

While troubleshooting, you may notice a cosmetic side effect from the June 9, 2026 update (KB5094126): permanently deleting a single item shows an internal name like $Rxxxxx.ext in the confirmation dialog instead of the real filename. This is harmless, the file restores correctly, and Microsoft fixed it in updates released June 23, 2026 (KB5095093) and later. Installing the newest cumulative update resolves it.

Bottom line

These errors come from a corrupted component store on upgraded machines, not from your hardware. Start with the DISM package removal, fall back to RestoreHealth and sfc, and keep the in-place upgrade in your back pocket. Once the store is healthy again, future Patch Tuesday updates install normally. If a recent update also knocked out a device like Bluetooth, the broader fix for Bluetooth not working on Windows 11 gets that radio back.

Frequently asked questions

Why do these errors only hit upgraded PCs and not clean installs?

In-place upgrades carry forward the old servicing store, and a manifest or catalog can be left inconsistent in the process. Clean installs build a fresh store, so they rarely hit 0x80073712 or 0x800f0993.

Is it safe to delete the SoftwareDistribution folder?

You are renaming it, not deleting it, and only after stopping the update services. Windows rebuilds a fresh copy automatically. The old one stays as SoftwareDistribution.old and can be removed later once updates work.

How long does DISM /RestoreHealth take?

Usually 15 to 30 minutes, depending on your internet speed and how damaged the store is. It can appear to hang around 20 percent, that is normal. Let it finish rather than closing the window.

Will an in-place upgrade erase my files?

No, as long as you choose the option to keep personal files and apps. It rebuilds system files while leaving your data, programs, and most settings intact. Still, back up anything important first as a precaution.