M
MycGyver
As many people are experiencing frustration with this error I decided to dig a bit deeper into my own problem, hoping that what I find might help others.
The frustration with problem solving online is that we are often asked to try multiple standard solutions without understanding the actual root cause of the problem first. These suggestions are meant to fix the majority of problems.
The three standard suggestions for this problem:
I do not believe any of these apply to me.
Microsoft products have always been pretty good at having the ability to trace into issues through log files so I thought it was time to dig a bit to see what I could find, so away I went down the rabbit hole....
STEP 1
Examining the C:\Windows\logs\WindowsUpdate\WindowsUpdate.log
Here I find the error code:
2019-03-20 21:34:25.2682241 5404 6440 Handler Post-reboot status for session 30728068_2341961783: 0x800f0922.
This only indicated the failure that was logged and found after rollback/reboot, so I had to dig backwards further.
Looking further in the file I noticed the install steps that seem to be responsible for each installer package:
2019-03-20 21:27:09.3341633 2312 6024 Handler CBS called Progress with state=7, ticks=752, total=1000
2019-03-20 21:27:10.6576048 2312 6024 Handler CBS called Progress with state=7, ticks=752, total=1000
2019-03-20 21:27:10.7071653 2312 6024 Handler CBS called Progress with state=7, ticks=1000, total=1000
2019-03-20 21:27:10.7078483 2312 6024 Handler CBS called Terminate
2019-03-20 21:27:19.4807585 2312 1668 Handler Requesting post-reboot reporting for package Package_for_RollupFix~31bf3856ad364e35~amd64~~17134.590.1.7.
2019-03-20 21:27:19.4812427 3068 10456 Misc Removed update 11904777-F6C7-4327-A0E3-D4E87C8B1FB4 from sticky list for service 5C4E689A-8F00-41BE-A45C-A9990E61BDB8
2019-03-20 21:27:19.4813226 3068 10456 Misc Removed update E58A0618-89B2-42D2-9999-2CC56FC37958 from sticky list for service 5C4E689A-8F00-41BE-A45C-A9990E61BDB8
2019-03-20 21:27:19.4813622 2312 1668 Handler Completed install of CBS update with type=3, requiresReboot=1, installerError=0, hr=0x0
2019-03-20 21:27:20.6825193 2312 1668 Handler * END * CBS Install
Since this indicated no errors, I wondered about the problem with the last installer package that was executed likely causing the rollback.
STEP 2
This led me to look into the C:\Windows\Logs\CBS\CBS.log file.
In here I found the error code:
2019-03-20 21:31:13, Info CSI 0000061f The queue has completed running, and AI failures have occured.
2019-03-20 21:31:13, Info CSI 00000620 ==Error Summary Start==
2019-03-20 21:31:13, Error CSI 00000621 (F) Installer: Boot File Servicing (BFSVC) Installer Binary Name: bfsvc.dll ErrorCode: 8031004a Phase: 31 Mode: Delta Component: NONE[gle=0x80004005]
2019-03-20 21:31:13, Info CSI 00000622 ==Error Summary End==
2019-03-20 21:31:13, Info CSI 00000623 Failed unloading hive file: \??\C:\Users\Default\NTUSER.DAT, key: \Registry\USER\Template, with flags: 1, NTSTATUS: 0
2019-03-20 21:31:13, Info CSI 00000624 Failed unloading hive file: \??\C:\Users\.NET v4.5 Classic\NTUSER.DAT, key: \Registry\User\S-1-5-82-3876422241-1344743610-1729199087-774402673-2621913236, with flags: 1, NTSTATUS: 0
2019-03-20 21:31:13, Info CSI 00000625 Failed unloading hive file: \??\C:\Users\DefaultAppPool\NTUSER.DAT, key: \Registry\User\S-1-5-82-3006700770-424185619-1745488364-794895919-4004696415, with flags: 1, NTSTATUS: 0
2019-03-20 21:31:13, Info CSI 00000626 Failed unloading hive file: \??\C:\Users\.NET v4.5\NTUSER.DAT, key: \Registry\User\S-1-5-82-271721585-897601226-2024613209-625570482-296978595, with flags: 1, NTSTATUS: 0
2019-03-20 21:31:13, Info CSI 00000627 Failed unloading hive file: \??\C:\Users\anneb\NTUSER.DAT, key: \Registry\User\S-1-5-21-2287868482-2659178975-332919780-1004, with flags: 1, NTSTATUS: 0
2019-03-20 21:31:13, Info CSI 00000628 Failed unloading hive file: \??\C:\Users\mmyc\NTUSER.DAT, key: \Registry\User\S-1-5-21-2287868482-2659178975-332919780-1001, with flags: 1, NTSTATUS: 0
2019-03-20 21:31:13, Error CBS Startup: Failed to process advanced operation queue, startupPhase: 0. A rollback transaction will be created. [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]
2019-03-20 21:31:13, Info CBS Setting ExecuteState key to: CbsExecuteStateInitiateRollback | CbsExecuteStateFlagAdvancedInstallersFailed
2019-03-20 21:31:13, Info CBS SetProgressMessage: progressMessageStage: -1, ExecuteState: CbsExecuteStateInitiateRollback | CbsExecuteStateFlagAdvancedInstallersFailed, SubStage: 0
2019-03-20 21:31:13, Info CBS Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Rollback.
2019-03-20 21:31:13, Info CBS Setting original failure status: 0x800f0922, last forward execute state: CbsExecuteStateResolvePending
2019-03-20 21:31:13, Info CBS Attempting to remove poqexec from SetupExecute
2019-03-20 21:31:13, Info CBS Removed poqexec from SetupExecute.
2019-03-20 21:31:13, Info CBS Configured poqexec to not pend to SetupExecute.
2019-03-20 21:31:14, Info CBS Startup: Changing logon timeout to a static timeout: 10800000
2019-03-20 21:31:15, Error CSI 00000629 (F) Installer: Boot File Servicing (BFSVC) Installer Binary Name: bfsvc.dll ErrorCode: 8031004a Phase: 31 Mode: Delta Component: NONE[gle=0x80004005]
2019-03-20 21:31:15, Info CSI 0000062a Rolling back transactions...
The problem initiating the rollback appears to be related to "Boot File Servicing (BFSVC) Installer"
STEP 3
I found various articles referring to this type of issue which required fixing the system partitions such as:
[solved] Windows Update Install Loop: Error 0x800F0922 for KB3192440
These steps failed on the bootrec /fixboot step with an access denied error.
STEP 4
I found various articles referring to fixing the access denied problem sub as:
Windows 10 bootrec /fixboot access is denied
Unfortunately I could find nothing to help me determine the root cause of this error.
These steps involve resetting the system partition.
STEP 5
Most of the articles I found referred to formatting FAT32. I was confused why my partition layouts seemed different and why the format was NTFS.
Understanding the steps for this was a bit confusing due to the different types of boot partition styles UEFI/GPT vs BIOS/MBR.
Hard Drives and Partitions
After some research I understand that I have a BIOS/MBR computer built in 2010, just around the time of evolution to UEFI/GPT.
(Dell Studio XPS 9100)
This research also revealed that I did not appear to have a standard partition layout.
STEP 6
Now i need to backup and try out some adjustments. Stay tuned...
Continue reading...
The frustration with problem solving online is that we are often asked to try multiple standard solutions without understanding the actual root cause of the problem first. These suggestions are meant to fix the majority of problems.
The three standard suggestions for this problem:
- Low System Reserved partition space
- Fail to connect to Microsoft Windows Update server
- The .Net framework installation portion of Windows 10 upgrade fails.
I do not believe any of these apply to me.
Microsoft products have always been pretty good at having the ability to trace into issues through log files so I thought it was time to dig a bit to see what I could find, so away I went down the rabbit hole....
STEP 1
Examining the C:\Windows\logs\WindowsUpdate\WindowsUpdate.log
Here I find the error code:
2019-03-20 21:34:25.2682241 5404 6440 Handler Post-reboot status for session 30728068_2341961783: 0x800f0922.
This only indicated the failure that was logged and found after rollback/reboot, so I had to dig backwards further.
Looking further in the file I noticed the install steps that seem to be responsible for each installer package:
2019-03-20 21:27:09.3341633 2312 6024 Handler CBS called Progress with state=7, ticks=752, total=1000
2019-03-20 21:27:10.6576048 2312 6024 Handler CBS called Progress with state=7, ticks=752, total=1000
2019-03-20 21:27:10.7071653 2312 6024 Handler CBS called Progress with state=7, ticks=1000, total=1000
2019-03-20 21:27:10.7078483 2312 6024 Handler CBS called Terminate
2019-03-20 21:27:19.4807585 2312 1668 Handler Requesting post-reboot reporting for package Package_for_RollupFix~31bf3856ad364e35~amd64~~17134.590.1.7.
2019-03-20 21:27:19.4812427 3068 10456 Misc Removed update 11904777-F6C7-4327-A0E3-D4E87C8B1FB4 from sticky list for service 5C4E689A-8F00-41BE-A45C-A9990E61BDB8
2019-03-20 21:27:19.4813226 3068 10456 Misc Removed update E58A0618-89B2-42D2-9999-2CC56FC37958 from sticky list for service 5C4E689A-8F00-41BE-A45C-A9990E61BDB8
2019-03-20 21:27:19.4813622 2312 1668 Handler Completed install of CBS update with type=3, requiresReboot=1, installerError=0, hr=0x0
2019-03-20 21:27:20.6825193 2312 1668 Handler * END * CBS Install
Since this indicated no errors, I wondered about the problem with the last installer package that was executed likely causing the rollback.
STEP 2
This led me to look into the C:\Windows\Logs\CBS\CBS.log file.
In here I found the error code:
2019-03-20 21:31:13, Info CSI 0000061f The queue has completed running, and AI failures have occured.
2019-03-20 21:31:13, Info CSI 00000620 ==Error Summary Start==
2019-03-20 21:31:13, Error CSI 00000621 (F) Installer: Boot File Servicing (BFSVC) Installer Binary Name: bfsvc.dll ErrorCode: 8031004a Phase: 31 Mode: Delta Component: NONE[gle=0x80004005]
2019-03-20 21:31:13, Info CSI 00000622 ==Error Summary End==
2019-03-20 21:31:13, Info CSI 00000623 Failed unloading hive file: \??\C:\Users\Default\NTUSER.DAT, key: \Registry\USER\Template, with flags: 1, NTSTATUS: 0
2019-03-20 21:31:13, Info CSI 00000624 Failed unloading hive file: \??\C:\Users\.NET v4.5 Classic\NTUSER.DAT, key: \Registry\User\S-1-5-82-3876422241-1344743610-1729199087-774402673-2621913236, with flags: 1, NTSTATUS: 0
2019-03-20 21:31:13, Info CSI 00000625 Failed unloading hive file: \??\C:\Users\DefaultAppPool\NTUSER.DAT, key: \Registry\User\S-1-5-82-3006700770-424185619-1745488364-794895919-4004696415, with flags: 1, NTSTATUS: 0
2019-03-20 21:31:13, Info CSI 00000626 Failed unloading hive file: \??\C:\Users\.NET v4.5\NTUSER.DAT, key: \Registry\User\S-1-5-82-271721585-897601226-2024613209-625570482-296978595, with flags: 1, NTSTATUS: 0
2019-03-20 21:31:13, Info CSI 00000627 Failed unloading hive file: \??\C:\Users\anneb\NTUSER.DAT, key: \Registry\User\S-1-5-21-2287868482-2659178975-332919780-1004, with flags: 1, NTSTATUS: 0
2019-03-20 21:31:13, Info CSI 00000628 Failed unloading hive file: \??\C:\Users\mmyc\NTUSER.DAT, key: \Registry\User\S-1-5-21-2287868482-2659178975-332919780-1001, with flags: 1, NTSTATUS: 0
2019-03-20 21:31:13, Error CBS Startup: Failed to process advanced operation queue, startupPhase: 0. A rollback transaction will be created. [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]
2019-03-20 21:31:13, Info CBS Setting ExecuteState key to: CbsExecuteStateInitiateRollback | CbsExecuteStateFlagAdvancedInstallersFailed
2019-03-20 21:31:13, Info CBS SetProgressMessage: progressMessageStage: -1, ExecuteState: CbsExecuteStateInitiateRollback | CbsExecuteStateFlagAdvancedInstallersFailed, SubStage: 0
2019-03-20 21:31:13, Info CBS Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Rollback.
2019-03-20 21:31:13, Info CBS Setting original failure status: 0x800f0922, last forward execute state: CbsExecuteStateResolvePending
2019-03-20 21:31:13, Info CBS Attempting to remove poqexec from SetupExecute
2019-03-20 21:31:13, Info CBS Removed poqexec from SetupExecute.
2019-03-20 21:31:13, Info CBS Configured poqexec to not pend to SetupExecute.
2019-03-20 21:31:14, Info CBS Startup: Changing logon timeout to a static timeout: 10800000
2019-03-20 21:31:15, Error CSI 00000629 (F) Installer: Boot File Servicing (BFSVC) Installer Binary Name: bfsvc.dll ErrorCode: 8031004a Phase: 31 Mode: Delta Component: NONE[gle=0x80004005]
2019-03-20 21:31:15, Info CSI 0000062a Rolling back transactions...
The problem initiating the rollback appears to be related to "Boot File Servicing (BFSVC) Installer"
STEP 3
I found various articles referring to this type of issue which required fixing the system partitions such as:
[solved] Windows Update Install Loop: Error 0x800F0922 for KB3192440
These steps failed on the bootrec /fixboot step with an access denied error.
STEP 4
I found various articles referring to fixing the access denied problem sub as:
Windows 10 bootrec /fixboot access is denied
Unfortunately I could find nothing to help me determine the root cause of this error.
These steps involve resetting the system partition.
STEP 5
Most of the articles I found referred to formatting FAT32. I was confused why my partition layouts seemed different and why the format was NTFS.
Understanding the steps for this was a bit confusing due to the different types of boot partition styles UEFI/GPT vs BIOS/MBR.
Hard Drives and Partitions
After some research I understand that I have a BIOS/MBR computer built in 2010, just around the time of evolution to UEFI/GPT.
(Dell Studio XPS 9100)
This research also revealed that I did not appear to have a standard partition layout.
STEP 6
Now i need to backup and try out some adjustments. Stay tuned...
Continue reading...