This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 2%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Hi,
I have a physical 2016 server that I installed updated KB5029242 on.
I've not found any reports of known issues, but since doing so, my machine now bluescreens on every boot with error "INACCESSIBLE BOOT DEVICE".
It can get into the recovery menu, but then no fixed disks are found. I have to use drvload to load in the HP Smart Array controller driver, at which point the disks appear.
Listing the disks and volumes, everything looks fine, but running startup repair yields no success:
Root cause found:
Unspecified changes to system configuration might have caused the problem
Repair action: Result: Failed. Error code - 0x32
Time taken = 140ms
Repair action: System files integrity check and repair
Result: Failed. Error code = 0x490
Time taken = 473874ms
Running a manual chkdsk, sfc /scannow, and dism image tools everything looks ok.
BCDEDIT looks ok too, with Windows Boot Manager being on E: and one entry to Windows Boot Loader on C: referencing winload, Windows Server 2016 and OS root of \Windows
I also used DISM to install the HP driver into the Windows image on C:, just to be sure there was no driver issue.
I'm not sure what else to try here? Can anyone offer any suggestions on what else the cause could be, or my best course of action?
Should I run some DISM repair-image commands, or try and "In place upgrade" from 2016 to 2016?
Appreciate any advice anyone can offer
Thanks
James
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Might work through these beginning with Startup Repair
--please don't forget to close up the thread here by marking answer if the reply is helpful--
Thanks.
I had already run startup repair with the log results mentioned in OP.
I looked at all the other steps in the article, but some of them could not be applied, such as the renaming of C:\boot\bcd, as it doesn't exist.
I think the issue is at kernel phase, as an example it mentions which is what I'm getting, is INACCESSIBLE_BOOT_DEVICE.
I ran through that entire article too, with not fix.
Thanks
James
We have been unable to identify the underlying cause of this issue, so have decided to just reimage and reconfigure the server.
I had two servers do the same thing that I've spent several hours trying to get back to an operational state. I can load the HPE array drivers and see and access the drives using recovery media but once rebooted it does the same. Afraid to reboot any other servers now.