Quick Answer — Windows 11 June 2026 Update Failed (0x800f0922)
The June 2026 Windows 11 cumulative update (KB5094126) is failing on many 24H2 and 25H2 PCs — especially ones upgraded from Windows 10 — with error 0x800f0922, 0x80073712 or 0x800f0993. In most cases the real cause is an EFI System Partition (ESP) that ran out of free space, so the new bootloader files cannot be written. The fastest fix: free space on the ESP, then run DISM /Online /Cleanup-Image /RestoreHealth and retry. The full 7-step guide below covers every case, up to a no-data-loss in-place upgrade.
What Is the Windows 11 "Update Failed" Error?
Starting with the June 2026 Patch Tuesday release, a wave of Windows 11 machines began failing the monthly cumulative update. Windows Update downloads the package, reaches "Installing… 100%", then rolls back on reboot with "We couldn't complete the updates — Undoing changes" and one of three error codes in Update history: 0x800f0922, 0x80073712 or 0x800f0993.
Microsoft confirmed the issue: a subset of PCs that were upgraded to Windows 11 24H2 or 25H2 cannot install the latest cumulative update. The underlying problem traces back to the May 2026 servicing stack and an EFI System Partition with insufficient free space — the small hidden FAT32 partition that holds the boot files. When the updater tries to stage new boot components there and the partition is full, servicing aborts and rolls the whole update back.
Which Error Code Did You Get?
All three codes come from the same June 2026 update. The fix overlaps heavily, but here is what each one points at:
| Error code | What it means | Best first fix |
|---|---|---|
0x800f0922 | Update could not be staged/committed — usually a full EFI System Partition | Fix 2 (free ESP space) |
0x80073712 | A component-store file is missing or corrupted | Fix 4 (SFC + DISM) |
0x800f0993 | Update could not be committed during servicing | Fix 3 (remove stuck package) |
Symptoms You'll See
- Update reaches 100%, then on reboot: "Undoing changes made to your computer"
- Update history shows "Failed to install" with
0x800f0922/0x80073712/0x800f0993 - The same KB (e.g. KB5094126) keeps re-appearing and re-failing every reboot
- Windows Update sits at "Restart pending" that never completes
- Disk Management shows a 100 MB EFI System Partition with little or no free space
Don't want to touch the EFI partition yourself?
Editing the boot partition is risky if you mistype a command. Our certified bilingual technicians remote in, free the ESP safely and push the update through — same day, flat rate, no fix no fee.
Common Causes (Why This Happens)
- Full EFI System Partition — the #1 cause of 0x800f0922 in June 2026. Old language and font bootloader files fill the 100 MB ESP.
- Corrupted component store (WinSxS) — a half-applied earlier update left the servicing stack inconsistent (drives 0x80073712).
- Partially staged package from a previous failed attempt that now blocks the retry (drives 0x800f0993).
- Broken Windows Update database in
SoftwareDistribution/catroot2. - Third-party antivirus or disk-encryption locking servicing files mid-install.
- Pending reboot from another app (driver, .NET, Visual C++) blocking the servicing operation.
The 7 Fixes (In Order of Success Rate)
Work through these in order. Fix 1 and Fix 2 resolve the large majority of June 2026 cases. Run every Command Prompt / PowerShell step as Administrator (Win + X → Terminal (Admin)).
Run the Windows Update Troubleshooter (success rate ≈ 25%)
The fastest, safest first move — it clears stuck queues and re-registers update services.
- Open Settings → System → Troubleshoot → Other troubleshooters.
- Next to Windows Update, click Run.
- Let it apply fixes, reboot, then retry the update from Settings → Windows Update → Check for updates.
Free Space on the EFI System Partition (the real 0x800f0922 fix ≈ 45%)
This is the fix that actually clears the June 2026 wave. The 100 MB ESP fills with old font and language bootloader files and leaves no room to stage the new build.
- Open Command Prompt as administrator and mount the ESP to drive S:
mountvol S: /S
S:
cd S:\EFI\Microsoft\Boot\Fonts
dir- Delete the stale font files (these are regenerated automatically and safe to remove):
del *.ttf
cd S:\EFI\Microsoft\Boot
rmdir /S /Q Resources\Custom 2>nul
cd \
mountvol S: /DNow retry Windows Update. If you are unsure which files are safe to delete, stop here and let a technician do it — a mistake on the ESP can stop Windows booting.
Remove the Stuck Update Package with DISM (≈ 12%)
A partially staged package from a failed attempt blocks the retry. List packages, find the June 2026 one stuck in Install Pending, and remove it.
DISM /Online /Get-Packages /Format:TableLook for a package with state Install Pending dated June 2026, copy its full PackageIdentity, then:
DISM /Online /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e35~amd64~~XXXXX
Dism /Online /Cleanup-Image /StartComponentCleanupReboot and retry the update.
Run SFC and DISM RestoreHealth (≈ 9%) — best for 0x80073712
Repairs the component store when a servicing file is missing or corrupted.
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealthLet both finish (DISM can sit at 20% / 62% for several minutes — that's normal). Reboot and retry the update.
Reset Windows Update Components (≈ 5%)
Rebuilds the update database when SoftwareDistribution or catroot2 is corrupted. Run these lines in an elevated prompt:
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 msiserverReboot and check for updates again. Windows rebuilds both folders automatically.
Install the Update Manually from the Microsoft Update Catalog (≈ 2.5%)
Bypasses the Windows Update client entirely by installing the standalone package.
- Go to the Microsoft Update Catalog and search the KB number from your Update history (e.g. KB5094126).
- Download the
.msumatching your build (x64 for most PCs). - Run the
.msu, reboot when prompted.
In-Place Upgrade Repair Install (≈ 1.5%) — keeps all your files
The nuclear option that rebuilds Windows without wiping anything. Resolves nearly every stubborn 0x800f0922 case.
- Download the official Windows 11 ISO from microsoft.com/software-download/windows11.
- Double-click the ISO to mount it, then run
setup.exe. - Choose Keep personal files and apps and let it run (30–60 min).
Your files, installed programs and settings are preserved — only the Windows system files are replaced, which clears the corrupted servicing state for good.
Advanced Diagnostics: Read the CBS Log
To see exactly what failed, open the Component-Based Servicing log:
C:\Windows\Logs\CBS\CBS.log
Open it in Notepad, press Ctrl + End to jump to the latest run, and search upward for Error. Common lines and the fix they map to:
- "Failed to... ESP" / "not enough space" → Fix 2 (free the EFI partition)
- "Cannot find / corrupt payload" / 0x80073712 → Fix 4 (SFC + DISM RestoreHealth)
- "Install Pending" / cannot commit → Fix 3 (remove the stuck package)
- "Access is denied" / 0x80070005 → disable third-party antivirus, then Fix 5
Update Still Failing After All 7 Fixes?
IT Cares technicians remote into your PC, read the CBS log, free the EFI partition safely and push the June 2026 update through on the spot — usually under 30 minutes. Flat rate, no fix no fee.
Common Mistakes to Avoid
- Don't keep hitting "Retry" all day. If the ESP is full, every attempt fails the same way. Fix the cause (Fix 2) first.
- Don't delete random files from the EFI partition. Only the stale fonts and old custom boot resources are safe — never touch
bootmgfw.efior theBootBCD store. - Don't run a clean install before trying the in-place upgrade. Fix 7 keeps your data and solves the same problem.
- Don't disable Windows Update permanently. The June 2026 update carries security patches — fix it, don't bury it.
- Don't skip the reboot between fixes. Servicing needs a clean restart to release pending operations.
How to Prevent Update Failures Going Forward
- Keep at least 15 GB free on your system drive before each monthly update.
- Run
DISM /Online /Cleanup-Image /StartComponentCleanupevery few months to keep WinSxS healthy. - If you upgraded from Windows 10, check your EFI partition size — the old 100 MB ESP is the usual culprit; a clean 24H2/25H2 install uses a larger one.
- Pause feature updates for a week after Patch Tuesday so known-bad builds get patched before you install.
- Keep a current backup (File History or a full image) before every major update.
Related Windows Errors We Cover
- Windows Won't Boot After an Update — Recovery Guide
- Chrome STATUS_BREAKPOINT Error
- Chrome Keeps Crashing on Windows 11 — Fix
- Wi-Fi Not Working After a Windows Update
- Full error code library →
Frequently Asked Questions
What does Windows update error 0x800f0922 mean?
0x800f0922 means the update could not be staged or committed. In the June 2026 Windows 11 wave the most common trigger is an EFI System Partition that ran out of free space, so the bootloader files for the new build cannot be written. Freeing ESP space or removing the stuck package with DISM resolves it.
Will I lose my files if the update keeps failing?
No. A failed update rolls back automatically and leaves your previous working build, apps and personal files untouched. Even the in-place upgrade repair install (Fix 7) keeps your files, apps and settings — it only replaces the Windows system files.
Is it safe to skip the June 2026 Windows 11 update?
You can pause it for up to 5 weeks from Settings, but don't skip it permanently — KB5094126 contains security fixes. Pause it only long enough to free EFI space or apply the fixes above, then install it.
How do I fix a full EFI System Partition?
Open an elevated Command Prompt, run mountvol S: /S, delete the stale fonts under S:\EFI\Microsoft\Boot\Fonts, run mountvol S: /D to unmount, then retry the update. If you're not comfortable editing the ESP, a technician can do it remotely in minutes.
Which Windows 11 versions are affected?
Microsoft confirmed that PCs upgraded to Windows 11 24H2 or 25H2 — especially machines upgraded from Windows 10 — may fail to install the June 2026 cumulative update with 0x800f0922, 0x80073712 or 0x800f0993. Clean installs are far less affected.
What's the difference between 0x800f0922, 0x80073712 and 0x800f0993?
All three are servicing-stack errors for the same June 2026 update. 0x800f0922 is usually a staging/ESP-space failure, 0x80073712 a missing or corrupt component-store file, and 0x800f0993 a commit failure. The fixes overlap — DISM RestoreHealth plus freeing ESP space resolves the large majority.
Do I need to reinstall Windows to fix this?
Almost never. A clean reinstall is the last resort. The in-place upgrade repair install (Fix 7) rebuilds Windows while keeping your files, apps and settings, and resolves nearly every stubborn 0x800f0922 case without data loss.
How long does the fix take?
The DISM cleanup and update-component reset take 5–15 minutes. Freeing the EFI partition takes 2–3 minutes. An in-place upgrade repair install takes 30–60 minutes depending on your PC and internet speed. Book a remote session or call (888) 711-9428 if you'd rather have it done for you.
Comments
Got the 0x800f0922 / 0x80073712 error on your PC? Tell us which fix worked below.
Leave a Comment