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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-01-24T05:59:29+00:00

    OMG Showster, OMG,

    If I was arrogant, as you paint me, OMG, I COULD NOT live with myself....

    As I said to you way back then, Showster, "If you have the answers, tell the people! They want to know". I didn't come here thinking, I had the answers. I came her to offer my experience of untangling Microsoft's messes in the Past. It is called "The School of Hard knocks", did you ever attend Showster? OH! I believe you did, if I am not mistaken The solution that has your name on it, eventually FAILED FOR YOU TOO, just like many here on this thread. I could have that wrong but that is how I remember it.

    Just for the record, Showster, I believe you said " Good information granted" was learned through allot of VERY PAINFUL TIMES, similar to what is going on here. I definitely don't know everything and have never claimed that I did. I wonder Showster, what you are really upset about?

    I am not going to start calling you names, because in the end, I think our views on things Microsoft and Windows are probably very close to the same, as you have eluded to.

    Believe me I am no fan of Microsoft, but I have learned one thing, waiting for them to fix their OS, you will grow old and moldy. Eventually you might get a Bandaid, However one starts to realize, that is mostly what Windows is, a huge amount of bandaids and plaster casts. Unfortunately Windows is still the only viable game/OS for most of us. I wish there was a true alternative but for most there isn't. Some are getting more close for some more but it is still a subset.......

    It has always been Bobby's post, Showster, and Bobby failed terribly too, with your solution. that is the SAD epitaph....

    Best Regards,

    Crysta

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-24T06:12:52+00:00

    I speak upon your first reply to me.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-24T07:58:43+00:00

    But don't forget we love ya for it ;)

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-24T08:43:08+00:00

    Ok, I'm done with this.  I simply restored from an old backup image I had of the disk.

    DISM is effectively broken as half its functions fail.  I called Microsoft earlier, as I mentioned I would, and that was a terrible experience.  45 min waiting only to forcefully go through basic troubleshooting steps after which I was told to do a clean install and that a level 2 technician would tell me the same thing (in a nice foreign tone).  As I was effectively asking to be transferred anyway, either the call dropped or I was hung up on, but either way I didn't get a call back (even though my number was taken down in the beginning).  Not like it matters I guess; they wouldn't know s*** anyway.

    Anyone getting the 0x8000ffff error after removing the update with DISM, getting in once, and then getting the BSOD again, you're pretty much screwed.

    Was this answer helpful?

    0 comments