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-02-01T21:28:46+00:00

    Hello,

    We have been hit with this INNACCESSIBLE_BOOT_DEVICE too on a Windows 10 Home machine used for computations.

    For long time we had prevented the unattended installations by setting all network connections as metered and were not less then 2-3 weeks behind with the updates. However, last weeks some Windows update "nag"  was comming up stating that an update was ready  to be installed regarding Intel or Intel drivers (I remember only this much). It was intrusive, as never before.

    After reboot the stop occured  INNACCESSIBLE_BOOT_DEVICE. No new installed packages in the store so I had nothing to remove with the dism command you describe here.

    As I had a mirror copy of the whole disk subsystem only one week old, I am sure the issue is caused by the update. Windows boots from the old snapshot just fine.

    Now the Windows Update service is "Disabled" and I will be making a snapshot each time before enabling Windows Update service.

    One day of work and 24 hs. of calculations is lost. Who will pay for this, Microsoft?

    See my post on page 2. Sounds like the same thing.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-02-01T20:28:23+00:00

    Hello,

    We have been hit with this INNACCESSIBLE_BOOT_DEVICE too on a Windows 10 Home machine used for computations.

    For long time we had prevented the unattended installations by setting all network connections as metered and were not less then 2-3 weeks behind with the updates. However, last weeks some Windows update "nag"  was comming up stating that an update was ready  to be installed regarding Intel or Intel drivers (I remember only this much). It was intrusive, as never before.

    After reboot the stop occured  INNACCESSIBLE_BOOT_DEVICE. No new installed packages in the store so I had nothing to remove with the dism command you describe here.

    As I had a mirror copy of the whole disk subsystem only one week old, I am sure the issue is caused by the update. Windows boots from the old snapshot just fine.

    Now the Windows Update service is "Disabled" and I will be making a snapshot each time before enabling Windows Update service.

    One day of work and 24 hs. of calculations is lost. Who will pay for this, Microsoft?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-02-01T19:52:06+00:00

    Thank you for posting this.  This worked for me as well.  I spent a great deal of time trying to rebuild MBR and other regular no boot fixes to no avail.  This worked for me, and it was the same KB that you had.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-01T18:39:54+00:00

    That HP desktop will not allow anything to be loaded in any way. The BAD "Meltdown Spectre Update" by MS left the HD in a state that can't even be formatted. I'm lucky that I have a couple of new comps still in the sealed boxes to replace it with.

    The only reason that I've spent so much time trying to fix MS's mess on that HP is that it runs a ham radio repeater that makes long range wifi available & also runs the DVDRW control box with 16 security cameras on the 45 acres that I live on. It will take a lot of time to set up another comp to take its place. Over the last year I've been hit by lightning, hurricane Irma & several other really bad storms / floods ($50K+ in damages). So this is just another nightmare to add to the list.

    People at MS have tried to blame it on HP & AMD when everyone knows that Microsoft just released an update that was not tested well. I feel very sorry for those that lost their only comps to this sad mistake & hope that Microsoft will take responsibility & help those people out somehow. I know that there will be a class action lawsuit over this mess in the end & MS will keep it delayed in the courts until this is just a distant memory.

    I wish everyone the best & hope that all can get back to where they were before this MS mistake.

    Was this answer helpful?

    0 comments