Windows Update Error 0x800f0922? Here’s the Fix

Windows update error 0x800f0922 installation failed means your update rolled back during the finalising stage and your system is still unpatched. In most cases, the hidden EFI System Partition has run out of space. That's the short answer. The fix takes 20 to 45 minutes depending on how deep the problem goes, and you almost certainly don't need to reinstall Windows to sort it.

What Causes Windows Update Error 0x800f0922 Installation Failed?

Most of the advice floating around online points at generic Windows Update issues. Corrupted files, dodgy services, that sort of thing. Those can contribute, but the real culprit in the majority of cases I see is the EFI System Partition. This is a hidden partition, usually just 100MB, that Windows uses to store boot files. Over time, it fills up with font files, boot loaders, and other staging data. When a cumulative update tries to write its files there during installation, it hits a wall. The update fails, rolls back, and you get 0x800f0922.

Here's the thing: Microsoft's own UEFI partition documentation recommends the EFI partition be at least 100MB, but many OEM systems ship with exactly that. No headroom at all. Add a few years of updates and the partition is stuffed. This is especially common on Windows 11 24H2 and 25H2 machines, where the cumulative updates are larger than they used to be.

That said, there are other causes worth knowing about. Corrupted system files in the Component-Based Servicing store can block the installer from completing. The SoftwareDistribution folder (where Windows caches update files before installing them) can accumulate broken or partially downloaded files that cause the whole process to stall. And .NET Framework, specifically versions 3.5 and 4.8, has to be properly enabled because many updates depend on it. If those features have been toggled off at some point, you'll see failures.

Third-party antivirus and VPN software are lower on the list but worth mentioning. Some security tools intercept Windows Update's network calls and block the download or installation process. If you're running an aggressive endpoint security suite, that's worth checking. For a full breakdown of what each cause looks like on screen, the Microsoft Windows Update Troubleshooter page covers the diagnostic steps Microsoft recommends as a starting point.

So in order of likelihood: EFI partition space (high), corrupted system files (medium), stuck update services (medium), .NET issues (low), antivirus interference (low). Work through the solutions in that order and you'll fix it without wasting time on the wrong thing.

Windows Update Error 0x800f0922 Quick Fix

Start here. This covers the basic causes and fixes about 60 to 70% of cases. It's quick, low-risk, and worth doing before anything more involved.

More Windows Update Error 0x800f0922 Solutions

If the quick fix didn't work, the problem is likely corrupted system files or a broken update cache. This solution takes 30 to 45 minutes but has a 70 to 80% success rate. Don't skip the DISM step, it's the one that actually downloads and replaces damaged Windows image components.

If you're still getting the error after this, the EFI partition is almost certainly the problem. This is the fix that handles the remaining cases where the basic and intermediate solutions don't cut it. Worth noting: if the DISM repair fails because Windows can't access Microsoft servers, check whether a VPN is active and disable it, then try again. Network issues can look identical to corruption issues at this stage.

Advanced Windows Update Error 0x800f0922 Fix: EFI Partition Cleanup

This is the fix that sorts the majority of persistent 0x800f0922 errors. It involves mounting the hidden EFI System Partition and deleting unused boot font files to free up space. Took me three reboots on one client machine before I realised the EFI partition had literally 4MB free. Once we cleared it, the update installed first time.

Before you start: create a system image backup. Go to Settings > Update & Security > Backup > Go to Backup and Restore (Windows 7) > Create a system image. Save it to an external drive. If something goes wrong with the EFI partition, you'll want that. If you're worried about losing data during this process, our guide on free file recovery for Windows covers your options for getting files back if the worst happens.

If you're still seeing the error after clearing EFI space, the last option before an in-place upgrade repair is to download the specific update manually from the Microsoft Update Catalog. Search for the KB number shown in your Windows Update history, download the .msu file, and run it directly. This bypasses the Windows Update service entirely and sometimes gets past whatever is blocking the automated process. And if you end up with boot issues during any of this, check our guide on Windows Boot Manager boot failed for recovery steps.

Preventing Windows Update Error 0x800f0922 Installation Failed

The EFI partition problem is the one to focus on for prevention. Most systems ship with a 100MB EFI partition and never get bigger. That's fine for the first few years, but as Windows accumulates boot files across major updates, the space disappears. Check Disk Management every few months and keep an eye on that partition's free space. The moment it drops below 50MB, run the font file cleanup described above before the next major update hits.

For system file health, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth monthly. It sounds excessive but it takes 20 minutes and catches corruption before it causes update failures. Set a calendar reminder. Most of the machines I see with severe corruption issues are ones where nobody ran these tools for two or three years.

Keep .NET Framework 3.5 and 4.8 enabled in Windows Features. Don't toggle them off unless you have a very specific reason. Many updates silently depend on them, and disabling them is a common cause of update failures that are hard to trace.

A few other things worth doing in priority order:

1. Temporarily disable third-party antivirus before installing major feature updates. Re-enable immediately after.
2. Use a wired connection without VPNs active during updates. Wireless and VPN-routed connections can cause partial downloads that corrupt the update cache.
3. Install updates promptly. Letting cumulative updates pile up means larger, more complex installations that are more likely to hit edge cases.
4. Make sure the App Readiness service is set to Automatic in services.msc. It's a quiet dependency that causes failures when it's disabled.

And if you're managing storage across multiple drives or thinking about backup strategies, having a solid backup in place means that even if an update goes badly wrong, you're not starting from scratch. Our overview of 10 TB cloud storage options for Windows is worth a look if you want offsite backup sorted properly.

Windows Update Error 0x800f0922 Installation Failed: Summary

Windows update error 0x800f0922 installation failed is fixable in the vast majority of cases without reinstalling Windows. Start with the quick troubleshooter and .NET reset. If that doesn't work, reset your update services and run DISM and SFC. If the error persists, the EFI partition is almost certainly full and needs the font file cleanup. Work through the solutions in order and you'll have an 85 to 90% chance of fixing windows update error 0x800f0922 installation failed before you need to consider anything more drastic. The update rolls back cleanly each time it fails, so your system isn't damaged. You've got time to work through this properly.