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-01-20T06:27:30+00:00

Thank You, I hope they get through several/multiple Reboots and Shutdowns.

Then even longer term. It is the extend Multiple/Time that gets some.

In other words it is early times, but I sure hope the successes expand.....

Best Regards,

Crysta

PS. I have seen TLDR; many many times over the last months but have never heard an explanation for it. I assume it originated in the Valley but I don't live anywhere near San Francisco. Could you break my ignorance?
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-20T04:42:43+00:00
An update to my experiences with this issue:

I had a total of 4 units with the BSOD.
1. The first one brought in I attempted most of the solutions in this thread with no luck, except for the one time boot I was able to do directly after removing the installed package with dism. Ultimately I completed a fresh Windows installation and was able to complete all available updates with no further issues encountered.
2. This time the client told me a fresh Windows install had to be a last resort and was willing to leave the unit with me longer if that would help avoid reinstall. I decided here to restore the unit back to a point near the end of December and disable updates until a later date. This seemed like a good solution until the client brought the unit back to me a day later with the same issue (not sure if they managed to re-enable updates or what).
3. Units three and four came in around the same time. I quickly got into Windows on both by removing the package with dism. I tried all the updated solutions this thread offered and few other things with no luck. What I hadn't tried was letting Windows updates install all available updates immediately after being able to boot once after removing package. This actually worked on the fourth unit brought in. I went back and ran system restore on units 2 and 3 (as i had since rebooted and got BSOD) and removed the package once again. After booting into windows on these, I completed all available updates and my next restarts went smoothly.
TLDR; Fixed this BSOD on three units by removing the package through dism, and immediately after being able to boot once, completed all available updates before restarting.
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-20T01:29:37+00:00

Thanks, it fixed my problems, thank GOD!

Let us know if it stays fixed..... Please....

Other are finding that it does not?????

Best Regards,

Crysta

Crysta,

The security updates dated 10/Jan/2018 caused the BSOD, after I removed those two updates, I was able to re-enter the system successfully without the need of re-installation of the whole system, thanks to Showster18's post.

As long as I keep those two updates from re-installing again, my Win10 will be fine, I think.

Charles
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-20T01:02:35+00:00

Thanks, it fixed my problems, thank GOD!

Let us know if it stays fixed..... Please....

Other are finding that it does not?????

Best Regards,

Crysta
Was this answer helpful?

0 comments No comments