Windows Update error 0x800f0922: how to fix it

Published Sources checked By helps.wiki editorial team

0x800f0922 (CBS_E_INSTALLERS_FAILED) means one of the update's installers failed, so Windows rolled the update back. The code is generic, so the real cause is in CBS.log. Restart, read the log, then work through SFC/DISM and the other fixes.

Applies to:Windows Server2016 (documented by Microsoft)Windows 101909, 22H2 (community-reported)Windows 1121H2, 23H2 (community-reported)Windows Server2019 (community-reported)
On this page

What it means

The code 0x800F0922 is CBS_E_INSTALLERS_FAILED, an error from Component-Based Servicing, the part of Windows that installs updates. While an update installs, it runs several smaller "advanced installers" (Task Scheduler, component installers and similar). If one of them fails, Windows undoes the update, usually after a reboot. That is why you often see the update download, restart your PC, and then come back as failed.

The code itself does not say which installer broke or why. The detail is in C:\Windows\Logs\CBS\CBS.log, and reading it is the quickest way to stop guessing. Search it for Failed execution of queue item and for lines marked (F). A line such as Failed to process advanced operation queue ... [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED] confirms you are in the right place.

Only one cause is documented by Microsoft: a corrupted scheduled task, described for Windows Server 2016. Reports for Windows 10, Windows 11 and Server 2019 come from community and third-party sources, and some Microsoft Q&A threads say generic fixes did not help in every case. So the order below is: simple checks, the log, then the general repairs.

Symptoms and causes

You are likely dealing with this problem if:

  • The update downloads and starts installing, then fails or reverts after a restart.
  • Update history or Event Viewer shows the update as failed with 0x800f0922.
  • CBS.log contains Failed to process advanced operation queue with CBS_E_INSTALLERS_FAILED.

The usual causes, most common first:

Corrupted scheduled task
The task \Microsoft\Windows\PI\SecureBootEncodeUEFI can be corrupted. CBS.log then shows RegisterTask failed 0x80070002 for the Task Scheduler installer. This is the cause Microsoft documents, written for Windows Server 2016.
Damaged system files or component store
Corruption in Windows system files or the component store can make an installer fail (reported by third-party guides).
VPN, proxy or security software
A VPN, proxy, firewall or third-party security product can block the update servers (third-party reports).
Outdated UEFI/BIOS for a Secure Boot update
PCrisk reports this for KB5012170 (the August 2022 Secure Boot DBX update) and attributes the advice to Microsoft; that attribution is unverified.
Low disk space or malware
Not enough free space, or malware interfering with the system, can also make an update fail (third-party reports).

How to fix it

Work through these in order. They start with the quickest, safest checks and move to deeper repairs; stop as soon as the problem is gone.

1.Restart and check the basics

EasyChanges settings

A leftover pending operation or a temporary network problem is the cheapest thing to rule out.

Before you start: Pausing security software lowers your protection. Do it only for the single install attempt, stay off untrusted networks (public Wi-Fi) while it is paused, and turn protection back on right afterwards. Pause the product; do not uninstall it.

  1. Restart the PC, then open Settings > Windows Update and click Check for updates.
  2. Make sure the system drive has comfortable free space.
  3. Disconnect any VPN and turn off any proxy, then try the update again.
  4. If it still fails and you use a third-party antivirus or firewall, pause its protection briefly for one install attempt, then re-enable it immediately, whether or not the update succeeded.

2.Read CBS.log to find the failing installer

Moderate

Because the code is generic, the log tells you which of the remaining fixes actually applies.

  1. Open C:\Windows\Logs\CBS\CBS.log in Notepad (it can be large).
  2. Search for Failed execution of queue item and for lines with (F).
  3. If you see RegisterTask failed 0x80070002 for the Task Scheduler installer, go to the scheduled task fix further down. Otherwise note which installer is named and continue with the general fixes below.

3.Run the Windows Update troubleshooter

Easy

It resets some common update settings automatically.

  1. Open Settings > System > Troubleshoot > Other troubleshooters.
  2. Next to Windows Update, click Run and follow the prompts, then restart and retry the update.

4.Repair system files with SFC and DISM

Easy

Corrupt system files or a damaged component store are among the usual reasons an installer fails.

  1. Open Command Prompt as administrator and run the three commands one after another. Wait for each to finish.
    Command Promptrun as administrator
    sfc /scannow
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
  2. Restart the PC and run Windows Update again.

5.Remove the corrupted SecureBootEncodeUEFI task (Microsoft's fix for Windows Server)

AdvancedBack up first

Use this only if CBS.log shows the RegisterTask failure for the Task Scheduler installer and the task SecureBootEncodeUEFI is the one named. Microsoft documents this fix for Windows Server 2016 (build 14393). Microsoft has not documented or tested it for Windows 10 or Windows 11, so on a home or work client PC treat it as a last resort and ask your IT team first.

Before you start: This deletes registry keys and staged update packages. Create a restore point first and export the keys as shown below. Substitute the real GUID and package names. Do not run this if your log does not match.

  1. Open Command Prompt as administrator and list the staged update packages.
    Command Promptrun as administrator
    Dism /english /online /get-packages /format:table | findstr /i "Staged"
  2. Get the task's GUID from the ID value.
    Command Promptrun as administrator
    reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\PI\SecureBootEncodeUEFI" /v ID
  3. Back up the four registry keys before deleting anything. Replace {GUID} with the value you found.
    Command Promptrun as administrator
    mkdir C:\TaskBackup
reg export "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Maintenance\{GUID}" C:\TaskBackup\maintenance.reg /y
reg export "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Plain\{GUID}" C:\TaskBackup\plain.reg /y
reg export "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tasks\{GUID}" C:\TaskBackup\tasks.reg /y
reg export "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\PI\SecureBootEncodeUEFI" C:\TaskBackup\tree.reg /y
  4. Remove each staged package listed in the first step, replacing the name with the one shown on your PC.
    Command Promptrun as administrator
    Dism /online /remove-package /PackageName:Package_for_RollupFix~31bf3856ad364e35~amd64~~14393XXXX
  5. Delete the task's registry entries, replacing {GUID} with the value you found.
    Command Promptrun as administrator
    reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Maintenance\{GUID}" /f
reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Plain\{GUID}" /f
reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tasks\{GUID}" /f
reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\PI\SecureBootEncodeUEFI" /f
  6. Restart and retry the update. If something goes wrong, double-click the exported .reg files in C:\TaskBackup to restore the keys.

6.Check firmware and scan for malware

AdvancedChanges settings

These are less certain causes, so try them last. An outdated UEFI/BIOS (for KB5012170) is reported by a third-party guide only.

Before you start: A BIOS update should come only from your PC or motherboard maker, and the PC must not lose power during it. Back up your files first.

  1. If the failing update is KB5012170, check your PC or motherboard maker's support page for a newer BIOS/UEFI version and install it using their instructions.
  2. Run a full scan with Windows Security or your installed antivirus to rule out malware.
  3. Resetting Windows is a last resort. Back up your files first.

Check that it worked

  • Open Settings > Windows Update > Update history and check that the update is listed as Successfully installed.
  • After a restart, the update does not roll back and no new 0x800f0922 entry appears.
  • Check for updates once more and confirm Windows reports it is up to date.

If it still fails

  • Read CBS.log (C:\Windows\Logs\CBS\CBS.log) and note which installer is reported as failed. That detail narrows the cause far more than the error code.
  • Try installing the failing update manually if you know its KB number, and check whether the same KB fails every time or only some.
  • If the problem is on a managed work PC or server, give the CBS.log lines to your IT team.
  • Ask on Microsoft Q&A or contact Microsoft Support with the KB number, your Windows version and the CBS.log lines. If you also see permission problems, see Windows Update error 0x80070005.

Questions

Is 0x800f0922 a sign of malware?

Not usually. Malware is listed as a possible cause, but other reasons such as corrupted files, a bad scheduled task or blocked update servers are more likely. A scan is a sensible last check.

Why does the update seem to install and then disappear?

The failure happens during installation, so Windows reverts the changes after restarting. That is the rollback you see.

Sources

  1. Error code 0x800F0922 when installing Windows updates - Windows ServerOfficial · Microsoft Learn
  2. Fix Windows Update Error 0x800f0922 on Windows 11 · PCrisk

Browse