[SOLVED] Installing KB5055526 on WS2022 21H1 Results in a BSOD Boot-loop

LukeS

New member
Joined
Apr 28, 2025
Posts
4
We have a Windows Server 2022 21H1 Build 20348.3207 that will not install KB5055526. If we manually install the update, we get error 0X8024200B and on the next system reboot - the system will BSOD with "Inaccessible Boot Device". I've had to disable Windows Update Services to keep the server online as everytime it even attempts to install said KB, it will result in a dead server BSOD Boot loop.

I've tried DISM /online /cleanup-image /RestoreHealth with no success and at this point I'm unsure how else to proceed!

Any help is greatly appreciated!
 
Hi @LukeS,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team
 
Quick update - SFC and DISM have been run as per Steps #1 & #2 and I've found that whenever dism /Image:C:\ /Cleanup-Image /RestoreHealth is run, the subsequent reboot will always result in a BSOD for Inaccessible boot device , it does not appear to be generating a dump file. I have however attached the dism.log file.

Currently, WUA Services are disabled on the prod server and I've duplicated it and performing testing in that.
 

Attachments

Ok Final update as I'm lost.

After restoring my test VM again, I then ran Component Scanner and it returned no corruptions found. Lastly, I've run SFCFix (Finished with No Corruptions Were Detected) and it would seem it too must use DISM as after it completed and I rebooted, another BSOD
🫠


Anyway, CBS Logs are below aswell. Unsure how to proceed - It's obvious now that this is not a specific issue with Windows Update but a more serious underlying issue.
 

Attachments

Final update - Repair install of WS2022 has resolved the issue. I'd love to know the root cause but a W is a W.
 
Hi and welcome to Sysnative,

It seems to be a drriver issue which was root cause and possibly the cause of the BSODs as well. But glad the issue has been resolved with a repair install.

Rich (BB code):
2025-04-29 13:35:28, Info                  CBS    DriverUpdateInstallUpdates failed [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2025-04-29 13:35:28, Info                  CBS    Doqe: Failed installing driver updates [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2025-04-29 13:35:28, Info                  CBS    Perf: Doqe: Install ended.
2025-04-29 13:35:28, Info                  CBS    Failed installing non-critical driver updates [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2025-04-29 13:35:28, Error                 CBS    Doqe: Failed processing queue [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2025-04-29 13:35:28, Error                 CBS    Doqe: Failed undoing interactive driver operations. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2025-04-29 13:35:28, Info                  CBS    Setting ExecuteState key to: ExecuteStateNone
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top