If your Windows 11 update keeps failing with the error code 0x800f0922, you are not alone. This error appeared especially often with the security updates released in late 2025 and early 2026, on devices with a small EFI system partition. It is usually related to disk space, .NET, or corrupted update components. Here is the step-by-step fix.
Causes of the 0x800f0922 Error
This error occurs when Windows Update fails to install a feature or a cumulative update. The most common causes are: insufficient free space in the EFI system partition (ESP), a failed .NET Framework installation, a corrupted update cache, a VPN connection blocking access to the update server, and corruption in system files.
With the 2025-12 and 2026-01 security updates, on devices with 10 MB or less of free space in the EFI partition, the installation often failed at around 35-36%, during the restart phase. Microsoft began addressing this issue in subsequent updates.
Solution 1: Disable Your VPN and Try Again
Start with the simplest fix: if you have an active VPN or proxy connection, disable it. A VPN can block Windows Update from reaching Microsoft's servers. After disabling it, try again via Settings > Windows Update > Check for updates.
Solution 2: Run the Windows Update Troubleshooter
Go to Settings > System > Troubleshoot > Other troubleshooters and run the Windows Update troubleshooter. This tool automatically detects and resets corrupted components and resolves most simple update errors.
Solution 3: Repair System Files
Corrupted system files are a frequent cause of this error. In an administrator Terminal, run the following commands in order:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannowWhen the process finishes, restart and try the update again.
Solution 4: Reset the Update Cache
To clear the corrupted update cache, stop the services in an administrator Terminal and rename the cache folder:
net stop wuauserv
net stop bits
ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
net start wuauserv
net start bitsThen restart the update. Windows will rebuild the cache from scratch.
Solution 5: Check the EFI Partition Space and .NET
If the error appears because the EFI partition is full, the healthiest solution is to install Microsoft's most recent update that addresses the issue; so install the other pending updates first. Also, enable .NET Framework 3.5 via Control Panel > Programs > Turn Windows features on or off and try again. If Windows Sandbox is enabled, disabling it and trying again has also worked for some users.
Frequently Asked Questions (FAQ)
Why did the 0x800f0922 error increase especially with recent updates?
The late-2025 security updates got stuck during installation on devices with very little free space in the EFI system partition. Microsoft started fixing this with later updates; installing the most recent updates usually resolves the issue.
Does disabling the VPN really work?
Yes, surprisingly often this is the fix. A VPN/proxy can break the connection to the update servers. Disabling it and trying again is the quickest test.
What should I do if the commands don't fix it?
Try manually downloading and installing the relevant KB update from the Microsoft Update Catalog, or perform an in-place upgrade to repair Windows while keeping your files.
Conclusion
0x800f0922 is mostly an update error caused by disk space, connectivity, or corrupted components. Disabling the VPN and running the troubleshooter, then SFC/DISM and resetting the cache, resolves most cases. For cases caused by the EFI partition, installing the most recent update is the permanent solution.