How to Fix Windows Update Error 0x800f0922 in Windows 11

Attempting to download and apply monthly cumulative updates or feature releases in Windows 11 only to have the installation reach 96%–98%, fail, and roll back with the stop code 0x800f0922 is a widespread system update breakdown. The error dialogue typically presents: “Something didn’t go as planned. No need to worry—undoing changes.” In the Windows servicing stack, error code 0x800f0922 indicates either a failure to connect to Microsoft update endpoints (often caused by an active VPN proxy), corrupted .NET Framework advanced components, or critically, insufficient free storage within the hidden EFI System Partition (ESP) required to stage updated bootloader files. This comprehensive guide details how to resolve each root cause and complete Windows 11 updates successfully.

What Causes Error 0x800f0922 in Windows 11?

The Windows 11 servicing pipeline enforces rigorous pre-flight checks before executing kernel-level patching:

• Insufficient Free Space in the EFI System Partition: Security updates for the Windows bootloader require at least 15–20 MB of free buffer space on the EFI partition; third-party backup software or antivirus utilities frequently clutter this partition with orphaned log files.
• Corrupted or Disabled .NET Framework Features: Windows cumulative patches update .NET binaries; if required .NET 3.5 or 4.8 components are damaged, servicing halts.
• Active VPN or Secure Proxy Interference: VPN tunnels blocking Windows Update client connections to designated Microsoft Content Delivery Networks (CDNs).
• Corrupted SoftwareDistribution Database: Incomplete download staging files inside C:\Windows\SoftwareDistribution generating hash mismatch errors during package verification.
• Damaged Windows Component Store (WinSxS): Broken hardlinks or corrupted manifests preventing the servicing stack from committing differential updates.

Method 1: Disconnect Active VPNs and Reset Network Proxy Settings

Windows Update requires direct, unhindered TLS handshakes with Microsoft server farms to authenticate cryptographic update payloads.

1. If you run a third-party VPN client (such as NordVPN, ExpressVPN, or Cloudflare WARP), right-click its tray icon and select Disconnect or Exit.
2. Press Win + I to open Windows Settings.
3. Navigate to Network & internet > Proxy.
4. Under Automatic proxy setup, ensure Automatically detect settings is toggled On.
5. Under Manual proxy setup, ensure Use a proxy server is set to Off.
6. Re-open Windows Update and click Check for updates.

Method 2: Verify and Free Space on the EFI System Partition

Lack of buffer space on the hidden EFI partition is the leading hardware-level cause of update failure at 98% completion.

1. Press Win + X and select Terminal (Admin) or PowerShell (Admin).
2. Assign a temporary mount drive letter (such as Y:) to your hidden EFI partition:

   mountvol Y: /S

3. Switch to the newly mounted partition and navigate to the EFI directory:

   Y:
   cd EFI

4. List directory contents to check for third-party folders (such as old OEM backups, HP, Dell, or orphaned Linux bootloaders):

   dir

5. If third-party or residual antivirus diagnostic logs are occupying space, delete them carefully while leaving the Microsoft and Boot directories untouched.
6. Unmount the EFI drive letter:

   mountvol Y: /D

7. Restart your computer.

Method 3: Enable and Repair .NET Framework Features

Ensuring both modern and legacy .NET components are correctly configured prevents update rollback during component registration.

1. Press Win + R, type optionalfeatures.exe, and press Enter.
2. In the Windows Features dialogue, locate:
   • .NET Framework 3.5 (includes .NET 2.0 and 3.0)
   • .NET Framework 4.8 Advanced Services
3. Ensure both parent checkboxes are fully ticked. (If unticked, tick them and click OK to let Windows download the required feature files).
4. If they were already ticked, untick them, click OK, restart your PC, and then return to re-tick them to rebuild the .NET subsystem cleanly.

Method 4: Reset Windows Update Services and Clear SoftwareDistribution

Purging cached update staging payloads forces Windows 11 to re-download pristine installation files.

1. Press Win + X and select Terminal (Admin).
2. Stop core update services sequentially:

   net stop wuauserv
   net stop cryptSvc
   net stop bits
   net stop msiserver

3. Rename the corrupted cache folders:

   ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
   ren C:\Windows\System32\catroot2 catroot2.old

4. Restart the services:

   net start wuauserv
   net start cryptSvc
   net start bits
   net start msiserver

5. Close Terminal and restart your computer.

Method 5: Execute DISM and SFC Repair Scans

Repairing corrupted Windows component store manifests ensures the operating system can integrate cumulative update packages.

1. Launch Terminal (Admin) (Win + X > Terminal (Admin)).
2. Run the DISM component cleanup tool:

   dism /online /cleanup-image /restorehealth

3. Wait for the scan to reach 100% and report that the corruption was repaired.
4. Execute System File Checker:

   sfc /scannow

5. Once verification completes, open Settings > Windows Update and re-attempt the installation.