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-01-30T22:51:22+00:00

    Hi Showster, 

    When I follow your steps, I get stuck after - 

    Run the following to view the installed packages which will also show a date of install.

    Dism /Image:D:\ /Get-Packages

    I type - D:>Dism /Image:D:/Get-Packages

    I get - Error 1639

    Could use your assistance.

    Thanks,

    PH

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-30T20:46:51+00:00

    https://support.microsoft.com/en-us/help/12415/windows-10-recovery-options

    If you can't open Settings, you can get to reset by restarting your PC from the sign-in screen. Press the Windows logo key Windows logo key  +L to get to the sign-in screen, then hold the Shift key down while you select Power  > Restart in the lower-right corner of the screen. After your PC restarts, select Troubleshoot > Reset this PC.

    If you can't get to the sign-in screen, use a recovery drive or installation media to reset your PC.

    Boot from the flash drive, go into troubleshooting. From there you can reset the PC.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-30T20:44:28+00:00

    Given that the inaccessible boot device means you have an unbootable device, there's no way to "roll back the impact" with a patch that merely is installing registry keys.

    Let me go see if I can get any sort of unofficial official guidance here.  All we have right now is get a bootable ISO, boot from that, go into the troubleshooting section and do a refresh (does not remove applications, only refreshes the OS) as a "solution"

    Susan, can you provide anything that describes the "refresh" how to, to avoid loosing apps? Every attempt I make, and every article I find, says I can only start that process if I am successfully booting into windows already. I have tried starting setup from the command prompt, and booting to a USB. Neither work.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-30T20:09:53+00:00

    Is anyone else finding that this dism solution works for ONLY ONE REBOOT and then does it again. I removed four update via this fix and rebooted into windows successfully. Immediately paused updates and rebooted again. Now same BSOD and NO new updates showing in DISM to remove.

    Was this answer helpful?

    0 comments