Why are we getting "Package KB5053887 failed to be changed to the Installed state. Status: 0x800f0922."

Question

We have a server that we have purchased Windows server 2012 extended support updates for.

It currently does not have an internet connection, and we need to apply the updates manually.

The server is running server 2012R2, and we have succesfully installed KB5052108 (using DISM.exe) - which is the service stack update. We have rebooted.

We are now trying to install KB5053887, using the command

dism /online /add-package /packagepath:"windows8.1-kb5053887-x64.cab"

( I am running this command from c:\temp which is where the cab file is)

Why are we getting "Package KB5053887 failed to be changed to the Installed state. Status: 0x800f0922." when trying to install KB5053887 ?

Are additional files needed ?

The computer does not have an internet connection.

in the registry, in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP the Key with value Start is set to 3

There is plenty of disk space. We have run sfc /scannow and it does not indicate any issues.

Post reboot the windows setup log has 3 messages:

1. After the initial install it says

Initiating changes for package KB5053887. Current state is Staged. Target state is Installed. Client id: DISM Package Manager Provider.

2. Then:

A reboot is necessary before package KB5053887 can be changed to the Installed state.

3. So we reboot, and then we get:

Package KB5053887 failed to be changed to the Installed state. Status: 0x800f0922.

The initial output from the DISM tool is

c:\Temp>dism /online /add-package /packagepath:"windows8.1-kb5053887-x64.cab"

Deployment Image Servicing and Management tool

Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~

~9600.22470.1.16

[==========================100.0%==========================]

The operation completed successfully.

Restart Windows to complete this operation.

Do you want to restart the computer now? (Y/N)

So appears successful, but after reboot we see message 3) in the event log.

The CBS.log also has an error:

2025-03-16 13:02:11, Info CSI 000002a0 Begin executing advanced installer phase 50 (0x00000032) index 0 (sequence 0)

Old component: [l:0]""

New component: [l:0]""

Install mode: uninstall

Installer ID: {4006c604-9280-4d68-b731-2fe3d02e84bf}

Installer name: [16]"Shortcut Tickler"

2025-03-16 13:02:11, Info CSI 000002a1@2025/3/16:13:02:11.606 CSI Advanced installer perf trace:

CSIPERF:AIDONE;{4006c604-9280-4d68-b731-2fe3d02e84bf};(null);472us

2025-03-16 13:02:11, Info CSI 000002a2 End executing advanced installer (sequence 0)

Completion status: S_OK 

2025-03-16 13:02:12, Info CBS Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Percent progress: 99.

2025-03-16 13:02:12, Info CBS Winlogon: TiCoreOnCreateSession has been called

2025-03-16 13:02:17, Error CBS Startup: Failed to process advanced operation queue, startupPhase: 0. A rollback transaction will be created. [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]

Answer 1

Hello,

This error (0x800f0922) means that even though DISM staged the update, one or more components inside the package couldn’t finish installing. In many cases it isn’t a “disk space” or “HTTP service” issue at all—it’s that the update installer hit a dependency or prerequisite “gap” that prevents the package from fully committing.

In our situation the update KB5053887 is designed to patch Windows Server 2012R2 (which shares its code base with Windows 8.1), and work went into having the proper servicing stack (that is, KB5052108) in place. However, when you’re offline you can run into a few common issues:

• Missing prerequisites that under normal circumstances are pulled in from Windows Update. Even though the service‐stack update was applied, KB5053887 might be expecting other components (or at least a “healthy” servicing environment) that it can’t find because the machine isn’t online.

• Sometimes the update’s “inner” installer (the advanced installer step that you see in the CBS logs—for example, the part with “Shortcut Tickler”) fails. This failure can happen if the current installation isn’t exactly what the update expects (for example, if some legacy or superseded component is still present). In this log you see that while DISM staged the package, on reboot the system is trying to commit changes and something isn’t “happy.”

• While the registry settings and available disk space look okay, the installation might be trying to update a component that was either updated already or that needs to be uninstalled first; the “advanced operation queue” error in CBS (CBS_E_INSTALLERS_FAILED) is generally an indicator that one of the installer operations (internal to the package) did not complete successfully.

To troubleshoot and work around this error you might try the following steps:

1. Verify that the servicing stack update (KB5052108) truly got applied correctly. Running a DISM /Online /Cleanup-Image /ScanHealth (and perhaps /RestoreHealth) might catch some hidden corruption before the update is processed.
2. Double-check prerequisites for the update offline. Although the update ZIP/CAB file is “self-contained,” sometimes additional “dependency packages” (for instance, optional .NET or platform updates) need to be installed manually when there’s no Internet connection.
3. Look more carefully at the CBS.log and Setup logs (beyond the small extract provided) to see which component is stumbling (for example, the entry mentioning “Shortcut Tickler”). That may provide a clue as to whether a component is out-of-date, already installed, or simply unresponsive to the update’s instructions.
4. If possible, try to install the update on a test machine (or connect the machine temporarily to the Internet) so that Windows Update can “fill in” any missing files. Once the update is committed, you might be able to disconnect the connection again.

For many administrators installing extended support updates offline, it comes down to making sure that all prerequisites are installed—and that the image is in the expected “clean” state. Once you’ve ensured that, the error 0x800f0922 (“CBS_E_INSTALLERS_FAILED”) should clear.

---

If the Answer is helpful, please click "Accept Answer" and upvote it.