Microsoft documents two primary causes for Windows Update error 0x800f0922 (CBS_E_INSTALLERS_FAILED): an active VPN or proxy blocking Windows Update server connections, or insufficient free space inside the hidden System Reserved / EFI System Partition (often appearing when an update rolls back at 98–99% with ‘We couldn’t complete the updates’). Disconnect any VPN first, enable .NET Framework 3.5/4.8 in Windows Features, clear SoftwareDistribution and run DISM/SFC, and check EFI partition free space if the update reverts during reboot.
At a glance
- Applies to
- Windows 11 and Windows 10 cumulative updates, feature upgrades & .NET
- Fails immediately?
- Disconnect active VPN/proxy & check App Readiness / .NET features
- Reverts at 98–99%?
- System Reserved / EFI partition has < 15 MB free space for boot/DBX files
- Before partition edits
- Back up personal files and BitLocker recovery keys first
Provenance
- Nov 21, 2026Published
Inside Windows’ Component-Based Servicing (CBS) engine, 0x800f0922 translates to CBS_E_INSTALLERS_FAILED: the update downloaded fine, unpacked its files, and then one of its internal post-unpack installers failed—often forcing that agonizing “We couldn’t complete the updates. Undoing changes” rollback at 98% or 99%.
Microsoft’s official Windows upgrade error reference points to two main causes—an active VPN connection or too little free space in the System Reserved / EFI partition—and field troubleshooting adds two fast software checks (AppReadiness service and .NET features) that take two minutes before you touch any partition.
Step 1. Disconnect VPNs and verify App Readiness + .NET Framework (3 minutes)
Work the zero-risk checks first:
- Disconnect and fully exit any VPN or proxy client: close corporate VPNs (Cisco AnyConnect, GlobalProtect, FortiClient) and consumer WireGuard/OpenVPN clients from the system tray—not just paused—before clicking Retry in Windows Update. Ensure your C: drive also has at least 20 GB of regular free space.
- Check that
App Readinesswasn’t disabled by a tweak script: if you previously ran a third-party Windows “debloater” (see our safe Windows 11 debloat guide for what never to disable), pressWin + R, runservices.msc, double-click App Readiness, and set Startup type to Manual (neverDisabled). Confirm Windows Update and Background Intelligent Transfer Service (BITS) are also enabled. - Turn on
.NET Framework 3.5and4.8 Advanced Services: pressWin + R, runoptionalfeatures.exe, ensure both .NET Framework 3.5 (includes .NET 2.0 and 3.0) and .NET Framework 4.8 Advanced Services are checked, click OK, and restart if Windows installs missing components.
Step 2. Repair the component store (DISM / SFC) and clear SoftwareDistribution
If a previous interrupted update left half-staged servicing manifests behind, clear the download cache and repair the image from Command Prompt (Admin) (Microsoft’s Windows Update troubleshooting steps):
DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow
Once both reach 100%, flush stale update downloads:
net stop wuauserv
net stop bits
del /f /s /q %windir%\SoftwareDistribution\Download\*
net start bits
net start wuauserv
Restart your PC and test Settings > Windows Update > Check for updates.
Step 3. Check if the 100 MB EFI / System Reserved partition is full
Did the update still fail at 98%–99% during restart (or display “We couldn’t update the system reserved partition” alongside 0x800f0922 or 0xc1900104)?
Monthly Windows 11 and Windows 10 cumulative updates regularly update bootmgfw.efi and append Secure Boot DBX revocation signatures inside your tiny 100 MB EFI System Partition (ESP). On OEM laptops and prebuilts (especially HP, Dell, and Lenovo machines whose BIOS updater leaves megabytes of old firmware logs inside EFI\HP\ or EFI\Dell\), free space on that 100 MB partition drops under 15 MB and blocks the installer!
How to inspect EFI free space safely (read-only check first)
Press
Win + R, typediskmgmt.msc, and press Enter.Right-click Disk 0 (your Windows boot drive) -> Properties -> Volumes tab and check Partition style:
GUID Partition Table (GPT)(almost all UEFI Windows 11 PCs; see Secure Boot & GPT check): uses a100 MB(or260 MB) FAT32 EFI System Partition.Master Boot Record (MBR)(older legacy Windows 10 installs): uses an NTFS System Reserved partition.
On a UEFI / GPT PC, open Command Prompt as Administrator and temporarily mount the EFI System Partition to drive letter
Y:to see what is filling it without deleting anything yet:mountvol Y: /s dir Y:\ /a dir Y:\EFILook at the
bytes freeline at the bottom ofdir Y:\ /a:- If
25,000,000 bytes free(25+ MB) or more is available: your EFI partition is not full! Unmount it right away withmountvol Y: /dand checkC:\Windows\Logs\CBS\CBS.log(search from the bottom for, Errorright above0x800f0922to see which specific CBS component failed). - If under
15 MB(15,000,000 bytes) is free: you found the exact bottleneck!
- If
Safe ways to reclaim space on a full EFI System Partition
Caution: Never delete
Y:\EFI\Microsoft\Boot\bootmgfw.efiorBCD—corrupting the EFI boot folder will stop Windows from booting. Back up personal files and save your BitLocker recovery key before modifying anything onY:.
- Check vendor BIOS staging folders first (
Y:\EFI\HP\,Y:\EFI\Dell\BIOS\, etc.): OEM BIOS update utilities frequently leave old.bincapsule backups or diagnostic logs (15–40 MB) insideY:\EFI\<Vendor>\DEVFW\orBIOS\Previous\. Copying those old OEM log/backup files to a folder onC:\EFI-Backup\before removing them fromY:often frees30+ MBwithout touching a single Microsoft boot file. - Unused boot-screen font files (
Y:\EFI\Microsoft\Boot\Fonts\): on English-language installs with a100 MBEFI partition where no OEM bloat exists, Microsoft’s documented space-relief workaround backs upY:\EFI\Microsoft\Boot\Fonts\*.*toC:\EFI-Fonts-Backup\and clears unused multi-megabyte CJK boot-menu fonts (chs_boot.ttf,cht_boot.ttf,jpn_boot.ttf,kor_boot.ttf) to free ~13–15 MBfor the servicing update. - Always unmount
Y:when finished:Reboot once and re-run Windows Update. (Note: if your error wasmountvol Y: /d0x80070643on the larger500 MBRecovery partition at the end of the disk rather than0x800f0922on the EFI partition, use our KB50289970x80070643WinRE partition guide instead.)
Frequently asked questions
What causes Windows Update error 0x800f0922?
Why does my update reach 98% or 99% and say ‘We couldn’t complete the updates. Undoing changes’?
How is error 0x800f0922 different from error 0x80070643?
Why would a VPN trigger error 0x800f0922 when the update already downloaded to 100%?
Can a disabled Windows service cause 0x800f0922?
Sources and corrections
- Last updated
- Methodology
- See our methodology for research and review standards. It draws on 4 cited sources, listed below, each checked against the original page on the date above. Microsoft’s official two-cause explanation for 0x800F0922 (VPN connection interference and System Reserved partition free space) comes directly from Microsoft Support’s ‘Get help with Windows upgrade and installation errors’ table opened November 21, 2026 (UTC), paired with Microsoft Support’s Windows Update cache reset and System File Checker documentation.
- Sources
- Microsoft Support: Get help with Windows upgrade and installation errors (0x800F0922 section) accessed 2026-11-21
- Microsoft Support: Troubleshoot problems updating Windows accessed 2026-11-21
- Microsoft Support: 'We couldn't update system reserved partition' error installing Windows accessed 2026-11-21
- Microsoft Support: Using System File Checker in Windows accessed 2026-11-21
- Corrections
- Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.