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-14T19:34:05+00:00

    I continue to have machines fail that are just now rebooting for first time in several days (to several weeks). I have NOT experienced machines that the DISM fix, removing the 16299.192.x.x patch would not work on. BTW Microsoft DID finally admin / recognize the problem this past Sunday! Susan Bradley posted a link to a comment from the Windows 10 Feedback Hub about that...  

    https://aka.ms/I72l5n

    Now that they have acknowledged it, perhaps a permanent fix will soon follow!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-02-14T19:41:13+00:00

     Susan Bradley posted a link to a comment from the Windows 10 Feedback Hub about that...  

    https://aka.ms/I72l5n

    My account does not have access to that feedback....  What did it say?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-02-14T19:53:18+00:00

    I was able to recover in this case by running this command:

    DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\$Windows.~BT\Sources\Install.esd /LimitAccess

    Unfortunately, my DISM doesn't seem to support these options - these switches just don't exist. A difference between Home and Pro editions, perhaps?

    I did find a recent Restore point, but it doesn't work either - same INACCESSIBLE BOOT DEVICE on startup.

    Any other ideas for getting this running at least one more time (so I can do a full Windows 10 reinstall)?

    DISM Does support those commands If you are on the machine and have windows loaded. (/Online)

    If you are booting from other media, or are in the recovery environment, those commands are not supported.

    Scroll back to My 3 posts on Feb. 10th around page 30 for the exact procedure.

    Wiz

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-14T20:17:04+00:00

    Hi. An update 02/13/18 triggered BSOD. I ran the fix suggested here and received an error msg saying the scratch drive was too small to handle the removal. Now what? The package removal suggestion seems right, but I need a way over this next hurdle.

    Thanks.

    Tam Hofer

    Was this answer helpful?

    0 comments