● UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
Windows Update Error 0x800f0922? Here’s the Fix
Fix It Yourself · Troubleshooting

Windows Update Error 0x800f0922? Here’s the Fix

Updated 16 August 202612 min read
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

Windows update error 0x800f0922 installation failed means your PC tried to apply an update, got to the finalising stage, and then gave up and rolled back. The most common reason is simple: the hidden EFI System Partition is full. It's a 100MB partition that gradually fills with boot files and fonts until there's no room left for Windows to stage update data. Fix the space problem, and the update goes through. Here's exactly how to do that, plus the other causes if EFI space isn't the issue.

TL;DR

Windows update error 0x800f0922 installation failed is usually caused by a full EFI System Partition. Run the Windows Update Troubleshooter first, then reset update services and repair system files with DISM and SFC. If the error persists, mount the EFI partition and delete unused font files to free space. Works in 85 to 90% of cases without reinstalling Windows.

⏱️ 13 min read ✅ 85-90% success rate 📅 Updated August 2026

Key Takeaways

  • Windows update error 0x800f0922 installation failed is most often caused by a full EFI System Partition (100MB hidden boot partition).
  • Secondary causes include corrupted system files, stuck update services, and disabled .NET Framework features.
  • Start with the quick troubleshooter fix (60 to 70% success), then escalate to DISM/SFC repair (70 to 80%), then EFI partition cleanup (85 to 90%).
  • You do not need to reinstall Windows in the vast majority of cases.
  • Always back up before touching EFI partition files.

At a Glance

  • Difficulty: Intermediate to Advanced
  • Time Required: 20 to 45 mins
  • Success Rate: 85 to 90% of users

What Causes Windows Update Error 0x800f0922 Installation Failed?

The error code 0x800f0922 shows up during the final stages of a Windows Update installation, usually just before the system would normally reboot to complete. Windows detects it can't finish, rolls back automatically, and you end up back where you started. Frustrating, especially when it happens repeatedly on the same update.

The number one culprit, by a wide margin, is the EFI System Partition running out of free space. This is a small hidden partition (usually 100MB) that Windows uses to store boot files. Over time it fills up with accumulated boot fonts, old boot entries, and leftover files from previous updates. When a new update tries to write staging files to this partition and there's less than 30MB free, the installation fails with 0x800f0922. According to Microsoft's own UEFI/GPT partition documentation, the EFI partition needs adequate free space for update operations to complete successfully. Many OEM machines ship with a 100MB EFI partition that was fine years ago but simply isn't big enough for modern cumulative updates.

After that, corrupted system files are the next most likely cause. Damage to the Component-Based Servicing (CBS) store or the Windows image itself means the update installer can't validate or write files correctly. This is fixable with DISM and SFC, which we'll cover below.

Stuck Windows Update services are another common one. The SoftwareDistribution folder (where Windows caches downloaded update files) can accumulate corrupted data, and the BITS service or Windows Update service can get into a bad state where they appear to be running but aren't actually doing anything useful. Renaming the cache folders forces a clean rebuild.

.NET Framework issues are less common but worth knowing about. Many Windows updates have dependencies on .NET Framework 3.5 or 4.8. If these features are disabled in Windows Features, or if they've somehow got into a broken state, the update installer trips over them. And finally, third-party security software or VPNs can block Windows Update from reaching Microsoft's servers or interfere with file writes during installation. Worth disabling these temporarily before attempting any of the fixes below.

This error is particularly widespread on Windows 11 24H2 and 25H2 builds, and it affects Windows Server editions too. If you've been seeing it repeatedly on security updates from 2025 onwards, you're not alone. It's been all over Microsoft's support forums.

Windows Update Error 0x800f0922 Quick Fix

Start here. This covers the most common quick wins and sorts the problem for around 60 to 70% of users. Takes 10 to 15 minutes.

1

Quick Troubleshooting and Service Reset Easy

  1. Run the Windows Update Troubleshooter
    Press Win + I to open Settings. Go to System, then Troubleshooting, then Other troubleshooters. Find Windows Update in the list and click Run. Let it finish and apply any fixes it finds automatically. It'll reset update components and clear temp files without you having to do anything.
  2. Check EFI Partition space
    Right-click the Start button and open Disk Management. Look for the small partition labelled System or EFI (usually 100MB on the first disk). If it shows very little free space, the EFI fix in Solution 3 is what you need. If it looks fine, carry on here.
  3. Reset .NET Framework
    Press Win + R, type optionalfeatures.exe, and press Enter. Uncheck both .NET Framework 3.5 (includes .NET 2.0 and 3.0) and .NET Framework 4.8 Advanced Services. Click OK and restart. After the restart, open optionalfeatures.exe again, re-enable both features, click OK, and restart once more. This refreshes the .NET components and clears any dependency conflicts.
  4. Retry the update
    Go to Settings, then Windows Update, and click Check for updates. If the update installs cleanly, you're sorted.
If the update installs successfully, job done. If you see windows update error 0x800f0922 installation failed again, move to Solution 2.
Temporarily disabling .NET Framework may cause apps that depend on it to stop working until you re-enable it. Don't skip the re-enable step after the first restart.

More Windows Update Error 0x800f0922 Solutions

If the quick fix didn't work, the issue is most likely corrupted system files or a stuck update cache. This solution has a 70 to 80% success rate and takes around 30 to 45 minutes, mostly because DISM and SFC scans aren't quick. Don't interrupt them.

2

System File Repair and Update Service Reset Intermediate

  1. Stop Windows Update services
    Right-click Start and select Terminal (Admin) or Command Prompt (Admin). Run these four commands one at a time: net stop wuauserv net stop cryptSvc net stop bits net stop msiserver Each should confirm the service has stopped.
  2. Rename the cache folders
    In the same window, run: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 catroot2.old This backs up the corrupted cache. Windows will create fresh versions when services restart.
  3. Restart the services
    Run: net start wuauserv net start cryptSvc net start bits net start msiserver
  4. Run DISM to repair the Windows image
    Still in the admin Command Prompt, run: DISM /Online /Cleanup-Image /RestoreHealth This needs an active internet connection. It contacts Microsoft's Windows Update servers to download replacement files. Expect 10 to 20 minutes. Don't close the window.
  5. Run System File Checker
    Once DISM finishes, run: sfc /scannow Another 10 to 15 minutes. SFC uses the now-repaired Windows image to fix any corrupted system files. If it reports that it found and fixed corrupt files, that's a good sign.
  6. Restart and retry
    Restart your PC, go to Settings, then Windows Update, and try the update again.
Most users see the update install cleanly after this. If windows update error 0x800f0922 installation failed shows up again, the EFI partition is almost certainly the cause. Move to Solution 3.
DISM pulls repair files from Microsoft's servers, so a dodgy internet connection can cause it to fail. If you're on a VPN, disconnect it before running DISM. Similarly, if your antivirus is aggressive, consider pausing it for the duration of the scan. Problems with your network connection can cause other odd Windows behaviours too, and if you've noticed your WiFi button disappeared in Windows 11 around the same time, it's worth checking your network adapter drivers as a separate issue.

Advanced Windows Update Error 0x800f0922 Fixes

This is the fix that works when everything else hasn't. Freeing up space in the EFI System Partition resolves windows update error 0x800f0922 installation failed in 85 to 90% of cases where the basic and intermediate solutions didn't cut it. It sounds scarier than it is, but you do need to follow the steps exactly. Messing with the wrong files in the EFI partition can stop Windows booting, so read the warnings before you start.

CRITICAL: Create a system image backup before proceeding. Go to Settings, then Update and Security, then Backup, then Go to Backup and Restore (Windows 7), then Create a system image. Save it to an external drive. If something goes wrong and Windows won't boot, you'll need recovery media to restore. Laptop users: plug into mains power. Do not let the battery die mid-process.
3

Free EFI System Partition Space Advanced

  1. Create a system backup first
    Seriously, do this before anything else. External drive, network location, doesn't matter. Just have a recovery point.
  2. Mount the EFI partition
    Open Command Prompt as Administrator. Run: mountvol y: /s This assigns the drive letter Y: to the hidden EFI System Partition so you can access it.
  3. Navigate to the Fonts folder
    Run: cd /d y:\EFI\Microsoft\Boot\Fonts This is the specific folder containing boot font files. These are not required for normal Windows booting and can be safely removed.
  4. Delete the font files
    Run: del *.* Type Y and press Enter when prompted to confirm. This frees anywhere from 30 to 100MB in the EFI partition. Only delete from this Fonts folder. Do not touch anything else in the EFI directory.
  5. Unmount the EFI partition
    Run: cd \ Then: mountvol y: /d The partition is now unmounted and the changes are committed.
  6. Verify the freed space
    Open Disk Management (right-click Start, select Disk Management) and check that the EFI System Partition now shows more free space than before. You're looking for at least 100MB free ideally.
  7. Restart and retry the update
    Restart your PC, go to Settings, then Windows Update, and click Check for updates. The update should now install without hitting windows update error 0x800f0922 installation failed.
This fix has an 85 to 90% success rate. If the update installs, keep an eye on EFI partition space going forward. See the Prevention section below.
If all three solutions fail, try downloading the specific update manually from the Microsoft Update Catalog and installing the .msu file directly. Search for the KB number shown in your Windows Update history. As a last resort, an in-place upgrade repair using Windows installation media will fix the problem without wiping your files or apps. This is different from a clean install. It's worth knowing about, but you shouldn't need it.

Unrelated system issues can sometimes surface around the same time as update failures. If you've noticed Windows copy paste not working recently, that's a separate issue tied to clipboard services rather than the update error itself, but it can sometimes point to broader system file corruption that DISM and SFC will also address.

Preventing Windows Update Error 0x800f0922 Installation Failed

Once you've fixed it, here's how to stop it coming back. The EFI partition issue is the one that catches most people out repeatedly, so that's the priority.

Monitor EFI partition space monthly. Open Disk Management and glance at the EFI partition. If it's creeping below 100MB free, run the Fonts folder cleanup again before it causes another failed update. Some third-party partition tools can also show you EFI partition usage more clearly than Disk Management does.

Run DISM and SFC regularly. Once a month is enough. DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow catches corruption early before it causes update failures. Takes 30 minutes and saves a lot of headaches. According to Microsoft's support documentation, keeping the Windows component store healthy is one of the most effective ways to prevent update installation errors.

Keep .NET Framework enabled. Don't disable .NET Framework 3.5 or 4.8 in Windows Features unless you have a very specific reason to. Many updates depend on these components being present and functional.

Check the App Readiness service. Open services.msc, find App Readiness in the list, and make sure its startup type is set to Automatic. This service prepares apps for use after a Windows update, and if it's disabled, updates can stall during the finalising stage.

Disable VPNs and antivirus before major updates. Feature updates especially. Re-enable them once the update has completed and the system has rebooted. It's a bit of a faff but it prevents a lot of interference-related failures.

Install updates promptly. Skipping multiple updates and then trying to install a large cumulative package is more likely to cause conflicts. Staying current reduces the size and complexity of each individual update.

If you've had other odd system behaviour alongside the update errors, like files going missing or partition issues, it's worth checking our guide on folder disappeared Windows recovery as some of the underlying causes overlap.

Windows Update Error 0x800f0922 Installation Failed: Summary

Windows update error 0x800f0922 installation failed is a fixable problem. In most cases it comes down to a full EFI System Partition, which is a known issue on machines with the standard 100MB EFI partition that's been accumulating files for years. The fix is to mount the partition, delete the unused boot font files, and retry the update. If the EFI partition isn't the issue, resetting Windows Update services and repairing system files with DISM and SFC gets the job done for the majority of remaining cases.

Work through the three solutions in order: quick troubleshooter first, then service reset and file repair, then EFI partition cleanup if needed. Don't skip straight to the advanced fix without trying the others first, and always back up before touching EFI partition files. You should be able to resolve windows update error 0x800f0922 installation failed without reinstalling Windows in almost every case.

Frequently Asked Questions

Error 0x800f0922 occurs primarily because the hidden EFI System Partition runs out of free space, which prevents Windows from staging update files during the finalising stage. Secondary causes include corrupted system files, stuck Windows Update services, disabled .NET Framework features, or antivirus software blocking the installation process.

Start by running the Windows Update Troubleshooter in Settings, then reset .NET Framework via optionalfeatures.exe. If that fails, stop Windows Update services, rename the SoftwareDistribution and catroot2 folders, then run DISM and SFC repairs. For persistent cases, mount the EFI partition and delete unused font files to free space. Success rates go from 60% for basic fixes up to 90% for the EFI space solution.

Yes, it is very common, particularly on Windows 11 24H2 and 25H2 builds. The root cause (an undersized 100MB EFI partition that gradually fills up) affects a huge number of machines. It has been widely reported across Microsoft support forums and affects both home and business editions of Windows.

Absolutely. In 85 to 90% of cases this error is fixed without reinstalling Windows. Freeing EFI partition space, repairing system files with DISM and SFC, and resetting update services are enough. A clean install is only needed if the Windows image is severely corrupted and all other methods have failed.

The primary cause is a full EFI System Partition with less than 30MB free space, which blocks Windows from staging update files. Other causes include corrupted Windows component store files, a stuck SoftwareDistribution cache, misconfigured .NET Framework features, and interference from security software or VPN clients during the installation process.

Keep reading