Inaccessible Boot Device error in Windows 10

Anonymous

I manage multiple computers running Windows 10 Pro 64-bit with the latest Current Branch and recently had multiple computers randomly startup with this BSOD: Inaccessible Boot Device.

I have tried everything:

https://www.windowscentral.com/how-fix-update-causing-inaccessible-boot-device-error-windows-10

Which recommends deleting registry keys and install packages, though no pending installs could be found

SFC /SCANNOW - No corruption found

CHKDSK /R - Some minor issues corrected

BOOTREC - Scan OS shows 0 windows installations

FIXBOOT - Successful, but this tool finally made the entire process fail without being able to get to the recovery environment, just boots to the legacy screen and shows options for safe mode, but those fail too.

I am at my wits end, because I find thousands of websites and desperate users and admins, but the only fix that works is to clean install. I can't clean install the whole company. This is insane, there has to be a better known cause / fix out there...

*Modified title for accuracy*

*Original title: Inaccessible Boot Device error - cause? fix?*

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

WIN 10 BSOD FIX - Inaccessible Boot Device - THIS WORKS! I Just Repaired 2 computers that went down at the same time last night on 1/16/18

Good Afternoon Bobby,

Here is the fix I came across from another kind IT tech, please see below. Credits go to them, I'm just forwarding so everyone can finally get their computers back up and running.

Boot Windows 10

Go to Repair

Go to Tools/Options to get a command prompt.

Confirm the drive letter for the Windows image. Usually D: –> dir d:

Run the following to view the installed packages which will also show a date of install.

Dism /Image:D:\ /Get-Packages

Find the package(s) that were just installed by date. Run the following command on the last installed package:

example: dism.exe /image:d:\ /remove-package /packagename:Package_for_KB4014329~31bf3856ad364e35~amd64~~10.0.1.0

Reboot.

The patch that caused my issue was from 1/6/18 or 1/10/18 Remove the latest windows update entry with Rollup Fix in it's name. Once complete, close command prompt, turn off computer. Power back up. You should be back into WIN10.

If you still receive BSOD, rinse and repeat with the next latest update, try it again. You'll eventually boot right back into WIN10.

I hope this helps.

Have a great day.

Showster

0 comments

506 additional answers

Anonymous

2018-02-24T02:49:46+00:00

It has not been fixed, merely the KB is documenting the known issue and resolutions steps. 1703 is NOT impacted. Only 1709, so you are saying the system is at the step of upgrading to 1709?
Was this answer helpful?

0 comments No comments
Anonymous

2018-02-24T02:29:58+00:00

Susan-

You mentioned that KB4074588 was updated TODAY and now includes the text you posted that refers to KBs for the inaccessible boot device and USB issues. Do you know if the update file itself was modified/fixed or just the article describing it and possible issues?

Any advice when a system is sitting at 1703 ver .192 and has ALREADY DOWNLOADED KB4074588 (ver .248) and is just waiting to restart to finish installing the update? I would like to prevent the completion of the update with its possible death trap until Microsoft gives us a positive fix.

Thanks,
Was this answer helpful?

0 comments No comments
Anonymous

2018-02-24T02:16:40+00:00

1703 doesn't have the problem, only 1709.
Was this answer helpful?

0 comments No comments

Anonymous

After installing this update, some USB devices and onboard devices, such as a built-in laptop camera, keyboard or mouse, may stop working. This may occur when the windows update servicing stack incorrectly skips installing the newer version of some critical<br> drivers in the cumulative update and uninstalls the currently active drivers during maintenance.	Microsoft is working on a resolution and will provide an update<br> in an upcoming release.<br><br>Workaround steps are available in<br>KB4091240.
After installing this update, some devices may fail to boot with INACCESSIBLE_BOOT_DEVICE.<br><br><br>This issue occurs when the windows update servicing stack incorrectly skips installing the newer version of some critical drivers in the cumulative update and uninstalls the currently active drivers during maintenance.	Microsoft is working on a resolution and will provide an update in an upcoming release.<br><br>Workaround steps are available in KB4075150.

0 comments