Flamingo Raises $4.5M Seed Round

Skip to content

Error 0x800f0922: what it means and how to fix it

IT Operations
Troubleshooting
Aliaska VarievaAliaska Varieva
November 9, 2026
15 views
Error 0x800f0922: what it means and how to fix it

Windows Update error 0x800f0922 (CBS_E_INSTALLERS_FAILED) explained: how to read the cause in CBS.log, fixes for a full EFI or System Reserved partition, .NET Framework 3.5, VPN and Secure Boot, and a script that finds the error across a fleet.


Updated: November 2026

Error 0x800f0922 means a Windows update got most of the way through installing, failed during the restart, and rolled itself back. The code is generic, so this guide starts with the log line that names the real cause, then gives the fix for each cause in the order worth trying. The last section finds every device with the same failure across a fleet, before users start reporting it.

TL;DR

  • What it means. CBS_E_INSTALLERS_FAILED: an install step that runs during the reboot failed, and Windows undid the update.
  • Top cause in 2026. A nearly full EFI System Partition, behind the May 2026 KB5089549 failures on Windows 11.
  • Other causes. Full System Reserved partition, .NET 3.5, VPN or proxy, Secure Boot firmware.
  • First move. Search CBS.log before changing anything.
  • Fleet move. Query Event ID 20 and EFI free space on every device.

What does error 0x800f0922 mean?

The code's name is CBS_E_INSTALLERS_FAILED. CBS is Component-Based Servicing, the part of Windows that installs updates. Some of an update's work only runs during the restart, such as writing new boot files. When one of those steps fails, CBS returns 0x800f0922 and reverses the whole update.

You see it in two places. During the restart, the screen says "Something didn't go as planned. Undoing changes." Afterwards, Settings > Windows Update > Update history shows the KB with "Install error - 0x800f0922."

Our guide on how to fix Windows Update errors gives this code one line: free up space, then retry. That's often right, but "space" can mean three different places, and two of them don't show up in File Explorer. Here's how the causes map to what you'll find in the log:

CauseWhat CBS.log showsFix
EFI System Partition nearly fullSpaceCheck: Insufficient free space, ServicingBootFiles failed. Error = 0x70Latest cumulative update, Known Issue Rollback, or free ESP space
System Reserved partition fullERROR_DISK_FULL, or setup says "We couldn't update the system reserved partition"Free space on the partition
.NET Framework 3.5 can't installNetFx3 package lines failing near the errorDISM with a local source
VPN, proxy or blocked update serviceDownload or connection errors before the failureDisconnect and retry
Firmware rejects a Secure Boot updateFailure on a Secure Boot DBX update such as KB5012170UEFI firmware update from the OEM
Corrupt component store0x800f0922 with no clearer line nearbyDISM RestoreHealth, SFC, in-place repair

Log strings for the ESP row come from Microsoft's KB5089549 known issue, as reported by BleepingComputer on 18 May 2026.

This five-minute video makes the same argument: diagnose the cause before you start resetting things.

Step 1. read CBS.log before you fix anything

The log lives at C:\Windows\Logs\CBS\CBS.log. Search it for the code and the space-check lines in one pass, from an elevated prompt:

cmd
findstr /i /c:"0x800f0922" /c:"SpaceCheck" /c:"ERROR_DISK_FULL" /c:"ServicingBootFiles" /c:"NetFx3" C:\Windows\Logs\CBS\CBS.log

If nothing comes back, the failure may have rolled into an older file. Windows compresses old logs into CbsPersist_*.cab files in the same folder, so expand the newest one and search that too.

Note the timestamp of the first error, then read the lines just before it. The line before the code is usually the cause. The code itself is just the summary.

This r/sysadmin thread is a good example of what the hunt looks like. Patches kept rolling back at 99% on a Windows Server upgraded in place, and the 0x800f0922 line only turned up in a truncated CbsPersist cab.

Step 2. check the EFI or system reserved partition

This is the cause behind the biggest 0x800f0922 wave of 2026. The May 12, 2026 security update, KB5089549, failed on some Windows 11 24H2 and 25H2 devices and rolled back at about 35% to 36% of the restart. Microsoft's explanation was limited free space on the EFI System Partition (ESP), "especially when the device has 10 MB or less space available."

The ESP is a small hidden partition, often around 100 MB, that holds the boot manager and boot files. Older BIOS (MBR) installs use a System Reserved partition for the same job. Neither has a drive letter, so a full one never shows up in File Explorer.

Check the free space with PowerShell. The GUID is the standard partition type for an ESP:

powershell
# UEFI devices: EFI System Partition
Get-Partition | Where-Object GptType -eq '{c12a7328-f81f-11d2-ba4b-00a0c93ec93b}' |
  Get-Volume | Select-Object @{n='SizeMB';e={[math]::Round($_.Size/1MB)}}, @{n='FreeMB';e={[math]::Round($_.SizeRemaining/1MB,1)}}

# Older BIOS installs: System Reserved
Get-Volume | Where-Object FileSystemLabel -eq 'System Reserved' | Select-Object Size, SizeRemaining

If the device hit the May 2026 problem, the cleanest fix is a newer update. Microsoft resolved it in the optional KB5089573 update on May 26, 2026, and in every cumulative update since. For managed devices that still had to take the May update, Microsoft also shipped a Known Issue Rollback group policy.

If the partition is still nearly full, free some space. The usual method, documented by Microsoft for the "We couldn't update the system reserved partition" error, is to remove the boot font files from the partition. From an elevated Command Prompt:

cmd
mountvol Y: /s
del Y:\EFI\Microsoft\Boot\Fonts\*.ttf
mountvol Y: /d

One of the log lines Microsoft lists for KB5089549 counts the space "used by third-party/OEM files outside of Microsoft boot directories." Firmware updaters and old diagnostics tools leave files there. Check what's in Y:\EFI before you unmount, and don't delete another vendor's bootloader on a dual-boot machine. Resizing the partition is the last resort, and it means a third-party partition tool or a rebuild.

Step 3. repair .NET framework 3.5

If CBS.log shows NetFx3 failing near the error, the update is choking on the .NET Framework 3.5 feature. Reinstall it from install media that matches the device's Windows version and build. Mount the ISO, note its drive letter, then run:

cmd
DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:D:\sources\sxs

Replace D: with the mounted ISO's letter. /LimitAccess stops DISM from reaching out to Windows Update, which is the thing that's already failing.

Step 4. rule out VPN, proxy and Secure Boot

A VPN or a proxy can cut the device off from the update service partway through. Disconnect the VPN, retry the update, and check that nothing in Group Policy points the device at a WSUS server that no longer exists.

Secure Boot updates have their own version of this error. When Microsoft shipped the Secure Boot DBX update KB5012170 in August 2022, it warned that some devices would fail with 0x800f0922. The fix was a UEFI firmware update from the device maker, not anything inside Windows. If the failing KB is a Secure Boot update, update the firmware first. Our guide to what a BIOS update is covers doing that safely.

Step 5. repair the component store

When the log has nothing clearer than the code itself, repair Windows' own servicing files, then reset the update cache:

cmd
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
net stop wuauserv & net stop cryptsvc & net stop bits
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start bits & net start cryptsvc & net start wuauserv

Restart and retry the update. If it still fails, an in-place repair upgrade from matching install media reinstalls Windows while keeping apps and files. It's slower than DISM, but it fixes servicing damage DISM can't reach.

How to find 0x800f0922 across a fleet

One device with this error is a ticket. Fifty devices with it is a patch compliance hole that a monthly report shows three weeks late.

Windows logs every failed install as Event ID 20 from the WindowsUpdateClient source in the System log, with the error code and KB in the message. This script reports the failures from the last 30 days alongside ESP free space, so you see the cause and the symptom in one row:

powershell
$fail = Get-WinEvent -FilterHashtable @{
  LogName='System'; ProviderName='Microsoft-Windows-WindowsUpdateClient'; Id=20
  StartTime=(Get-Date).AddDays(-30)
} -ErrorAction SilentlyContinue | Where-Object Message -match '0x800f0922'

$esp = Get-Partition | Where-Object GptType -eq '{c12a7328-f81f-11d2-ba4b-00a0c93ec93b}' | Get-Volume

[pscustomobject]@{
  Computer  = $env:COMPUTERNAME
  Failures  = @($fail).Count
  LastKB    = if ($fail) { [regex]::Match($fail[0].Message, 'KB\d+').Value }
  EspFreeMB = [math]::Round($esp.SizeRemaining / 1MB, 1)
}

Run it as a scheduled script across every device. In OpenFrame, scheduled scripts target groups and can run when a device comes back online, so laptops that were off on Patch Tuesday still report. Any RMM that runs PowerShell does the same job. Sort by EspFreeMB. Anything near Microsoft's 10 MB line is next month's failure, so clear it now, before the next cumulative update lands.

Failures that come back after a fix belong in your patch compliance view, not in a pile of single tickets. Our piece on the last 10% of patching covers how to chase the stragglers.

The short version

0x800f0922 is a summary, not a diagnosis. Read CBS.log first and the line before the code tells you which fix to run. In 2026, the likeliest answer is a nearly full EFI partition, so check it with one PowerShell line and install a current cumulative update. Then run the fleet script once, because the device that told you about the problem is rarely the only one with it.

Aliaska Varieva

Aliaska Varieva

VP of Engineering

Hi! I’m Aliaska, and I’ve been working as a software engineer (mostly Java + a bit Kotlin) for over 8 years now. I mostly spend my time building backend services, integrating systems, fixing bugs (the fun part 🙃), and making sure things don’t fall apart behind the scenes.

Related Content

Frequently Asked Questions

/blog/0x800f0922

Still deciding?

Ask Mingo answers from our docs and customer stories.

Loading related content and questions