Microsoft's May 12, 2026 security update for Windows 11, KB5089549, is failing to install on some PCs with error 0x800f0922 — and the usual fix of clearing space on the C: drive won't help. The real bottleneck is a tiny, hidden partition most users never see: the EFI System Partition. When free space there drops to 10 MB or less, the update can hit a wall, even if you have hundreds of gigabytes free elsewhere.

What Actually Changed With KB5089549

KB5089549 is a standard Patch Tuesday security release, bringing Windows 11 24H2 to build 26100.8457 and 25H2 to build 26200.8457. Alongside the usual fixes, Microsoft quietly documented a known issue: installation may fail with error code 0x800f0922 on devices where the EFI System Partition has "very limited free space," especially when that space is 10 MB or below.

The EFI System Partition is a small, boot-critical slice of your drive — typically 100–500 MB — that stores the Windows Boot Manager and other startup files. It has no drive letter, so it's invisible in File Explorer, and standard disk-cleanup tools don't touch it. That's why a computer can report 300 GB free on C: yet still be blocked from applying a security patch.

This isn't a bug in the update code. It's a consequence of servicing stack operations that need temporary working room on the EFI partition during installation. Microsoft's documentation is clear: the error 0x800f0922 doesn't always mean an EFI space issue, but when that partition is critically low, it's the leading suspect.

Who's at Risk and How to Tell If It's You

The problem affects Windows 11 24H2 and 25H2 devices. (Older releases like 22H2 or 23H2 are not in scope.) If you see KB5089549 repeatedly fail with 0x800f0922 — often after appearing to download, then installing for several minutes, then rolling back — you may be hitting this condition.

Home users will likely encounter this as a stubborn update that refuses to install no matter how many times they retry or run the Windows Update troubleshooter. IT admins managing fleets may notice a cluster of failures across specific laptop models, especially those with older deployment images or disk layouts inherited from upgrades rather than clean installs.

The only way to know for sure is to measure free space on the EFI System Partition directly. Microsoft hasn't surfaced that figure in the Settings app or default system reports, so it takes a deliberate check.

Why Clearing Space on C: Won't Fix It

When Windows warns about low disk space, it usually points to the volume where your documents, apps, and temporary files live — almost always C:. So the natural first response is to delete downloads, empty the Recycle Bin, or run Storage Sense. For KB5089549, that's a red herring.

The EFI partition lives outside the C: volume entirely. It's a separate partition created when the operating system was installed, formatted with the FAT32 file system. User cleanup never touches it because user cleanup never goes there. Even if you free 100 GB on C:, the EFI partition stays exactly as cramped as before.

This misdirection has played out in support threads. On Microsoft's own Q&A forum, a user reported KB5089549 failing despite having "verified disk space," clearly checking C: and finding it healthy. They then went through the standard Windows Update repair steps — restarts, service resets, SoftwareDistribution folder cleanouts — none of which addressed the EFI partition. It's a perfect example of why the known-issue documentation matters: it steers the diagnosis away from dead-end fixes.

What This Means for You — Split by Audience

For Home Users

You're probably not equipped — nor should you be — to go messing around in the boot partition. The safest path is awareness. If KB5089549 keeps failing with error 0x800f0922 and you've already run the usual troubleshooting, point your support contact toward the EFI space known issue. The simple message: "The update may be blocked by a hidden boot partition, not my personal files."

Avoid any online advice that tells you to delete files from the EFI partition manually. That partition contains files critical for starting your PC, and removing the wrong one can turn an update failure into a computer that won't boot. You can, however, perform a safe read-only measurement if you're comfortable with PowerShell (see the verification section below). But for most, the right move is to wait for additional guidance from Microsoft or your PC manufacturer.

For Power Users and Tinkerers

You might have a system that's been upgraded across several Windows versions, cloned to a larger drive with a third-party tool, or dual-booted with Linux. Each of those paths can leave the EFI partition smaller than it needs to be. The first step is to check. Open an elevated PowerShell prompt and run:

mountvol S: /S
$drive = Get-PSDrive S
[PSCustomObject]@{
    ComputerName = $env:COMPUTERNAME
    EFIFreeMB    = [math]::Round($drive.Free / 1MB, 2)
    EFIUsedMB    = [math]::Round($drive.Used / 1MB, 2)
}
mountvol S: /D

This temporarily assigns the EFI partition to the S: drive, reads the free space, and then removes the mapping. If the free space is 10 MB or less, you've found the likely blocker. Back up your system before attempting any partition resizing. Many OEMs provide recovery tools that can rebuild the EFI partition safely, but it's not a casual operation. For now, the verification itself is the most valuable step.

For IT Administrators and Managed Fleets

A single laptop failing an update is a ticket. A dozen laptops from the same model failing is a pattern — and probably an image or provisioning issue. KB5089549's known issue gives you a concrete signal to act on.

  • Confirm the scope. Gather device name, Windows version, failing update (KB5089549), error code (0x800f0922), hardware model, and original OS image.
  • Measure EFI free space on all affected devices. Use a script — like the one above adapted to your remote management tool — and flag any device with 10 MB or less free.
  • Classify the device. A "confirmed known-issue candidate" is one running 24H2/25H2, failing KB5089549 with 0x800f0922, and at or below the 10 MB threshold. Possible candidates have the error but free space slightly above 10 MB and may still warrant investigation.
  • Correlate across the fleet. Group failures by OEM model, firmware version, original deployment image, and upgrade history. If a cluster emerges, stop treating these as individual help-desk problems. Escalate to endpoint engineering and OS deployment teams.
  • Assign ownership. Help desk verifies the condition; endpoint engineering designs the remediation; platform owners review disk-layout standards; compliance tracks devices as blocked by a servicing prerequisite, not as overdue patching.

Above all, do not keep pushing the update to confirmed low-space devices. It will continue to fail, and each attempt eats time and user confidence. Remediate the partition constraint first.

How We Got Here: A Familiar Pattern With a New Clue

Windows admins have seen update failures blamed on disk space for years, but rarely with this level of specificity. Earlier patch cycles generated similar user frustration. On Windows 10, KB5053606 triggered reports of failed installs and performance issues; on Windows 11, KB5048685, KB5050094, and others led to long community threads filled with the same troubleshooting loops. In most of those cases, the root cause was murky, and the conversation rarely moved beyond "clear space on C:" and "run the troubleshooter."

KB5089549 is different because Microsoft has explicitly named the EFI System Partition as a potential blocker. That changes the support dynamic from a guessing game to a measurable diagnostic. The value isn't just in solving today's problem — it's in establishing a workflow for the next update that hits the same hidden ceiling.

This also highlights a long-standing gap in Windows' self-reporting. The operating system can tell you how much space is left on your documents drive, but it won't proactively warn you that the boot partition is nearly full, even when that condition makes the machine unable to accept security fixes. It's a reminder that the visible system health indicators don't tell the whole story.

What to Do Now — Practical Steps at a Glance

  • Stop retrying. If KB5089549 has failed multiple times with 0x800f0922, additional attempts won't help until the EFI space issue is addressed.
  • Check your Windows version. This known issue applies only to 24H2 and 25H2. Confirm your build (Settings > System > About, or run winver).
  • Measure EFI free space. Use the PowerShell snippet above if you're comfortable; otherwise, ask your IT support to perform the check.
  • Do not delete files from the EFI partition. Even for power users, it's too easy to break the boot process. Wait for documented, supported remediation steps from Microsoft or your hardware vendor.
  • Escalate appropriately. If you're in an organization, report the measured EFI free space alongside the error code. Let the teams that own disk layout and deployment handle partition changes.

For managed environments, a short-term mitigation is to ensure new device provisioning includes an EFI partition large enough — 200 MB or more is typical, but some images have been as low as 100 MB. If you're imaging Windows 11 24H2 today, check that your image template allocates sufficient space.

Outlook: What to Watch Next

Microsoft will likely update the known-issue documentation as more data comes in. In similar past cases, the company has provided either a manual workaround (like a script to extend the partition) or a revised update that is less sensitive to EFI space. There's no guarantee of a zero-touch fix, though, because partition geometry is a foundational part of a device's layout.

The broader takeaway is that update blocking can happen for reasons completely invisible to the user — and to many management dashboards. Until Windows has built-in low-EFI-space alerts, fleet owners would do well to include EFI free space in their regular health checks. The next Patch Tuesday might not repeat this exact issue, but the principle will hold: when a security update fails despite ample C: drive space, check the hidden partitions.