Inaccessible Boot Device error in Windows 10

Anonymous
2018-01-09T16:46:16+00:00

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?*

Windows for home | Windows 10 | Performance and system failures

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
2018-01-17T17:16:49+00:00

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

Was this answer helpful?

30+ people found this answer helpful.
0 comments

506 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-03-01T14:45:31+00:00

    Thanks for the reply. I woke up this morning to see updates had automatically applied overnight and broke it again. I'm in  the process of fixing it for a 3rd time now. I'll try running the repair install  if I can get it to boot again...

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-03-01T05:28:30+00:00

    if you do a repair install once booted, you wont have that problem.  After your first successful boot, the repair install fixes all the problems.  Since it resets everything and removes all the pending actions you will be fine. you needent worry about updates either.  After the repair install, all the updates will install without problem.

    wiz

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-03-01T04:33:54+00:00

    I had both the broken packages on my computer:

    Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9

    and

    Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.248.1.17

    however I couldn't see either of them. I had to revert back to my oldest recovery image, which luckily allowed me to see "248.1.17". I removed it using the dism command, rebooted and received the same inaccessible boot device error. I then went back in a 2nd time and now I could see "192.1.9" and remove it.

    Now the computer would boot up to my desktop, so I used it for my work all day. At the end of the day I rebooted only to find out wonderful Microsoft update, which you can't shut off in Windows 10, installed all the updates and broke my computer yet again.

    Another 2 hours wasted this evening fixing it again!!!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-28T04:17:21+00:00

    I just edited it, let me know if that's good enough.

    Susan, It's fine.  You might mention there are more details deeper in tbe blog.

    I would add that in your edits, you are using the phrase "system refresh" which may be may be confusing.  The recovery environment calls this a "system reset".

    wiz

    Was this answer helpful?

    0 comments