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-10-11T22:03:23+00:00

If you are sure that your CMOS setting has not changed, and you cannot boot because of inaccessible boot device, then it is possible your boot records are corrupt or you have a bad or dying boot drive.

If your boot drive is OK, You will need to boot from a repair (or system) DVD or Flash Drive. Then go through the repair process. Try the system restore first. You may need to do a recovery (detailed much earlier in the thread)

This thread originally was to address the inaccessible boot device that was directly caused by the january 2018 windows update. It was not designed to be a general purpose inaccessible boot device thread.
Was this answer helpful?

0 comments No comments
Anonymous

2018-10-25T06:31:10+00:00

Just had the same happen to me yesterday after the 1803 upgrade. Can't boot at all not even safe mode. Have tried to remove the Roll-up fix updates from yesterday with dism.exe but not difference. Still can't boot beyond BSOD with inaccessible boot device error message.

And for some reason you can only install from boot media on top of running Windows, which seems to be a new "feature".

I also wonder why there is no way to roll back and why Windows doesn't create a restore point before such a big update.

Is my system really bricked? This will be the first time in 30 years I'll have to wipe a PC to reinstall Windows not being able to bring the current installation back to life.

Couldn't Microsfot at least tell us what drivers cause the issue and provide a way to fix the system from the command prompt back to a bootable state which you can install on top of from installation media.
Was this answer helpful?

0 comments No comments
Anonymous

2018-10-27T07:38:29+00:00

This is the point to use your windows repair with recovery last good known point
Was this answer helpful?

0 comments No comments
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more