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-28T01:03:32+00:00

    There are no ways to dism off an update if it's pending install.  Sorry, Ira.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-02-28T00:33:21+00:00

    Yes 64bit    I have tried after letting it through repair run on the hard drive then external boot. 

    The result is the same error

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-02-28T00:24:52+00:00

    I had the problem and removed all 2018 updates using dism in January.

    After that updates in February worked fine - no problems.

    Then today there were a couple of updates - the "inaccessible_boot_device" error occurred again.

    So back to dism to remove all updates on Feb/28 - problem fixed.

    Hmmmm not happy Microsoft

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-27T11:07:02+00:00

    Hello,

    I had the same problem with 3 machines at work, at first I couldn't find out what was wrong and had to reinstall windows with a BRAND NEW iso downloaded from microsoft in february 16th.

    After that, two of the same computers crashed AGAIN, on the same day, even with the new ISO. Then I searched online for newer questions and, not to my surprise, a lot of people are having the exact same issue.

    The only thing in common that these computers have is that all of them run on SSD (all using intel processors). I don't know if that is relevant, but hope that this helps to prevent this from ever happening again. The repair PC dialog is pretty much useless if you don't know what you are doing, none of the options help at all.

    Regards.

    Was this answer helpful?

    0 comments