Error 0x800f0922 is one of Windows Update’s more specific codes, and specificity is good news: it narrows the suspect list to three usual culprits. The EFI system partition is too cramped, the .NET Framework installation the update wants to patch is damaged, or VPN software is mangling the download. Each has a distinct fix, and this guide works through them in order of likelihood.

You will need administrator rights and a little patience. Nothing here risks your files, but the EFI partition work deserves a backup first — standard practice before touching boot structures.

This code rewards a few minutes of diagnosis before any fixing: note whether the failure happens during download or installation, and check Update history for whether .NET updates are among the failing items. Download-phase failures point at the VPN; install-phase failures point at .NET or the EFI partition. That single observation halves the work.

Why this happens

  • Cramped EFI partition: Less than ~30 MB free on the EFI system partition blocks the update.
  • Damaged .NET Framework: The update cannot patch a corrupted .NET installation.
  • VPN interference: VPN clients corrupting or blocking the update download stream.
  • Corrupted update cache: Damaged payload failing integrity checks with this code.
  • Third-party firewall: Blocking the update client’s server communication.
  • Failing storage: Disk errors in the EFI or system partitions.
  • Stale servicing stack: Old update client mishandling the package.
  • Dual-boot leftovers: Orphaned bootloader entries consuming EFI partition space.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Disconnect the VPN and retry

  1. Fully disconnect and exit your VPN client — not just pause, but quit the application.
  2. Also disable any third-party firewall temporarily.
  3. Run Settings > Windows Update > Check for updates and retry the failed update.
  4. If it succeeds, your VPN was the entire problem; consider updating the VPN client, as newer versions handle update traffic better.
  5. Test with the VPN’s kill switch disabled too — it can block even when the VPN is off.
  6. If the update succeeds, reinstall the VPN client fresh rather than just updating it.

Fix 2: Clear the update cache

  1. In an elevated Command Prompt, run net stop wuauserv and net stop bits.
  2. Empty C:\Windows\SoftwareDistribution\Download.
  3. Restart both services and retry the update.
  4. This eliminates the corrupted-payload variant of 0x800f0922 quickly. For the general cache technique, see our guide on security updates that will not install .
  5. Verify the Download folder stays empty until you trigger a new check.
  6. If corruption returns immediately, suspect the disk — run chkdsk.
  7. After clearing, check that Windows recreates the Download folder on the next update check.
  8. Persistent instant failures after a clear point to the EFI partition or .NET rather than the cache.

Fix 3: Repair the .NET Framework

  1. Open Settings > Apps > Installed apps and find Microsoft .NET entries.
  2. Use Modify > Repair where available, or download the latest .NET Desktop Runtime installer and run a repair install.
  3. For deeper damage, uninstall the .NET feature via Turn Windows features on or off, restart, and re-enable it.
  4. Retry the update — a healthy .NET removes one of the code’s three classic triggers.
  5. After the .NET repair, verify the version in Settings > Apps.
  6. Retry the Windows update before reinstalling anything else that depends on .NET.

Fix 4: Check EFI partition free space

  1. Press Win + X, open Disk Management, and locate the EFI system partition.
  2. If it shows very little free space (under ~30 MB), this is likely your blocker.
  3. Back up the entire disk before proceeding — EFI work is boot-critical.
  4. Free space by removing unnecessary fonts or language packs from the EFI partition using an elevated Command Prompt, or resize it with a reputable partition tool.
  5. Compare your EFI size against the 260 MB recommended for newer Windows versions.
  6. If the partition is full of fonts, remove unnecessary language font files first.

Fix 5: Resize or clean the EFI partition

  1. With a full backup in place, use a partition manager to extend the EFI partition to at least 260 MB if your disk layout allows.
  2. Alternatively, mount the EFI partition and delete stale entries: mountvol S: /s then inspect S:\EFI for orphaned bootloader folders from removed OSes.
  3. Remove only folders you can positively identify as orphaned — never touch the Microsoft or Boot folders.
  4. Unmount with mountvol S: /d and retry the update.
  5. After freeing space, verify the new free-space figure before unmounting.
  6. Reboot and confirm Windows starts normally before retrying the update.

Fix 6: Repair system files and the store

  1. Run DISM /Online /Cleanup-Image /RestoreHealth in an elevated Command Prompt.
  2. Follow with sfc /scannow and restart.
  3. These repairs fix the corrupted-component variant behind persistent 0x800f0922.
  4. Microsoft’s Windows support pages document both commands officially.
  5. Run the troubleshooter after the file repairs to validate the pipeline.
  6. If the troubleshooter itself fails, see our guide on troubleshooter problems .

Fix 7: Manual install and servicing stack refresh

  1. Install the latest servicing stack update for your build from the Microsoft Update Catalog .
  2. Then download the failed update’s KB package from the Catalog and install it manually.
  3. Restart and verify it appears in Update history.
  4. If even the manual install fails with 0x800f0922, run chkdsk C: /f to rule out disk errors as the final check.
  5. Install the SSU first and restart — order matters for servicing stack updates.
  6. After the manual install succeeds, run one normal update check to confirm the pipeline is healthy.

Closing

0x800f0922 rewards the troubleshooter who narrows instead of shotguns: VPN off, cache clear, .NET repair, EFI space check. One of those four resolves the overwhelming majority of cases. Keep your VPN client updated and your EFI partition reasonably sized, and this code should stay in your past. Keep a note of which of the three causes was yours — 0x800f0922 rarely strikes twice once the root cause is genuinely fixed. The EFI partition in particular deserves an occasional glance.

Frequently asked questions

What causes error 0x800f0922 during Windows Update?
The three classic causes are an EFI system partition with too little free space, a damaged .NET Framework installation that the update tries to patch, and VPN software interfering with the download. Less commonly, corrupted update components or a failing drive produce the same code. The fixes below address them in likelihood order.
How do I check my EFI partition's free space?
Open Disk Management and identify the EFI system partition — it is usually around 100 MB, formatted FAT32, with no drive letter. Right-click it to view properties and check free space. If it has less than about 30 MB free, it can block updates that need to write boot files. Resizing requires a reputable third-party partition tool or a careful diskpart procedure, and a full disk backup beforehand is mandatory since the EFI partition is boot-critical.
Can I just ignore 0x800f0922 and skip the update?
You can defer it, but the error will return with the next cumulative update because the underlying condition persists. The EFI partition does not free itself and .NET does not repair itself. Spending twenty minutes on the fix now saves you from fighting the same error monthly.
Does 0x800f0922 mean my Windows installation is damaged?
Not necessarily. In most cases it means one specific subsystem is blocking this particular update: the EFI partition is too full, the .NET Framework installation is damaged, or VPN software is interfering with the download. Your Windows installation itself is usually perfectly healthy. The standard repairs in this guide resolve the code without drastic measures — reinstalling Windows is almost never required for 0x800f0922.