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-01-22T15:54:29+00:00

    I would like to stress that our problems are with Intel processors.

    We had 3 more machines over the weekend go into the BSOD loop.

    All due to restarts.

    To "fix" the problem:

    1. We try the restore points in reverse date order until one works.
    2. We've told users not to restart their computers.

    Does anyone know:

    1. which update exactly is causing the problem?
    2. the steps to prevent it from re-installing?
    3. if there has been any acknowledgement of the W10/Intel processor problem by an AV supplier, Intel or Microsoft?

    Ideally the answers to the above questions should be a Microsoft tech bulletin.

    It's obviously difficult to wade thru all of the different suggestions in this thread.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-22T15:40:15+00:00

    Almost all the computers that I have seen with the issue can be recovered to a working state by going to a restore point. Unfortunately the issue will happen again. I have several machines that seem to need a restore every few days. Others last longer. I new thing I am seeing is that the USB Ports will randomly stop working. USB xHCI Compliant Host Controller with Code 28. Can't load the driver. Dell desktop computer, Intel based. Anyone else seeing this USB issue. This is the third machine to have this issue.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-22T12:20:26+00:00

    This is even more removed than with using the OS installation disk in Repair Mode which under these conditions COULD, COULD, be doing allot of damage.

    I was specifically wondering why this was the case.  I guess I should've more explicitly stated that I was running WinRE off a bootable flash drive.

    Perhaps adding to the confusion, I should otherwise add that I have two computers/laptops in the house which are exactly the same (hardware, history of software, and everything) with (almost) all the same software installed presently as well, and only one of them was affected. The only difference is, one of them is used every day (and therefore more frequently updated) - the one which is suffering from the issue - and the other closer to only like once a month.  The only other difference is that the one with the issue has ESET running on it as its antivirus.  I doubt that has anything to do with it though...

    In any case, if Microsoft doesn't acknowledge the issue (and furthermore release or promise a patch to be able to install from the recovery environment) tomorrow (from what I understand they haven't yet), I will just restore to one of the old backups I mentioned I did for this computer.  Screw it.  On the user end, I think everything that's possible to do has been exhausted and I learned everything I possibly can from this.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-22T00:57:58+00:00

    No I didn’t walk through all those settings and all the notes that you had in your one post.

    I haven’t checked the thread since Friday and just was fed up so I decided to do a clean install. I appreciate the help though!

     Yes that’s the update that I installed. So far so good 

    I get it that your pissed...... I understand that.

    To try to defer you get more pissed or pissed in the future, Please don't stick your finger in your eye, instead go read this above:

    In reply to Ppilihp's post on January 21, 2018

    If you already doing everything GREAT, if not everything, some day you will wish you did. I did once again last night.....

    I do it after every Patch session, Update and/or Upgrade. I would call it an old Pro Tip but it isn't, it should be standard for everybody and any one.

    Best Regards,

    Crysta

    Was this answer helpful?

    0 comments