Windows Update Error 0x800f0922: The Partition Problem Nobody Mentions

Error 0x800f0922 almost always means your PC's own storage checker is lying to you: it's not your hard drive that's full, it's a tiny, hidden boot partition most people never knew existed. The fix, in order of how likely it is to work: run the Windows Update Troubleshooter, then free space on that hidden partition (not your C: drive), then repair the update components with DISM and SFC, and only then consider an in-place upgrade. Here's the part nobody tells you up front: Windows isn't checking your hard drive space at all when it throws this error — it's checking a partition that's usually 100 MB, has been 100 MB since the day your PC was built, and never grows no matter how much you delete from your desktop.

Jake had a customer's laptop on the bench for a trade-in valuation — a routine job, twenty minutes, tops. He'd started the Windows update because the trade-in checklist requires the PC to be current before he'll quote a price. Forty minutes later, the laptop was still stuck at "Undoing changes. Don't turn off your computer," the customer was texting him asking if his laptop was broken, and Jake had a queue of three more walk-ins.

"It says my hard drive doesn't have space," Jake said, "but I checked. There's 400 GB free. Why is it lying to me?"

"It's not lying," Ethan said. "It's just not talking about the drive you think it is."

What error 0x800f0922 actually is

0x800f0922 is a code Microsoft's own troubleshooting documentation labels CBS_E_INSTALLERS_FAILED — "Processing advanced installers and generic commands failed." CBS stands for Component-Based Servicing, the system that unpacks and applies every Windows update behind the scenes. When one of those "advanced installer" steps can't finish, Windows rolls the whole update back and hands you this code instead of a plain-English reason.

The single most common trigger, and the one almost every generic "fix Windows Update errors" article skips, is a full System Reserved Partition (on older Master Boot Record disks) or EFI System Partition (on the GPT disks every Windows 11 PC uses). That's a small, separate partition — usually 100–300 MB — that holds boot loader files, not your programs or documents. It's invisible in File Explorer by design. Windows Update needs a little breathing room inside it to stage boot file changes, and on a lot of PCs that partition has been sitting one font file away from full since the day it left the factory.

Fixing 0x800f0922 on Windows 11

Work through these in order. Each one takes longer than the last, so stop as soon as one works.

1. Run the Windows Update Troubleshooter. Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run. On current Windows 11 builds this launches through the Get Help app and runs the same automated diagnostics Microsoft support agents use, catching a wider set of causes than the old standalone tool did.
2. Restart, then retry Windows Update. Sounds too simple to write down, but a reboot clears a stuck update session that can itself look like a partition problem.
3. Check the free space on your EFI System Partition using the steps in the next section. This is the fix that actually resolves most cases, and it's the one almost nobody checks first because the partition doesn't show up anywhere obvious.
4. Temporarily disable third-party antivirus and any VPN client, then retry. Security software that hooks into low-level disk or boot operations can interrupt the same installer phase that throws 0x800f0922.
5. Uninstall Windows Sandbox and Hyper-V if you have them enabled (Win+R > OptionalFeatures.exe), reboot, retry the update, then reinstall them afterward if you use them. Both features hook into virtualization components that occasionally conflict with a pending update.
6. Run DISM and SFC to repair the update components themselves (full commands below), then retry.
7. Do an in-place upgrade repair install if nothing above works. This is the most drastic step, and the last section covers when it's actually worth it.

Fixing 0x800f0922 on Windows 10

These steps are the same on both Windows 10 and 11: the troubleshooter, the antivirus/VPN check, the DISM and SFC repair, and — above all — the reserved partition check. The one Windows 10-specific wrinkle is where you find the troubleshooter and one honest fact about your update situation.

1. Run the troubleshooter. Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update > Run the troubleshooter. Same underlying diagnostics as Windows 11's version, older menu location.
2. Check your System Reserved Partition free space (next section) — on Windows 10, Microsoft's guidance has historically been to free at least 13 MB for a routine quality update and 15 MB for a feature update or version upgrade, so it's a smaller margin than Windows 11 typically needs but just as easy to run out of.
3. Work through the same antivirus/VPN, DISM/SFC, and in-place upgrade steps listed for Windows 11 above — they apply without changes.

The hidden partition problem, explained properly

Every Windows PC has at least one small partition dedicated purely to booting the machine, separate from the partition your files and programs live on. On older BIOS-based PCs it's called the System Reserved Partition. On the UEFI-based PCs that every Windows 11 machine uses, it's the EFI System Partition (ESP). Either way, it's typically formatted at 100–300 MB when the PC ships and is not something Windows expects to grow over the machine's life.

That partition holds the boot manager, boot configuration data, and — this is the part that quietly fills it up — a set of font files Windows uses to render text before the main operating system has even loaded, one set per language the boot screen might need to display. Feature updates and some cumulative updates need to write new boot files into that space during the restart phase. If there isn't enough room, the write fails, CBS rolls the whole update back, and you get 0x800f0922 or its sibling message, "We couldn't update the system reserved partition."

Ethan's take: "This is the single worst-designed part of the whole Windows Update experience, and I'll die on that hill. The error message talks about 'installers failing' when the real problem is a 100 MB partition running out of room for font files nobody asked for. Nothing in the dialog tells you where to look."

The clearest documented example is the May 2026 cumulative update for Windows 11 (KB5089549). Microsoft's own release notes describe the exact symptom: the update installs successfully through its initial phases, then fails during the restart phase at approximately 35–36% completion, rolls back with the message "Something didn't go as planned. Undoing changes," and logs error 0x800f0922. The cause, confirmed in the same release notes, was devices with 10 MB or less free on the EFI System Partition. The update servicing log (CBS.log, stored at C:\Windows\Logs\CBS) recorded entries reading "SpaceCheck: Insufficient free space" and "ServicingBootFiles failed. Error = 0x70" — a direct, documented confirmation that this is a space problem on a partition your normal disk-space indicator never shows you.

How to actually check that partition's free space

Press Win + R — this is the Run box, a small "type a command and hit Enter" tool that's existed in every version of Windows and is faster than digging through Settings once you know it. Type diskmgmt.msc and press Enter to open Disk Management, a system tool for viewing and managing every partition on every drive attached to your PC. Look for a small volume labeled "EFI System Partition," "System Reserved," or sometimes with no label and no drive letter at all — right-click it, choose Properties, and check the free space shown on the General tab.

If the partition shows less than those thresholds free, you've found your cause. If it already shows plenty of room, move on to the other-causes section further down — don't force a partition fix onto a problem that isn't a partition problem.

Freeing space inside the reserved partition

The reserved partition doesn't get a drive letter by default, which is exactly why it fills up unnoticed. You have to temporarily give it one, delete what you can, then remove the letter again.

1. Open Command Prompt as administrator (search for cmd, right-click, "Run as administrator" — on Windows 11, if you don't see that option immediately, look under "Show more options" in the right-click menu, since Microsoft condensed the menu starting with Windows 11 and moved several classic entries there).
2. Run mountvol Y: /s to temporarily assign the letter Y: to the EFI System Partition. (If Y: is already in use on your PC, pick a free letter instead and use it in the steps that follow.)
3. Navigate into the boot font folder: cd /d Y:\EFI\Microsoft\Boot\Fonts
4. List what's there and delete the unnecessary language font files — commonly chs_boot.ttf, cht_boot.ttf, jpn_boot.ttf, and kor_boot.ttf are the largest and safest to remove if you don't need Chinese, Japanese, or Korean characters on the boot screen: del chs_boot.ttf cht_boot.ttf jpn_boot.ttf kor_boot.ttf
5. Check the free space again with dir Y:\ or by reopening Disk Management.
6. Remove the temporary drive letter once you've confirmed more free space is available: reopen Disk Management, right-click the partition, "Change Drive Letter and Paths," select the letter, Remove.
7. Retry Windows Update.

When deleting fonts isn't enough: resizing the partition

Some PCs — particularly from manufacturers that store their own firmware update tools or diagnostic images inside the EFI partition — will still be nearly full after you've deleted every spare font file. In that case, the underlying partition itself is undersized for what's being asked of it, and no amount of file deletion inside it will create meaningful headroom.

The only real fix at that point is resizing the partition, which means shrinking an adjacent partition and growing the reserved one into the freed space. Windows' own Disk Management tool generally can't resize this specific partition type; that's the job of a dedicated third-party partition management tool, used carefully and only after a full backup. Treat this as the step you reach for after the font-file cleanup has genuinely failed to help, not a shortcut around it.

When it isn't the partition: other documented causes

0x800f0922 is a generic failure code covering more than one specific breakdown inside the CBS installer process, so if the partition check comes back clean, don't assume you're stuck — work through these instead.

One narrower, well-documented case involves .NET Framework 3.5. Microsoft's own troubleshooting guidance for .NET Framework installation errors lists 0x800F0922 as a distinct failure that can occur specifically while a Windows 10 or 11 upgrade tries to enable the .NET Framework 3.5 feature, separate from the boot-partition cause above. The documented fix there is different: use Group Policy to point the installer at an "alternate source" — the sources\sxs folder from a mounted Windows installation ISO — rather than Windows Update, then add the .NET Framework feature again through Windows Features. If your error specifically names .NET Framework in the failure message rather than a generic update, this is the branch to follow instead of the partition check.

A second, narrower cause worth checking: the App Readiness service. Microsoft's own support community has documented cases where this service being disabled or stuck interferes with the same installer phase. Open services.msc, find App Readiness, and confirm it's set to Manual (not Disabled) — then try starting it manually and retrying the update.

Repairing update components with DISM and SFC

DISM stands for Deployment Image Servicing and Management — a built-in Windows tool for repairing the underlying system image that updates get applied against. SFC is the System File Checker, an older tool that verifies individual protected system files against known-good copies. Together they're Microsoft's own documented general-purpose repair path for update installers that fail without an obvious cause.

1. Open Command Prompt as administrator.
2. Run DISM /Online /Cleanup-Image /RestoreHealth and let it finish — this can take fifteen minutes or more and downloads replacement files from Windows Update if it finds damage, so a working internet connection matters here.
3. Once that completes, run sfc /scannow to check and repair individual system files.
4. Restart the PC, then retry Windows Update.

If DISM reports it "could not perform the requested operation" or similar, that itself is diagnostic: it usually means the underlying corruption is deep enough that repairing files in place won't help, and you're looking at an in-place upgrade instead.

If your PC asks for a BitLocker recovery key after the fix

Because 0x800f0922 and boot file updates both touch the same low-level startup process that BitLocker (Windows' built-in drive encryption) monitors for tampering, it isn't unusual for a PC to boot into BitLocker recovery mode right after you finally get an update through — Microsoft's own release notes for boot-file servicing updates specifically address this interaction, including a fix in May 2026 for one such case tied to TPM validation settings. If that happens to you, don't panic and don't reinstall Windows: your files are still there, encrypted, waiting for the recovery key. Our walkthrough on finding your BitLocker recovery key after an update covers exactly where Windows stores that key and how to retrieve it.

The nuclear option: an in-place upgrade repair

An in-place upgrade means downloading the current installer for your version of Windows and running it from inside your existing installation, rather than from a bootable USB drive. It reinstalls the operating system's core files while keeping your apps, settings, and personal files intact, and it forces the reserved partition and update components through a full rebuild in the process — which is exactly why it clears up 0x800f0922 cases that survive every targeted fix above.

"It's the last thing you try, not the first," Ethan said, "but I won't pretend it isn't the most reliable one. If you've done the partition check, the DISM repair, and you're still stuck, you're spending more time chasing the error than the repair install would cost you."

Back up your files first regardless — an in-place upgrade is safer than a clean install, but "safer" isn't "risk-free," and no fix in this article is worth losing photos or documents over. If you want to check what's actually in the current cumulative update before you download it, our breakdown of the August 2026 Windows 11 update covers what changed and what's fixed.

Edition and hardware differences worth knowing

Most fixes above work the same on Windows 11 Home and Pro — the partition and installer problem doesn't care which edition you're on. Two exceptions: Hyper-V and Windows Sandbox don't exist on Home, so that step in the causes table simply doesn't apply, and the .NET Framework alternate-source fix uses the Group Policy Editor (gpedit.msc), which is also Pro/Enterprise/Education only. On Home, the equivalent workaround is mounting the ISO and pointing Windows Features at the sources\sxs folder manually when prompted, rather than through a policy setting.

On laptops with a recovery partition from the manufacturer in addition to the EFI System Partition, make sure you're checking the right one in Disk Management — the recovery partition (often several gigabytes, sometimes labeled "Recovery" or "WINRE") is a different volume from the small EFI System Partition this error is actually about. On PCs running inside a virtual machine, the same EFI partition check applies; the fix doesn't change, but resizing it usually means resizing the virtual disk in your hypervisor's settings rather than a physical partition tool.

When nothing here fixes it

If you've freed the reserved partition, run DISM and SFC, and completed an in-place upgrade and 0x800f0922 still appears, the honest next step is Microsoft's own support channel through the Get Help app, with your CBS.log file ready to share — at that point you're dealing with something specific enough to your hardware or firmware that a general how-to article, including this one, can't responsibly guess further. That's not a failure on your part. Some of these are firmware-level quirks from a specific motherboard or laptop model, and Microsoft's support engineers have access to diagnostic detail this article doesn't.

Frequently asked questions

What does error 0x800f0922 mean?

It's Microsoft's code for CBS_E_INSTALLERS_FAILED — a failure inside the Component-Based Servicing process that applies Windows updates. It most often shows up because a small hidden boot partition (the System Reserved Partition or EFI System Partition) doesn't have enough free space to stage the update.

What causes 0x800f0922 on Windows Update?

The leading documented cause is insufficient free space on the reserved boot partition. Other confirmed causes include a .NET Framework 3.5 feature installation failing during an upgrade, the App Readiness service being disabled, third-party antivirus or VPN software interrupting the installer, Hyper-V or Windows Sandbox conflicting with the update, and general corruption in the update servicing components.

How do I fix 0x800f0922 on Windows 11?

Run the built-in Windows Update Troubleshooter first, then check the free space on your EFI System Partition using Disk Management. If both check out, disable third-party security software, remove Hyper-V or Sandbox if installed, run DISM and SFC repairs, and consider an in-place upgrade as a last resort.

How do I fix 0x800f0922 on Windows 10?

The same steps apply as on Windows 11: troubleshooter, partition space check, antivirus/VPN check, DISM and SFC, then an in-place upgrade if needed. The reserved partition on Windows 10 generally needs less free space — around 13 MB for a routine update and 15 MB for a feature update — than the Windows 11 threshold documented in 2026.

How much free space does the System Reserved partition need?

Roughly 13 MB for a routine quality update and 15 MB for a feature update or major version upgrade, per Microsoft's historical guidance. A documented 2026 case on Windows 11 specifically named 10 MB or less as the failure threshold, so more headroom than the bare minimum is always safer.

How do I check how much free space is on my System Reserved partition?

Open Disk Management (Win+R, type diskmgmt.msc), find the small unlabeled or "EFI System Partition" volume, right-click it, choose Properties, and read the free space on the General tab.

Is 0x800f0922 the same as "We couldn't update the system reserved partition"?

They're two different messages for the same underlying cause in most cases. Both indicate the boot partition ran out of room during an update, and the fix is identical either way.

Can I safely delete files from the System Reserved partition?

Only specific files, carefully. The largest, safest candidates are unused language boot font files inside EFI\Microsoft\Boot\Fonts. Deleting anything outside that folder, including the EFI\Boot folder itself, risks making the PC unable to start.

What if I can't find the Fonts folder in the EFI partition?

Confirm you assigned the drive letter correctly with mountvol, and that you're browsing to EFI\Microsoft\Boot\Fonts rather than the partition's root. Some OEM laptops structure the partition slightly differently or store extra manufacturer files there, in which case the largest single file — not necessarily a font — is usually the one worth investigating.

Does resetting Windows Update components fix 0x800f0922?

It can, if the cause is corrupted update components rather than partition space. Running DISM's RestoreHealth option followed by System File Checker addresses that specific case, but won't help if the real problem is a full boot partition.

Will disabling my antivirus fix this error?

Sometimes. Third-party security software that intercepts low-level disk or boot operations has been reported to interrupt the same CBS installer phase this error comes from. It's worth testing after you've ruled out the partition space issue.

Does uninstalling Hyper-V or Windows Sandbox help?

It can in some cases, since both features hook into virtualization components that occasionally conflict with a pending update. Neither exists on Windows 11 Home, so this step doesn't apply there.

Why does my PC go into BitLocker recovery after I fix the update?

Boot file updates and BitLocker's tamper monitoring touch the same low-level startup process, so a PC can occasionally enter recovery mode right after a boot-file update finally installs. Your data isn't lost; you just need the recovery key to unlock the drive.

Is my hard drive failing if I get this error?

Almost certainly not. This error is about a small dedicated boot partition, not your main drive's health, and it appears on healthy drives constantly. Drive failure produces different symptoms, such as read/write errors in other apps or unusual noises on a mechanical drive.

Should I do an in-place upgrade to fix 0x800f0922?

Only after the partition check, the antivirus/VPN check, and a DISM/SFC repair haven't resolved it. It's effective but takes longer and carries more risk than the targeted fixes, so it belongs at the end of the list, not the start.

Is Windows 10 still getting updates if I hit this error post-EOL?

Only if you've enrolled in Extended Security Updates, which covers eligible Windows 10 devices through the program's current end date. Without ESU, Windows 10 no longer receives free security updates, though the operating system continues to boot and run normally.

Revision note. Written August 2026, covering Windows 11 (24H2 and 25H2) and Windows 10 22H2, including the documented EFI System Partition issue from the May 2026 cumulative update and its August 2026 successors. This will need a look whenever Microsoft ships a cumulative update with a new known issue tied to this error code. If you landed here at 11pm with a customer's laptop stuck mid-rollback, take a breath — this one almost always ends with a font file, not a new hard drive.