Fix error 0x800f0922

0x800f0922 is CBS_E_INSTALLERS_FAILED: processing advanced installers and generic commands failed, so Windows rolled the update back. Microsoft links it on Windows 11 to low disk space or a problem with .NET Framework or another component. Free space, disconnect any VPN, restart, and install the update again before trying deeper repairs.

Checked November 10, 2026 against the manufacturer's own pages.

The short version

What to install and where it comes from. Every link goes to the manufacturer or Microsoft, never to a copy.

Code0x800f0922
Official nameCBS_E_INSTALLERS_FAILED
Where it appearsCumulative updates in Windows Update, Windows upgrades, and .NET Framework 3.5 installs
Most common causeInsufficient disk space, a VPN connection, or a failing component installer such as .NET Framework
Windows versionsWindows 11, Windows 10 and Windows Server 2016 or later
Microsoft Support: Troubleshoot problems updating Windowssupport.microsoft.comMicrosoft Learn: Common Windows Update errors (0x800f0922)learn.microsoft.comMicrosoft Learn: .NET Framework 3.5 installation errorslearn.microsoft.com

Official files only, nothing bundled

Step by step

  1. Disconnect from any VPN

    Microsoft's Windows 11 list names a VPN as one cause. Turn off the VPN app or remove the connection under Settings, Network and internet, VPN, then try Windows Update on a normal home or office connection.

  2. Make room on the system drive

    Open Settings, System, Storage and use Cleanup recommendations or Temporary files. Insufficient disk space is the first cause Microsoft lists for this code on Windows 11.

  3. Restart and retry the same update

    Choose Start, Power, Restart. Then go to Settings, Windows Update and select Check for updates. A clean restart clears pending operations before the second attempt.

  4. Run the update troubleshooter

    Open Settings, System, Troubleshoot, Other troubleshooters and run Windows Update. It resets services and caches that a failed install can leave in a bad state.

  5. Repair the servicing store

    From an elevated Command Prompt, run dism /online /Cleanup-Image /RestoreHealth, then sfc /scannow. Microsoft's .NET 3.5 article ends its 0x800f0922 steps with this same RestoreHealth command.

  6. Check .NET Framework 3.5 if it is involved

    If the failure came while adding .NET 3.5, mount an ISO of your Windows version and run dism /online /enable-feature /featurename:netfx3 /all /source:D:\sources\sxs /limitaccess with the mounted drive letter.

Faster option: let a PC tool do the clean-up

The steps above fix this error. Errors like this often come back on a PC full of junk files, broken registry entries and leftovers from removed programs. A maintenance tool clears those in one scan.

Scan and clean up Windows

Finds junk files, invalid registry entries, startup slowdowns and privacy traces, then fixes them in one click.

Auslogics BoostSpeed 14 · Free version · Windows 11, 10, 8, 7 · 30-day refund on Pro

What happens before you see 0x800f0922

Microsoft’s full message for this code is “Processing advanced installers and generic commands failed.” In plain terms, the update’s files arrived, but one of the setup actions that runs while the update is applied did not succeed. The servicing stack then reverts the update, and the code is recorded in Settings, Windows Update, Update history. Microsoft’s first fixes are about disk space and the network path, not about downloading again.

Matching the cause to what you see

Microsoft gives three different stories for this code, and each points to its own fix. On Windows 11 home PCs, the support page links it to low disk space, a VPN, or a .NET Framework component. When you add .NET Framework 3.5, the fix is a local source from installation media plus a component store repair. On Windows Server 2016, Microsoft traced one wave of failures to licence token updates and folder permissions.

Less common: permissions on the Software Protection folder

The server case is worth knowing because the symptom looks like any other failed update. CBS.log shows the rollback happens after licence and product key tokens fail to update. Microsoft’s fix is narrow: add write permission for the User and Network Service accounts on C:\Windows\System32\spp, then install again. Make no other permission changes there.

Questions

What does processing advanced installers mean?

It is the stage Microsoft's error text names: after files are staged, the servicing stack runs extra setup actions for components. If one of them fails, the update cannot complete and is reverted.

Is 0x800f0922 only a .NET problem?

No. Microsoft notes the code is not specific to .NET Framework. It appears on monthly updates and upgrades too.

How do I find which installer failed?

Open C:\Windows\Logs\CBS\CBS.log, search for 0x800f0922 and read the lines just above it. They name the installer or component that stopped.

My server shows it after a cumulative update. Any known fix?

Microsoft documents one Windows Server 2016 case where licence and product key tokens failed to update. It was fixed by giving the User and Network Service accounts write permission on C:\Windows\System32\spp.