Quick answer: If Windows Update fails with 0x800f0993 (or 0x80073712) on a PC that was upgraded to Windows 11 24H2 or 25H2, you’ve likely hit a known issue Microsoft confirmed in June 2026. The upgrade worked, but a leftover update package blocks every later monthly update. Run the DISM command in Fix 1 from an administrator Command Prompt, restart, and try Windows Update again. If that doesn’t work, an in-place upgrade that keeps your files and apps fixes it.
In this guide
What Microsoft says causes it
Microsoft posted this issue on its Windows release health dashboard for IT admins (issue ID WI1317180). That page needs an admin sign-in, so the details below are Microsoft’s statements as quoted by BleepingComputer on June 10, 2026.
| Detail | What Microsoft says |
|---|---|
| Who’s affected | PCs upgraded to Windows 11 24H2 or 25H2 from Windows 10 21H2/22H2 or Windows 11 23H2 |
| Symptom | Monthly updates fail to install after the upgrade |
| Error codes | 0x800f0993 (PSFX_E_REBASE_HYDRATION_CANDIDATES_MISSING) or 0x80073712 (ERROR_SXS_COMPONENT_STORE_CORRUPT) |
| Updates linked to the problem | KB5082200, KB5082052 and KB5079391 |
| Fix for affected PCs | Remove a specific update package with DISM, or do an in-place upgrade |
The names explain a lot. A “rebase hydration candidate” is a file Windows needs to rebuild components when it applies a cumulative update. If those files are missing, the component store looks damaged and the update stops.
This is not the same as a failed upgrade. The upgrade completes, and the PC runs normally until it tries to install the next cumulative update.
Check whether your PC is affected
- Press Windows + R, type
winverand press Enter. Note the version (24H2 or 25H2) and build. - Open Settings > Windows Update > Update history and look for failed cumulative updates with 0x800f0993 or 0x80073712.
- Think back: was this PC upgraded from Windows 10 or from Windows 11 23H2, rather than bought with 24H2 or 25H2 already on it?
If all three fit, use the fixes below in order. Admins on patchmanagement.org (as reported by Borncity) also noticed that affected PCs often show build 10.0.26100.1 in winver. That’s a community observation, not a Microsoft rule, so don’t rely on it alone.
Fix 1: Remove the stuck update package
Microsoft’s workaround removes one leftover rollup package so the component store can be updated again.
- Select Start, type cmd, right-click Command Prompt and choose Run as administrator.
- Copy and paste this command exactly, then press Enter:
dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10- Wait for it to finish. If it asks to restart, type Y.
- After the restart, open Settings > Windows Update and select Check for updates.
A few notes:
- The package name must match character for character. A single typo gives a “package not found” style error.
- If DISM says the package isn’t installed, your PC isn’t stuck on that package, so go to Fix 2.
- To see which update packages are installed before or after, run
dism /online /get-packages /format:table. This tip comes from the admin community, not Microsoft’s notice. - One Borncity reader reported that the same command also cleared error 0x800f0823. That’s a single report, so treat it as worth a try, not a promise.
Fix 2: Do an in-place upgrade
If the DISM command fails or updates still don’t install, Microsoft’s advice is an in-place upgrade. This reinstalls Windows over itself and keeps your files, apps and most settings.
- Back up anything important first. An in-place upgrade is safe in normal use, but a backup costs little.
- Download Windows 11 media from Microsoft’s Windows 11 download page. Use the Installation Assistant, or download the ISO, right-click it and choose Mount.
- Run setup.exe from the mounted drive.
- When asked what to keep, choose Keep personal files and apps.
- Let setup finish and restart a few times, then run Windows Update.
Make sure the media is the same Windows edition and language as your PC, or the keep-files option may be greyed out.
Why newer PCs shouldn’t get it
Microsoft says it applied a fix on its side on May 19, 2026, at 6:30 p.m. PT. From then on, no new devices on Home edition or unmanaged business PCs should get into this state. A restart can help that change reach a PC sooner.
That change prevents new cases only. It doesn’t repair a PC that already has the problem, which is why the fixes above are still needed.
Microsoft also released updates on June 9, 2026 with upgrade protections:
| Windows version | June 9, 2026 update |
|---|---|
| Windows 10 21H2 and 22H2 | KB5094127 |
| Windows 11 23H2 | KB5093998 |
| Windows 11 24H2 and 25H2 | KB5094126 (builds 26100.8655 and 26200.8655) |
If you still have a Windows 10 or 23H2 PC you plan to upgrade, install the latest monthly update first. Managed business PCs should follow their IT team’s process; admins can track the issue in the Microsoft 365 admin center under Windows release health, and public notes are on Windows release health.
If your PC wasn’t upgraded
0x800f0993 has turned up on other PCs too, before this known issue. If your PC came with 24H2 or 25H2 installed, the package fix probably won’t apply. Try the general repairs instead:
- Run
sfc /scannow, thenDISM /Online /Cleanup-Image /RestoreHealth. See how to run SFC /scannow. - Work through Windows Update “Something went wrong” fixes, which covers resetting update components.
- Install the failing update manually; how to force a Windows update shows how.
- If nothing works, the in-place upgrade in Fix 2 is still the cleanest repair.
Related guides
- How to run SFC /scannow in Windows
- Windows Update “Something went wrong”
- How to force a Windows update
- Run Windows Update from the command line
Leave a Reply