Microsoft acknowledged on May 15, 2026, that a recent Windows 11 security update is tripping up a surprising number of devices—not because of code bugs, but because of a storage allocation decision made years ago: the size of the EFI System Partition (ESP). KB5089549, a Patch Tuesday cumulative update for Windows 11 versions 24H2 and 25H2, fails to install with error 0x800f0922 on machines where the hidden EFI partition has roughly 10MB or less of total space. The confirmation comes after weeks of user reports flooding community forums and IT helpdesks.

The problem is both deceptively simple and deeply frustrating. The EFI partition, a critical slice of your hard drive that stores boot managers and system utilities, has long been given a recommended minimum size of 100MB. Yet countless PCs—especially those shipped with Windows 10 or early Windows 11 builds, or those that underwent manual partitioning—ended up with ESPs of just 10MB or even less. For years, that cramped quarters sufficed. Now, with the expanding footprint of cumulative updates and the additional boot-time components they carry, that tiny partition has become a bottleneck.

The Anatomy of the Failure

When a Windows update like KB5089549 begins installation, it often needs to stage new boot-critical files directly onto the EFI System Partition. These include boot managers, Secure Boot certificates, and recover y tools. If the partition lacks sufficient free space—and a 10MB partition leaves almost none after the existing boot loader and logs—the update grinds to a halt. Windows Update throws error 0x800f0922, a generic code that usually points to insufficient storage or an inability to write temporary files. In this specific case, the staging fails because the ESP simply cannot accommodate the new payload.

Users first suspected a typo when they saw the error. How could a multi-gigabyte update fail for want of a few megabytes? The answer lies in the strict isolation of the EFI partition. Windows cannot borrow space from the C: drive for these critical files; they must land on the ESP itself. This architectural requirement, designed for security and boot integrity, becomes a landmine when the partition is undersized.

Who Gets Hit

The issue affects Windows 11 24H2 and 25H2 devices, according to Microsoft’s statement. Not every device with a small ESP will encounter the error—some updates may still squeak through if the required staging files are tiny—but KB5089549 appears to push the limit. The update carries a bundle of kernel improvements, driver updates, and security mitigations that collectively demand more ESP breathing room than previous patches.

Affected hardware spans a wide range. Some OEMs shipped systems with minimal 10MB ESPs to squeeze every last gigabyte for the user data partition. Enthusiast-built PCs are equally vulnerable if the installer auto-created a tiny ESP during Windows setup (a long-standing quirk of certain configurations). Virtual machines, often provisioned with lean disk layouts, are also showing failures in lab environments. The common denominator: a pre-existing ESP that’s 10MB or smaller.

Why This Matters Now

KB5089549 is no ordinary patch. As a security update, it plugs several critical vulnerabilities, including a zero‑day in the Windows Kernel reported by a third-party researcher. Delaying its installation leaves systems exposed. The failure, therefore, isn’t just an annoyance—it’s a security gap. For enterprise environments, where central management tools push these updates automatically, failed deployments mean red dashboards and hurried tickets. For consumers, it’s a return to the bad old days of Windows Update anxiety.

Microsoft’s acknowledgment, shared via a support document, reads: “We are aware of an issue where devices with EFI System Partition sizes of approximately 10 MB or less may fail to install KB5089549 with error 0x800f0922. We are working on a resolution.” No timeline was given, but the phrase “working on a resolution” suggests the company may either adjust the update’s staging logic or provide a tool to safely expand the ESP.

The EFI Partition: A Forgotten Corner

To understand the fix, you must first appreciate what the EFI partition does. It’s a small FAT32 volume, typically 100MB to 500MB, that lives at the beginning of a GPT disk. Its contents are hidden from File Explorer, but tools like Disk Management or the mountvol command can reveal it. Inside, you’ll find the Windows Boot Manager (bootmgfw.efi), a Boot Configuration Data (BCD) store, and sometimes memory dump files or crash logs. Secure Boot relies on it, as do firmware updates and system recovery routines.

The recommended minimum was always conservative. When Windows 8 first mandated the EFI system, Microsoft’s own documentation suggested 100MB. Why so much? To accommodate multiple boot loaders, language files, and future growth. But many third-party tools and older deployment images ignored that advice, creating bare-minimum 10MB partitions. For years, that shortsightedness went unnoticed because Windows updates rarely touched the ESP. That changed as Microsoft started baking update-driven boot manager revisions into cumulative patches.

Resizing the EFI Partition: A Dicey Workaround

Until an official fix arrives, the most direct workaround is to enlarge the EFI System Partition. This is not for the faint of heart. It involves shrinking the adjacent primary partition (usually C:) by at least 100MB, moving the partition boundary, and then extending the ESP into the freed space. A single misstep can render the system unbootable, leading to data loss if backups aren’t available.

The process typically goes like this:

  1. Boot from a Windows 11 installation USB or a live Linux environment.
  2. Launch a partition manager that can handle GPT disks and ESP resizing (such as GParted or the built-in DiskPart in recovery command prompt).
  3. Shrink the C: partition by, say, 200MB from the left side, creating unallocated space immediately after the ESP.
  4. Extend the EFI System Partition into that unallocated space.
  5. Apply changes and reboot, then attempt the update again.

The catch: built-in Windows tools like Disk Management cannot shrink the C: partition leftward, because that requires moving the partition’s start point. Third-party tools are necessary, and they come with their own risks. Even experts hesitate, because a power failure or lockup during the move can corrupt the filesystem. Many users will rightly prefer to wait for a safer, Microsoft‑supplied solution.

What Microsoft Might Do Next

Based on past incidents, Microsoft has several avenues. It could release a revised version of KB5089549 that first checks available ESP space and, if insufficient, stages boot files in a temporary location on the system partition while performing the update. This trick was used once before with a Windows 10 feature update. Alternatively, the company could push a standalone tool that automatically shrinks C: and expands the ESP—similar to how it once offered an “ESP repair” utility for another boot issue. The most ambitious fix would be an update to the Windows servicing stack that pre‑emptively resizes the ESP during the next servicing operation, but that carries heavy testing requirements.

For now, the ball is in Microsoft’s court. The confirmation statement promises eventual action, but no specific patch date. The trouble echoes a similar October 2024 fiasco where some Windows 11 updates failed on systems with a recovery partition that was too small. Then, Microsoft simply advised manually deleting the recovery partition and recreating it—a workaround that also daunted non‑technical users.

Protecting Yourself in the Meantime

If you’re staring at error 0x800f0922 and you’re not comfortable with manual partition surgery, you have a few interim options:

  • Pause updates for a few weeks via Settings > Windows Update > Pause updates. This prevents KB5089549 from repeatedly attempting to install, but leaves other security patches dormant.
  • Check your ESP size without making changes: open an elevated Command Prompt and type mountvol X: /s, then dir X: to see free space. (Replace X with any free drive letter; you’ll need to assign a letter to the EFI partition first.)
  • Defer the specific update using the Microsoft Show or Hide Updates tool, though that’s deprecated and may not work on Windows 11.
  • Escalate to your IT department if you’re on a managed network. They can block the update via Group Policy or Windows Server Update Services until a fix lands.

Above all, don’t ignore the problem. The vulnerabilities patched by KB5089549 are real. If you can safely enlarge the ESP, do it. If not, keep a close eye on the Microsoft support bulletin for KB5089549—that’s where the official resolution will be announced first.

The Bigger Picture

This episode underscores a growing tension in Windows’ evolution. As updates become more holistic—touching firmware, boot components, and deep system files—the once‑set‑and‑forget disk layouts of yesteryear can become liabilities. The EFI partition size isn’t the only forgotten frontier; Microsoft has also wrestled with recovery partitions that were too small for Windows RE updates. The industry trend toward immutable operating systems and containerized updates may eventually render such partitioning woes obsolete, but for the billion‑plus Windows devices already in the field, the past is always present.

KB5089549 is a stark reminder that the 10MB decision made by a technician in 2018 can come back to bite in 2026. The hope is that Microsoft’s acknowledgement, issued promptly once the pattern emerged, signals a faster turnaround than the months‑long waits that characterized earlier servicing woes. For now, affected users are left with a choice: brave the partition‑resizing gauntlet or sit tight with an unpatched machine, hoping the cure arrives before the next zero‑day.