Fix Windows 11 Cumulative Update Fails With 0x800F0922 Error

Quick fix: Error 0x800F0922 means installation script ran out of space on the System Reserved partition or the System partition. Free 1+ GB on C: drive, then retry update. If C: has plenty of space, check the EFI System Partition (typically 100 MB) for low space — remove old EFI entries via bcdedit /enum firmware.

Windows Update completes the download phase, then during install fails with error 0x800F0922. Sometimes 0x800F0907 or 0x800F0900 (related “script failed” errors). The common cause is one of three: low disk space, EFI partition full, or VPN/proxy interfering with update validation.

What causes this

Error 0x800F0922 is generic: “Couldn’t connect to the Windows Update servers” (network) or “Installation script failed” (component install). For modern Windows 11, it’s most often the latter — the install script needs free space and access to specific components. Three common root causes:

• Low disk space on System Reserved or EFI partition: the install needs 100–500 MB free on this small partition. Old recovery files or kernel images consume it.
• Active VPN or proxy blocking update CDN: install needs to verify components against Microsoft’s catalog mid-install.
• Antivirus interfering with install: third-party AV may block or modify install scripts.

Method 1: Free C: drive and System Reserved space

The most common fix.

1. Check free space: Settings → System → Storage. C: drive should have at least 10 GB free for a major cumulative update; 25 GB for feature update.
2. Run Disk Cleanup with admin (cleanmgr) → Clean up system files. Tick:
   • Windows Update Cleanup
   • Delivery Optimization Files
   • Temporary files
   • Previous Windows installation(s) (if present)
3. Run from Terminal (Admin):

   DISM /Online /Cleanup-Image /StartComponentCleanup
   DISM /Online /Cleanup-Image /SPSuperseded

   This cleans the component store.

4. Reduce hibernation file: powercfg /h /size 50. Saves several GB.
5. Retry the update. Settings → Windows Update → Check for updates → Install.

Often the fix is just free space.

Method 2: Disable VPN, proxy, and antivirus during update

For when disk space is fine.

1. Disconnect any active VPN.
2. If you use a proxy: temporarily disable. Settings → Network & internet → Proxy → toggle off Use a proxy server.
3. Disable third-party antivirus temporarily. Each AV has its own pause feature: Norton, McAfee, Kaspersky, etc.
4. For Windows Defender: don’t disable; it’s usually fine. But check Defender exclusions don’t include critical Windows folders.
5. Retry update.
6. If update succeeds: re-enable VPN/proxy/AV afterwards.
7. For corporate networks: contact IT. They may have configured Group Policy preventing Windows Update components access, or have a WSUS server that needs the update first.

This rules out network and security software interference.

Method 3: Use Windows Update Troubleshooter and manual cleanup

For persistent failures.

1. Open Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run. The troubleshooter fixes common issues automatically.
2. If troubleshooter doesn’t help: open Terminal (Admin) and run the Windows Update component reset:

   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 msiserver

3. Run system file checks:

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

   Both must complete without errors.

4. Retry update.
5. For the specific failing update: download standalone from catalog.update.microsoft.com. Install manually via MSU. Often works when Windows Update channel fails.
6. For repeated failures with same error: see Method 4 below.

This is the comprehensive repair path.

How to verify the fix worked

• Settings → Windows Update. Update installs successfully. Status shows installed with timestamp.
• Update history shows the previously-failing KB as installed.
• Reboot. After login, no “Updates failed” notification.

If none of these work

If update still fails with 0x800F0922, deeper troubleshooting. Method 4: Check EFI System Partition size: from Disk Management, the ESP is typically 100 MB (FAT32). If it’s nearly full: open Terminal (Admin) → diskpart → list volume → find ESP → select volume N → assign letter=S. Then in File Explorer, navigate to S: and delete old EFI entries (look for non-Microsoft folders if multi-boot). Use bcdedit /enum firmware to identify orphan entries; bcdedit /delete {GUID} to remove. For repeated failures with same error: download the cumulative update standalone from catalog.update.microsoft.com. Install via MSU file. Often succeeds where Windows Update channel fails. For very specific updates that keep failing: hide that specific update via Microsoft’s wushowhide.diagcab tool. Wait for a follow-up KB. Last resort: in-place upgrade: mount Windows 11 ISO, run setup.exe, choose “Keep personal files and apps.” Reinstalls Windows including all current updates. Fixes most update-related corruption.

Bottom line: 0x800F0922 most commonly means low disk space. Run Disk Cleanup + DISM component cleanup. If space is fine, disable VPN/proxy/AV temporarily. Use Windows Update Troubleshooter and SFC for deeper repair.