Solved Windows 11 24H2 update kb5044284 fails on reboot at 40%, error 0x800f0922

Desktop PC running Windows 11 24H2 26100.1742, I got the update for KB5044284.

This downloaded and extracted fine, then started to install. The update got to the 30% and restarted the PC.
On the reboot the update continued until 40%, when it hung for about 8 minutes, then gave an on screen error message (with no reference) and rolled back.

Windows Update shows the error as 0x800f0922.

Have you checked the CBS log(s)? That will contain greater detail on what the error is being caused by.

lafargeotte said:

Desktop PC running Windows 11 24H2 26100.1742, I got the update for KB5044284.

This downloaded and extracted fine, then started to install. The update got to the 30% and restarted the PC.
On the reboot the update continued until 40%, when it hung for about 8 minutes, then gave an on screen error message (with no reference) and rolled back.

Windows Update shows the error as 0x800f0922.
View attachment 111753

Click to expand...

Do you use VPN connection ?

Torus said:

Have you checked the CBS log(s)? That will contain greater detail on what the error is being caused by.

Click to expand...

Here is the relative CBS log entry, any ideas please:
2024-10-09 14:14:44, Info CBS TI: --- Initializing Trusted Installer ---
2024-10-09 14:14:44, Info CBS TI: Last boot time: 2024-10-09 13:58:01.500
2024-10-09 14:14:44, Info CBS Starting TrustedInstaller initialization.
2024-10-09 14:14:44, Info CBS Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:4
2024-10-09 14:14:44, Info CBS Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:5
2024-10-09 14:14:44, Info CBS Lock: New lock added: WinlogonNotifyLock, level: 8, total lock:6
2024-10-09 14:14:44, Info CBS Ending TrustedInstaller initialization.
2024-10-09 14:14:44, Info CBS Starting the TrustedInstaller main loop.
2024-10-09 14:14:44, Info CBS TrustedInstaller service starts successfully.
2024-10-09 14:14:44, Info CBS No startup processing required, TrustedInstaller service was not set as autostart
2024-10-09 14:14:44, Info CBS Startup processing thread terminated normally
2024-10-09 14:14:44, Info CBS TI: Startup Processing completes, release startup processing lock.
2024-10-09 14:14:44, Info CBS Starting TiWorker initialization.
2024-10-09 14:14:44, Info CBS Lock: New lock added: TiWorkerClassFactory, level: 30, total lock:2
2024-10-09 14:14:44, Info CBS Ending TiWorker initialization.
2024-10-09 14:14:44, Info CBS Starting the TiWorker main loop.
2024-10-09 14:14:44, Info CBS TiWorker starts successfully.
2024-10-09 14:14:44, Info CBS No content found - 'C:\WINDOWS\CbsTemp\._ForDelete\'
2024-10-09 14:14:44, Info CBS No content found - 'C:\WINDOWS\SystemTemp\CbsTemp._ForDelete'
2024-10-09 14:14:44, Info CBS Priority: Restoring default priority
2024-10-09 14:14:44, Info CBS Lock: New lock added: CCbsWorker, level: 5, total lock:3
2024-10-09 14:14:44, Info CBS Universal Time is: 2024-10-09 12:14:44.588
2024-10-09 14:14:44, Info CBS Loaded Servicing Stack v10.0.26100.2032 with Core: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.26100.2032_none_a54f556d772e44b1\cbscore.dll
2024-10-09 14:14:44, Info CBS Build: 26100.1.amd64fre.ge_release.240331-1435
2024-10-09 14:14:44, Info CBS Current Overlay Status: 0, Velocity configured status: 0
2024-10-09 14:14:44, Info CSI 00000001@2024/10/9:12:14:44.590 WcpInitialize: wcp.dll version 10.0.26100.2032 (WinBuild.160101.0800)
2024-10-09 14:14:44, Info CBS TurboContainer load Successful
2024-10-09 14:14:44, Info CBS Lock: New lock added: CCbsSessionManager, level: 11, total lock:9
2024-10-09 14:14:44, Info CBS Lock: New lock added: CSIInventoryCriticalSection, level: 64, total lock:10
2024-10-09 14:14:44, Info CBS NonStart: Set pending store consistency check.
2024-10-09 14:14:44, Info CBS Module starts contributing to an existing logging session
2024-10-09 14:14:44, Info SXS TurboStack version 10.0.26100.2032 (WinBuild.160101.0800) loaded from C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.26100.2032_none_a54f556d772e44b1
2024-10-09 14:14:44, Info CSI 00000002@2024/10/9:12:14:44.621 WcpInitialize: wcp.dll version 10.0.26100.2032 (WinBuild.160101.0800)
2024-10-09 14:14:44, Info CSI 00000003 Perf: LRU Cache Initialize @0x207078963e0; Maximum Size: 1024 MiB; Initial Elements: 8192
2024-10-09 14:14:44, Info SXS Initialized store, arch=amd64, style=Desktop, compact=false, windir=(null), sandbox=
2024-10-09 14:14:44, Info CBS Session: 31136324_3548557668 initialized by client WindowsUpdateAgent
2024-10-09 14:14:44, Info CBS InternalOpenPackage failed for Package_for_KB3025096~31bf3856ad364e35~amd64~~6.4.1.0 [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2024-10-09 14:14:44, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2024-10-09 14:14:44, Info CBS Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2024-10-09 14:14:44, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2024-10-09 14:14:44, Info CSI 00000004 Perf: LRU Cache Clear @0x207078963e0
2024-10-09 14:14:44, Info CBS Module starts contributing to an existing logging session
2024-10-09 14:14:44, Info SXS TurboStack version 10.0.26100.2032 (WinBuild.160101.0800) loaded from C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.26100.2032_none_a54f556d772e44b1
2024-10-09 14:14:44, Info CSI 00000005@2024/10/9:12:14:44.627 WcpInitialize: wcp.dll version 10.0.26100.2032 (WinBuild.160101.0800)
2024-10-09 14:14:44, Info CSI 00000006 Perf: LRU Cache Initialize @0x20707896d40; Maximum Size: 1024 MiB; Initial Elements: 8192
2024-10-09 14:14:44, Info SXS Initialized store, arch=amd64, style=Desktop, compact=false, windir=(null), sandbox=
2024-10-09 14:14:44, Info CBS Session: 31136324_3548597907 initialized by client WindowsUpdateAgent
2024-10-09 14:14:44, Info CBS InternalOpenPackage failed for Package_for_KB3025096~31bf3856ad364e35~x86~~6.4.1.0 [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2024-10-09 14:14:44, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2024-10-09 14:14:44, Info CBS Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2024-10-09 14:14:44, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2024-10-09 14:14:44, Info CSI 00000007 Perf: LRU Cache Clear @0x20707896d40
2024-10-09 14:14:45, Info CBS WU creates the package, AppID:MoUpdateOrchestrator, UpdateID:{33D6CF13-224E-459B-AD4F-AF8C5E3CC469}, revision: 202
2024-10-09 14:14:45, Info CBS Module starts contributing to an existing logging session
2024-10-09 14:14:45, Info SXS TurboStack version 10.0.26100.2032 (WinBuild.160101.0800) loaded from C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.26100.2032_none_a54f556d772e44b1
2024-10-09 14:14:45, Info CSI 00000008@2024/10/9:12:14:45.628 WcpInitialize: wcp.dll version 10.0.26100.2032 (WinBuild.160101.0800)
2024-10-09 14:14:45, Info CSI 00000009 Perf: LRU Cache Initialize @0x207078965c0; Maximum Size: 1024 MiB; Initial Elements: 8192
2024-10-09 14:14:45, Info SXS Initialized store, arch=amd64, style=Desktop, compact=false, windir=(null), sandbox=
2024-10-09 14:14:45, Info CBS Session: 31136324_3558622341 initialized by client WindowsUpdateAgent
2024-10-09 14:14:45, Info CSI 0000000a Perf: LRU Cache Clear @0x207078965c0
2024-10-09 14:14:46, Info CBS WU creates the package, AppID:MoUpdateOrchestrator, UpdateID:{33238534-6440-4232-9A18-E7A602E51BE6}, revision: 201
2024-10-09 14:14:46, Info CBS Module starts contributing to an existing logging session
2024-10-09 14:14:46, Info SXS TurboStack version 10.0.26100.2032 (WinBuild.160101.0800) loaded from C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.26100.2032_none_a54f556d772e44b1
2024-10-09 14:14:46, Info CSI 0000000b@2024/10/9:12:14:46.060 WcpInitialize: wcp.dll version 10.0.26100.2032 (WinBuild.160101.0800)
2024-10-09 14:14:46, Info CSI 0000000c Perf: LRU Cache Initialize @0x207078967a0; Maximum Size: 1024 MiB; Initial Elements: 8192
2024-10-09 14:14:46, Info SXS Initialized store, arch=amd64, style=Desktop, compact=false, windir=(null), sandbox=
2024-10-09 14:14:46, Info CBS Session: 31136324_3562925596 initialized by client WindowsUpdateAgent
2024-10-09 14:14:46, Info CBS Appl: detect Parent, Package: Package_for_KB3064238~31bf3856ad364e35~amd64~~10.0.1.2, Parent: Microsoft-Windows-Presentation-Package~31bf3856ad364e35~amd64~~10.0.10074.0, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: GE, Exist: present
2024-10-09 14:14:46, Info CBS Appl: detectParent: related parent found: Microsoft-Windows-Presentation-Package~31bf3856ad364e35~amd64~~10.0.26100.1, which is not real parent
2024-10-09 14:14:46, Info CBS Appl: detectParent: no parent found, go absent
2024-10-09 14:14:46, Info CBS Appl: detect Parent, Package: Package_for_KB3064238~31bf3856ad364e35~amd64~~10.0.1.2, Parent: Microsoft-Windows-Presentation-Package~31bf3856ad364e35~amd64~~10.0.10115.0, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: GE, Exist: present
2024-10-09 14:14:46, Info CBS Appl: detectParent: related parent found: Microsoft-Windows-Presentation-Package~31bf3856ad364e35~amd64~~10.0.26100.1, which is not real parent
2024-10-09 14:14:46, Info CBS Appl: detectParent: no parent found, go absent
2024-10-09 14:14:46, Info CBS Appl: detect Parent, Package: Package_for_KB3064238~31bf3856ad364e35~amd64~~10.0.1.2, Parent: Microsoft-Windows-Presentation-Package~31bf3856ad364e35~amd64~~10.0.10122.0, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: GE, Exist: present
2024-10-09 14:14:46, Info CBS Appl: detectParent: related parent found: Microsoft-Windows-Presentation-Package~31bf3856ad364e35~amd64~~10.0.26100.1, which is not real parent
2024-10-09 14:14:46, Info CBS Appl: detectParent: no parent found, go absent
2024-10-09 14:14:46, Info CBS Appl: Evaluating package applicability for package Package_for_KB3064238~31bf3856ad364e35~amd64~~10.0.1.2, applicable state: Absent
2024-10-09 14:14:46, Info CBS External EvaluateApplicability - Current state, package: Package_for_KB3064238~31bf3856ad364e35~amd64~~10.0.1.2, package current state: Absent, lowest rollup current state: Absent, resulting current state: Absent
2024-10-09 14:14:46, Info CSI 0000000d Perf: LRU Cache Clear @0x207078967a0
2024-10-09 14:16:46, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2024-10-09 14:16:46, Info CBS TiWorker signaled for shutdown, going to exit.
2024-10-09 14:16:46, Info CBS Waiting for any outstanding sessions to complete
2024-10-09 14:16:46, Info CBS Outstanding sessions complete
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2024-10-09 14:16:46, Info CBS Execution Engine Finalize
2024-10-09 14:16:46, Info CBS Execution Engine Finalize
2024-10-09 14:16:46, Info CBS Execution Engine Finalize
2024-10-09 14:16:46, Info CBS Execution Engine Finalize
2024-10-09 14:16:46, Info CBS Completed cleanup thread
2024-10-09 14:16:46, Info CBS Lock: Lock removed: TiWorkerClassFactory, level: 30, total lock:3
2024-10-09 14:16:46, Info CBS Lock: Lock removed: CCbsWorker, level: 5, total lock:2
2024-10-09 14:16:46, Info CBS Ending the TiWorker main loop.
2024-10-09 14:16:46, Info CBS Starting TiWorker finalization.
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2024-10-09 14:16:46, Info CBS CBS Engine already deactivated
2024-10-09 14:16:46, Info CBS CBS Engine already deactivated
2024-10-09 14:16:46, Info CBS CBS Engine already deactivated
2024-10-09 14:16:46, Info CBS CBS Engine already deactivated
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: ComponentAnalyzerFinalize
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: PackageTrackerFinalize
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: CoreResourcesUnload
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: SessionManagerFinalize
2024-10-09 14:16:46, Info CBS Lock: Lock removed: CSIInventoryCriticalSection, level: 64, total lock:10
2024-10-09 14:16:46, Info CBS Lock: Lock removed: CCbsSessionManager, level: 11, total lock:9
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: CapabilityManagerFinalize
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: PublicObjectMonitorFinalize
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: Enter vCoreInitializeLock
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: WcpUnload
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: DrupUnload
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: CfgMgr32Unload
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: DpxUnload
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: SrUnload
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: TurboStackUnload
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: TurboContainerUnload
2024-10-09 14:16:46, Info CBS TurboContainer unload Successful
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: CbsEsdUnload
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: CbsOneSettingsFinalize
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: CbsEventUnregister
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: AppContainerUnload
2024-10-09 14:16:46, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2024-10-09 14:16:46, Info CBS Ending TiWorker finalization.
2024-10-09 14:16:46, Info CBS Ending the TrustedInstaller main loop.
2024-10-09 14:16:46, Info CBS Starting TrustedInstaller finalization.
2024-10-09 14:16:46, Info CBS Lock: Lock removed: WinlogonNotifyLock, level: 8, total lock:6
2024-10-09 14:16:46, Info CBS Ending TrustedInstaller finalization.

There is also a CBS Persist Log, but it is too big to copy and paste or attach.

Bug locker said:

Do you use VPN connection ?

Click to expand...

There is VPN software on the PC but it has not been active for quite some time, and certainly was not active during the install.

lafargeotte said:

There is VPN software on the PC but it has not been active for quite some time, and certainly was not active during the install.

Click to expand...

Create a Restore point and a system image back up.
Try the possible from here. Avoid ads of the site.

lafargeotte said:

There is also a CBS Persist Log, but it is too big to copy and paste or attach.

Click to expand...

Please copy all those log files including the .*persist ones to a .zip folder and then try and attach that .zip to your next post.

CBS Persist Log:

Torus said:

Please copy all those log files including the .*persist ones to a .zip folder and then try and attach that .zip to your next post.

Click to expand...

OK, got it now.

Thanks, could you please provide your COMPONENTS hive from the following path:


Just copy it your desktop, place it inside of a .zip and then attach to your next post. If it doesn't allow you to copy it then please reboot your computer and then try again.

Torus said:

Thanks, could you please provide your COMPONENTS hive from the following path:

Code:

%systemroot%\System32\config\COMPONENTS

Just copy it your desktop, place it inside of a .zip and then attach to your next post. If it doesn't allow you to copy it then please reboot your computer and then try again.

Code:

2024-10-09 13:57:32, Info                  CBS    Startup: Changing logon timeout to a static timeout: 10800000
2024-10-09 13:57:32, Error                 CSI    00002d51 (F) STATUS_TRANSACTION_NOT_ACTIVE #10632389# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysEnumerateValueKey(flags = 1, key = 1a2f0 ('\REGISTRY\MACHINE\COMPONENTS\CanonicalData\Deployments\88af3289426..0640d7ee8c8_b03f5f7f11d50a3a_4.0.15912.395_8a9cefc42ced3a64'), i = 0, kvic = 0, kvi = 0, disp = 0)[gle=0xd0190003]
2024-10-09 13:57:32, Error                 CSI    00002d52 (F) HRESULT_FROM_WIN32(6701) #10620377# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(...)[gle=0x80071a2d]
2024-10-09 13:57:32, Error                 CSI    00002d53 (F) HRESULT_FROM_WIN32(6701) #259674# from Windows::COM::CComponentStore_IAdvancedInstallerAwareStore::ResolvePendingTransactions(dwFlags = (DontFailIfPrimitivesPending|IndicatePrimitiveRollback), Progress = NULL, Phase = 0, Disposition = RollbackComplete' | '0x00020000)[gle=0x80071a2d]
2024-10-09 13:57:32, Error                 CBS    Startup: Failed to process advanced operation queue, startupPhase: 0. [HRESULT = 0x80071a2d - ERROR_TRANSACTION_NOT_ACTIVE]
2024-10-09 13:57:32, Info                  CBS    Current global progress. Current: 5486, Limit: 5486, ExecuteState: CbsExecuteStateResolvePending | CbsExecuteStateFlagRollback
2024-10-09 13:57:32, Info                  CBS    Previous global progress. Current: 462, Limit: 4815, ExecuteState: CbsExecuteStateStageDrivers | CbsExecuteStateFlagRollback | CbsExecuteStateFlagAdvancedInstallersFailed
2024-10-09 13:57:32, Info                  CBS    Clearing HangDetect value

Click to expand...

Hi, thanks for your help so far.
Here is components, it is too large to upload here, so I hope the link is good:
Microsoft OneDrive

Thanks, could you please open a command prompt and then enter the following command:


Please attach the Package.txt which will have been saved to your Desktop to your next post.

Note: KB5044030

Torus said:

Thanks, could you please open a command prompt and then enter the following command:

Code:

reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_1_for_KB5044030~31bf3856ad364e35~amd64~~10.0.9277.2" /s >> %userprofile%\Desktop\Package.txt

Please attach the Package.txt which will have been saved to your Desktop to your next post.

Note: KB5044030

Click to expand...

Thanks again. Here is the file.

Thanks, that CurrentState value doesn't look right at all! Let's fix it using FRST to overcome any possible permission issues:

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

Torus said:

Thanks, that CurrentState value doesn't look right at all! Let's fix it using FRST to overcome any possible permission issues:

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

Click to expand...

In the meantime I used the recovery with windows update, clicking on Reinstall now (see image), and that did the trick. It downloaded the update as well the repair install and then installed it. It took about an hour for the download and install in the background, and then 25 minutes for the reboots and back into desktop. I am now on version 2033.

However I redid the Package.txt file, and added it here, so that you can see if that is correct now.

Thanks again.

That's good to hear, basically it couldn't determine the state of that package but it looks like the repair install did what my fix script would have also done. Could you please mark this thread as solved so others will know it has a solution?

Torus said:

That's good to hear, basically it couldn't determine the state of that package but it looks like the repair install did what my fix script would have also done. Could you please mark this thread as solved so others will know it has a solution?

Click to expand...

Thank you so much for all your help.