Fix Windows 11 Update Error 0x800f0922: The EFI Partition Trap

If your Windows 11 PC keeps rolling back its cumulative update at around 35% with error 0x800f0922, you are almost certainly hitting the EFI System Partition (ESP) space bug that Microsoft confirmed in 2026. The good news: it is fixable, and you do not need to reinstall Windows. The trap is that the usual repair tools report a perfectly healthy system while the real blocker, a partition only a few megabytes too small, goes unnoticed.

Key takeaways

• In the 2026 outbreak, 0x800f0922 means the EFI System Partition is too full to receive a larger boot component, not generic corruption.
• It hits PCs that were upgraded forward from Windows 7/10, which often have a cramped ~100 MB ESP.
• Install the latest cumulative update first, Microsoft shipped a Known Issue Rollback (KIR) mitigation that fixes many systems automatically.
• A clean DISM/SFC result does not clear it if the partition is the real blocker, keep going to the ESP checks.
• If 0x80073712 or 0x800f0993 appear alongside it, treat them the same way.

What 0x800f0922 actually means

Historically, 0x800f0922 is a generic "a feature or update component could not be installed" code. Microsoft's own documentation ties it to two common situations: the system reserved partition lacks free space, or a .NET/component-store operation failed during servicing.

In the 2026 outbreak, the cause is specific. The May and June Patch Tuesday cumulative updates (such as KB5089549) ship a larger boot component that must be written into the EFI System Partition. On machines whose ESP has 10 MB or less free, the write fails, the install stalls mid-reboot, and Windows rolls everything back.

This disproportionately affects PCs that were originally set up years ago, often machines that started on Windows 7 or 10 and were upgraded forward. Those layouts frequently created a tiny ~100 MB EFI partition that is now too cramped for modern servicing.

Here is how to read each fix against its risk and effort, so you try the safe ones first:

Step	What it fixes	Risk	Time
Install latest cumulative update	Lets the KIR mitigation apply automatically	None	10-20 min
DISM then SFC	Rules out genuine component-store corruption	None	15-30 min
Check ESP free space (diskpart)	Confirms the partition is the real blocker	Low (read-only)	5 min
Registry padding mitigation	Reduces reserved ESP space Windows requests	Medium (back up first)	10 min
Enlarge the EFI partition	Permanent room for boot components	High (can break boot)	30-60 min

Step 1: Install the official fix first

Before manual surgery, check whether Microsoft has already patched your system. The issue was addressed by updates released May 26, 2026 (KB5089573) and later, and Microsoft pushed a Known Issue Rollback (KIR) mitigation to consumer and unmanaged business devices automatically.

1. Open Settings, then go to Windows Update.
2. Click Check for updates and install everything offered.
3. Restart and retry the failed update.

If a newer cumulative update is available, installing it may resolve the failure without any of the steps below.

Step 2: Repair the component store

If the update still fails, rule out genuine corruption. Open an elevated Command Prompt or Terminal (Run as administrator) and run, in order:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

DISM repairs the underlying Windows image; sfc then fixes individual protected system files against that repaired image. Reboot afterward and try the update again. These are the same workhorse commands behind most Windows repairs, including the CRITICAL_PROCESS_DIED blue screen.

Step 3: Check EFI partition free space

You need to confirm whether the ESP is actually full. Open an elevated Command Prompt and start diskpart:

diskpart
list disk
select disk 0
list partition

Look for a partition labeled "System" of roughly 100 MB. If it exists and reports almost no free space, that is your problem. Type exit to leave diskpart.

The cleanest way to inspect contents is to temporarily assign it a drive letter, but be cautious, the ESP holds boot files. If you are not comfortable in diskpart, skip to the registry mitigation in Step 4 instead. (For a step-by-step on safely assigning the ESP a letter, our INACCESSIBLE_BOOT_DEVICE guide walks through the same diskpart flow.)

Step 4: Apply Microsoft's registry mitigation

For systems that still fail after the KIR rollout, Microsoft published a registry workaround that reduces the reserved padding Windows requests inside the EFI partition during servicing. This frees just enough room for the install to complete.

1. Press Windows + R, type regedit, and press Enter.
2. Follow Microsoft's published key and value exactly for your build, do not guess the path.
3. Reboot and reattempt the update.

When nothing works: enlarge the ESP

If the partition is genuinely too small, the permanent fix is to grow the EFI System Partition. This is an advanced operation: it typically means shrinking the adjacent Windows partition, deleting and recreating the ESP at a larger size (256 MB is a safe modern target), and rebuilding the boot configuration with bcdboot. Because a mistake here can leave the machine unbootable, back up your data first and consider a reputable partition tool that handles ESP resizing safely.

Frequently asked questions

Why does this only affect older PCs?

PCs first installed on Windows 7 or 10 and upgraded forward usually have a small ~100 MB EFI partition created by those older installers. Modern Windows servicing writes larger boot components, and that legacy partition no longer has room. Machines installed fresh on recent Windows 11 builds tend to have a roomier ESP.

Will running DISM and SFC fix 0x800f0922?

Only if the cause is component-store corruption. In the 2026 ESP-space outbreak, DISM and SFC come back clean while the update still fails because the blocker is partition space, not corruption. Run them to rule corruption out, then check the EFI partition.

Is it safe to edit the registry mitigation myself?

Yes, if you follow Microsoft's published key and value exactly and back up first. Export the key and create a System Restore point before changing anything. Do not improvise the path, an incorrect edit won't help and could cause other servicing problems.

Can I just enlarge the EFI partition to be done with it?

That is the permanent fix, but it is advanced and risky, a mistake can leave the PC unbootable. Try the KIR update and registry mitigation first. If you do resize, back up your data and use a partition tool that handles ESP resizing and bcdboot rebuild safely.

What to do right now

• Install the latest cumulative update and let the KIR mitigation apply.
• Run DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow.
• Verify EFI System Partition free space with diskpart.
• Apply Microsoft's registry padding mitigation if the failure persists.
• As a last resort, enlarge the ESP after backing up.

Work through these in order and the 0x800f0922 rollback loop almost always clears without a full Windows reinstall.