Windows 11 Update KB5089549 Blocked by EFI Space Shortage

Windows 11 Update Hits a Snag

Microsoft's May 2026 security update for Windows 11, KB5089549, isn't going smoothly for everyone. Some users are hitting a wall during installation. The core problem: insufficient free space on the EFI System Partition (ESP). A simple space issue, actually, is killing the update process.

Affected users? They're seeing the installation roll back. It usually happens around 35–36% completion. That's when you get those classic error messages: "Something didn't go as planned. Undoing changes." This issue is pretty common on devices with 10 MB or less free space on the ESP. That tight squeeze triggers error code 0x800f0922.

Microsoft’s Recommended Fix

So, what's Microsoft suggesting? Use the Known Issue Rollback feature. It lets users reverse faulty updates. For enterprise systems, IT admins can manually apply a Group Policy fix. That means installing and configuring specific policies, then restarting the affected devices. Pretty straightforward, if you're an admin.

Broader Context

This isn't Microsoft's only headache lately. The company's been dealing with a few. There was that Windows Autopatch bug in the EU, remember? It accidentally pushed restricted driver updates. And a vulnerability also popped up, affecting third-party backup applications right after the April 2026 updates. Yeah, it's been a busy time.

Key Points:

• Known Issue Rollback: Your escape hatch for bad updates.
• Group Policy Fix: For IT departments to implement manually.
• Error 0x800f0922: The specific code for that EFI space crunch.

What This Means for You

Running Windows 11 and hitting this update snag? You might need to check your EFI partition's free space. Enterprise users, talk to your IT team. They'll need to roll out that Group Policy fix. It's kinda crucial to keep your system secure and avoid those frustrating installation failures.

What's Still Unclear

How will Microsoft permanently fix this EFI space problem? Will future updates just keep running into similar issues? We don't know yet. And what about the long-term impact on systems with minimal available ESP space? That's still an open question.

Why This Matters

This isn't just a tech hiccup. It shows how important it is for systems to have enough resources for updates. It also highlights Microsoft's ongoing challenge with managing space constraints in its update processes. A small partition, a big problem.