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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2018-02-23T23:35:01+00:00

    I can't be sure but it looks like you have not booted from external media.  You have booted into the recovery tools on the hard drive.

    It is necessary to boot from external media of the same version and bit-type.

    Using the get packages command note the latest rollup package. 

    You should try removing only the latest rollup packages first.  

    Remove that package then try again.

    I assume it is a 64 bit system based on the commands you are using.

    See the next post for another idea.

    try that.

    Wiz

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-02-23T19:46:41+00:00

    Or this error....

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-02-23T18:44:47+00:00

    Thanks to Susan and all the others that made suggestions posted to this thread. After unsuccessfully trying the numerous DISM command variations, RegEdit fixes and other attempts mentioned here since Feb 13th, I finally gave in. I wiped my wife's old 2011 HP computer with AMD processor and went to a clean install from a current Win 10 Home image which failed.  

    During the last two days, I have spent seven hours with three levels of Microsoft Support trying to get the machine working. I watched as they created multiple installs of Win 10, Win 8.1 and Win 7 all of which failed to boot after installation. MS felt we must have a hardware problem.

    We then loaded from the original Windows 7 Home Premium media and the machine came to life. We have been able to install all Windows 7 updates. We were then about to upgrade to Win 10, version 1607 (Creators Update), when the technician checked compatibility on the HP website. Paraphrasing the statement on the HP website, "HP has not tested version 1607 for compatibility with any pre-2013 product, proceed at your own risk". 

    A surprise statement then came from the MS Tech, his recommendation, to avoid incompatibility issues with Win 10 and future updates, stay with Windows 7.  I am OK with staying on Win 7, it was never my intent to upgrade this machine to Win 10, an errant click to a message scheduled the upgrade last year.

    The aggravation here is that all of this is the result of the Microsoft policy forcing the Windows 10 Update model for Home users, that pushes untested items. If this policy was such a good idea, auto updates wouldn't be optional for Win 10 Professional and Enterprise users.

    Because the true problem was loaded as apart of an update months ago, I could not uninstall current updates, and my system backups did not go back that far. I guess I should be happy that I have current data backups, so it is the "simple" task of just re-installing all the printers, application software and configuring.

    Does anyone know the address where I send the bill for my time to fix this? :)

    Thanks, 

    Jim

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-23T18:27:26+00:00

    It gives the same error message.

    Was this answer helpful?

    0 comments