Fix Windows 11 Update 0x800f0922 Error on KB5089549

The windows 11 update 0x800f0922 error appears when KB5089549 — Microsoft’s May 2026 Patch Tuesday cumulative update — hits around 35–36% during the reboot phase, then rolls back with the message “Something didn’t go as planned. Undoing changes.” Microsoft has confirmed the root cause: insufficient free space on the EFI System Partition (ESP). If your ESP has 10 MB or less of free space, the update cannot complete. The fix is straightforward once you know where to look.

What Does Error 0x800f0922 Actually Mean?

Error code 0x800f0922 is a Windows Update failure code that specifically signals the update installer could not write required files during the reboot servicing phase. It is not a generic network or corruption error — in the context of KB5089549, it almost always means the EFI System Partition ran out of room mid-install.

The EFI System Partition is a small, hidden FAT32 partition on UEFI-based systems. It holds bootloader files, firmware drivers, and update staging files. Most OEM PCs ship with an ESP sized between 100 MB and 260 MB. Over years of cumulative updates, old boot files accumulate and gradually eat into that space. When a new update needs to write its files during the pre-boot servicing phase — and less than ~10 MB remains — the installer fails, triggers a rollback, and surfaces error 0x800f0922.

Microsoft acknowledged this specific behaviour for KB5089549 in its release health documentation, noting that devices with 10 MB or less free on the ESP are affected. The workaround is to free space on the partition before attempting to install the update again.

How to Check EFI Partition Free Space

Before you start deleting anything, check exactly how much free space your ESP has. You need an elevated Command Prompt or PowerShell window for this — the ESP is not visible in File Explorer by default.

Step 1 — Open DiskPart

1. Press Win + S, type cmd, right-click Command Prompt, and select Run as administrator.

2. Type diskpart and press Enter.

Step 2 — Identify and select the ESP

1. Type list disk and press Enter. Note the disk number for your system drive (usually Disk 0).

2. Type select disk 0 (replace 0 with your disk number) and press Enter.

3. Type list partition and press Enter. Look for a partition of type System — typically 100–260 MB in size.

4. Type select partition X (replace X with that partition number) and press Enter.

5. Type assign letter=Z and press Enter. This mounts the ESP temporarily.

6. Type exit to leave DiskPart.

Step 3 — Check free space

1. Back in the elevated Command Prompt, type dir Z: and press Enter.

2. At the bottom of the output you will see a line like X bytes free. If that number is below roughly 10,000,000 bytes (10 MB), your ESP is the problem.

When you are done, remove the drive letter by running DiskPart again: select partition X then remove letter=Z. Leaving the ESP mounted without a drive letter is the safer default state.

How to Free Up Space on the EFI Partition Safely in order to fix the 0x800f0922 error

Freeing space on the ESP requires care. Deleting the wrong files here will prevent your PC from booting. Follow these steps exactly — only remove what is explicitly identified below as safe to delete.

Warning: Do not delete folders named Microsoft, Boot, or any .efi files unless you are certain what they are. Never format the partition. The goal is to remove stale, duplicate boot entries left by old Windows update servicing files — not to clear the partition.

What is safe to remove

• Duplicate or outdated language pack folders inside Z:\EFI\Microsoft\Boot\ — folders named with locale codes (e.g. en-US, de-DE) that duplicate what is already in a parent folder. Keep at least one set.

• Old boot manager backup files with extensions like .bak inside the Boot folder.

• Folders created by third-party boot managers you no longer use (e.g. old Linux GRUB entries if you removed that OS).

Steps to reclaim space

1. With the ESP mounted as Z: (repeat the DiskPart assign steps above if you removed the letter), open an elevated Command Prompt.

2. Type dir Z:\EFI\ to list what is in the EFI folder. You should see a Microsoft subfolder and possibly others.

3. Type dir Z:\EFI\Microsoft\Boot\ to inspect the Boot folder contents and note the sizes.

4. Delete only stale locale folders you do not need: rmdir /s /q Z:\EFI\Microsoft\Boot\de-DE (example — only remove locales that are not your system language).

5. If old .bak files exist: del Z:\EFI\Microsoft\Boot\bootmgfw.efi.bak (example filename — check yours first).

6. Run dir Z: again to confirm free space has increased above 50 MB to give the update room to work.

7. Remove the drive letter: open DiskPart, select partition X, remove letter=Z, exit.

If you cannot recover enough space through this method alone, Microsoft’s support article also notes that resizing the ESP using third-party partition tools is an advanced option — but that is outside the scope of this guide and carries additional risk. For most users, clearing old locale folders is sufficient.

Installing KB5089549 After Fixing the 0x800f0922 Error

Once your ESP has at least 50 MB of free space, the windows 11 update 0x800f0922 block is resolved and KB5089549 should install normally. Here is how to trigger the install cleanly:

1. Open Settings > Windows Update and click Check for updates. KB5089549 should reappear as a pending update.

2. Alternatively, download the standalone installer directly from the Microsoft Update Catalog — search for KB5089549 and download the version matching your Windows 11 edition (x64 for most systems).

3. Run the standalone .msu installer as administrator if you downloaded it manually.

4. Allow the system to restart when prompted. The reboot phase should now complete without rolling back.

5. After reboot, verify the update is listed under Settings > Windows Update > Update history with a status of Successfully installed.

If the update still fails after freeing space, run the built-in Windows Update Troubleshooter: Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run. This clears the software distribution cache and can resolve secondary issues unrelated to the ESP.

What to Do If a BitLocker Recovery Key Prompt Appears

Some users see a BitLocker recovery key prompt immediately after KB5089549 installs and the system reboots. This is expected behaviour — not a sign something went wrong. When the update modifies boot-critical files on the ESP, BitLocker detects a change to the boot measurement chain and requires key confirmation before unlocking the drive.

To resolve this:

• Have your 48-digit BitLocker recovery key ready before you install the update. You can retrieve it from your Microsoft account recovery key page if the drive was backed up there, or from your Azure AD / Active Directory admin if this is a work device.

• Enter the recovery key when prompted at the blue pre-boot screen. Windows will boot normally after that.

• After booting, BitLocker re-seals its measurements to the new boot state, so you should not be prompted again for this update.

If you do not have the recovery key and are locked out, do not attempt further reboots. Contact your IT administrator or refer to your organisation’s key escrow policy before proceeding.

Keeping Windows 11 Healthy After Fixing the Update Error

Resolving the KB5089549 cumulative update failure is a one-time fix, but the underlying problem — an ageing, cluttered ESP — will return if not monitored. A few habits help:

• Check ESP free space after major feature updates. Windows 11 24H2 and future releases may add new boot files. Re-run the dir Z: check a couple of times a year.

• Remove unused OS boot entries. If you previously had a dual-boot setup that you no longer use, clean up the leftover EFI entries with bcdedit /enum all to identify them and bcdedit /delete to remove stale entries.

• Stay current with cumulative updates. Skipping multiple Patch Tuesday updates causes a larger backlog, which increases the risk of failures like 0x800f0922 when a big update arrives.

• Keep your Windows licence valid. Update failures on unlicensed copies of Windows are harder to diagnose because activation issues can compound servicing errors. If you need a genuine Windows 11 key, you can buy a Windows 11 Home licence or check the Windows 11 Pro installation and activation guide for setup steps.

Frequently Asked Questions

Is the windows 11 update 0x800f0922 error dangerous?

No. The update rolls back cleanly, leaving your system in exactly the same state as before the failed install attempt. Your files and settings are not affected. However, KB5089549 includes security fixes, so you should resolve the error and install the update as soon as possible rather than leaving it pending indefinitely.

Does this 0x800f0922 error only affect KB5089549?

The 0x800f0922 code can appear with other cumulative updates too, but Microsoft specifically confirmed that KB5089549 (May 2026 Patch Tuesday) triggers it on devices with 10 MB or less free on the ESP. If you see this code on a different update, the ESP space check is still the right first diagnostic step.

How much free space does the EFI System Partition need?

Microsoft’s guidance is that 10 MB or less triggers the failure. To give yourself a safe buffer, aim for at least 50 MB of free space before installing a cumulative update. Some IT administrators recommend keeping the ESP at least 30% free at all times, which on a 100 MB partition means no more than 70 MB in use.

Can I resize the EFI System Partition to avoid this in future?

Yes, but it is an advanced operation. You need to shrink an adjacent partition and extend the ESP using a tool like GParted from a bootable USB drive, or use Windows RE with diskpart — the ESP cannot be resized while Windows is running from it. Make a full system backup before attempting this. For most home and small business users, clearing old locale and backup files from the ESP is sufficient.

Will this 0x800f0922 fix work if my PC uses a legacy MBR/BIOS setup instead of UEFI?

No. Error 0x800f0922 related to ESP space only occurs on UEFI-based systems that have an EFI System Partition. If your PC uses legacy BIOS with an MBR disk, the same error code may appear but it has a different cause — most likely a corrupted Windows system image or a blocked Windows Modules Installer service. Run DISM /Online /Cleanup-Image /RestoreHealth and then sfc /scannow in that scenario.