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-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
  2. 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
  3. Anonymous
    2018-02-01T21:36:46+00:00

    Microsoft won't pay. 

    The End User License Agreement (EULA) that you agree to before you can use windows, severely limits their liability.

    "DISCLAIMER OF WARRANTY. THE SOFTWARE IS LICENSED “AS IS.” YOU BEAR THE RISK OF USING IT. MICROSOFT GIVES NO EXPRESS WARRANTIES, GUARANTEES, OR CONDITIONS. TO THE EXTENT PERMITTED UNDER APPLICABLE LAWS, MICROSOFT EXCLUDES ALL IMPLIED WARRANTIES, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT."

    Their maximum liability is to a) repair or replace the software  b) return the software for refund (additional conditions apply).

    These are your only remedies.

    I'm not a lawyer, but my interpretation of the EULA is as follows:

    They don't guarantee that the software is suitable for anything, or even fit to be sold.  If any part of Windows infringes on someone else's rights, they will not indemnify you.

    Their maximum liability is to either repair the problem (which they did) or refund of the amount you paid Microsoft.  You MIGHT be entitled to a refund. (But only If you bought it from Microsoft or it is a Microsoft Branded device (Like a Surface). If not you are SOL).

    There is a whole bunch of other stuff that limits what you can and cannot do with the software as well.

    If you don't like the license, you shouldn't use windows. (although the terms are pretty common in most software licenses)

    wiz

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-02T12:32:06+00:00

    JoelTP,

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

    Yes, it looks the very update is causing the screeching halt.

    My hardware config is: mobo MSI Z270-A PRO with i7-7700k with maxed out RAM and clock speed.

    Was this answer helpful?

    0 comments