Quick answer

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.

Fix steps

3 steps

Diagnostic workbench

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:

  1. 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.
  2. Check that App Readiness wasn’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), press Win + R, run services.msc, double-click App Readiness, and set Startup type to Manual (never Disabled). Confirm Windows Update and Background Intelligent Transfer Service (BITS) are also enabled.
  3. Turn on .NET Framework 3.5 and 4.8 Advanced Services: press Win + R, run optionalfeatures.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)

  1. Press Win + R, type diskmgmt.msc, and press Enter.

  2. 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 a 100 MB (or 260 MB) FAT32 EFI System Partition.
    • Master Boot Record (MBR) (older legacy Windows 10 installs): uses an NTFS System Reserved partition.
  3. 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:\EFI
    

    Look at the bytes free line at the bottom of dir Y:\ /a:

    • If 25,000,000 bytes free (25+ MB) or more is available: your EFI partition is not full! Unmount it right away with mountvol Y: /d and check C:\Windows\Logs\CBS\CBS.log (search from the bottom for , Error right above 0x800f0922 to see which specific CBS component failed).
    • If under 15 MB (15,000,000 bytes) is free: you found the exact bottleneck!

Safe ways to reclaim space on a full EFI System Partition

Caution: Never delete Y:\EFI\Microsoft\Boot\bootmgfw.efi or BCD—corrupting the EFI boot folder will stop Windows from booting. Back up personal files and save your BitLocker recovery key before modifying anything on Y:.

  1. Check vendor BIOS staging folders first (Y:\EFI\HP\, Y:\EFI\Dell\BIOS\, etc.): OEM BIOS update utilities frequently leave old .bin capsule backups or diagnostic logs (15–40 MB) inside Y:\EFI\<Vendor>\DEVFW\ or BIOS\Previous\. Copying those old OEM log/backup files to a folder on C:\EFI-Backup\ before removing them from Y: often frees 30+ MB without touching a single Microsoft boot file.
  2. Unused boot-screen font files (Y:\EFI\Microsoft\Boot\Fonts\): on English-language installs with a 100 MB EFI partition where no OEM bloat exists, Microsoft’s documented space-relief workaround backs up Y:\EFI\Microsoft\Boot\Fonts\*.* to C:\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 MB for the servicing update.
  3. Always unmount Y: when finished:
    mountvol Y: /d
    
    Reboot once and re-run Windows Update. (Note: if your error was 0x80070643 on the larger 500 MB Recovery partition at the end of the disk rather than 0x800f0922 on the EFI partition, use our KB5028997 0x80070643 WinRE partition guide instead.)

Frequently asked questions

What causes Windows Update error 0x800f0922?
In Windows’ Component-Based Servicing stack, 0x800f0922 maps to CBS_E_INSTALLERS_FAILED—an advanced installer failed during update staging or reboot commit. Microsoft’s official upgrade error table names two top causes: an active VPN preventing connection to Windows Update servers, or insufficient free space in the hidden System Reserved / EFI partition.
Why does my update reach 98% or 99% and say ‘We couldn’t complete the updates. Undoing changes’?
Late-stage rollback during reboot happens when Windows tries to write updated boot manager binaries or Secure Boot DBX revocation lists into the 100 MB EFI System Partition (or legacy MBR System Reserved partition) and runs out of space—frequently caused by OEM diagnostic logs or firmware capsules sitting inside that tiny partition.
How is error 0x800f0922 different from error 0x80070643?
Partition-related 0x80070643 hits the Windows Recovery Environment (WinRE) NTFS partition (typically ~500 MB at the end of the disk, fixed via Microsoft KB5028997). Partition-related 0x800f0922 hits the 100 MB FAT32 EFI System Partition (or legacy System Reserved boot partition) at the front of the disk.
Why would a VPN trigger error 0x800f0922 when the update already downloaded to 100%?
Optional features (such as .NET Framework 3.5) and certain servicing components fetch additional payloads or certificate checks during the install phase; split-tunnel VPN drivers and strict corporate proxies can block those background connections even after the main KB package downloaded.
Can a disabled Windows service cause 0x800f0922?
Yes. If a ‘Windows debloat’ script set the App Readiness (AppReadiness) service to Disabled, cumulative updates fail their post-reboot installer phase and roll back with 0x800f0922. Setting App Readiness back to Manual fixes that loop without touching disk partitions.

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.
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.

About the author

I am Lowell K. Wood IV. I research, write and maintain everything on TechFuelHQ from St. Louis County, Missouri.