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 No 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 No comments

506 additional answers

Sort by: Newest
  1. Anonymous
    2018-03-12T16:45:22+00:00

    I just want to add a note in for those who were like me and did the fix and restarted before you knew or could do a repair install. 

    DO A SYSTEM RESTORE to before the date you removed the update, then go back and do a DISM and the update will be back! Remove it, reboot, and do repair install while in windows!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-03-08T05:40:14+00:00

    Warranty repair wont cover software problems.  They will reformat your drive and reload the original windows that came with the machine.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-03-08T05:00:55+00:00

    I got this error 2 months ago and did a complete reset and reload my programs in  and today I have the same issue.  This notebook is only 4 months old. I don't want to send in for warrenty repair!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-03-08T02:27:42+00:00

    Hmmm. Tried booting into Windows, got the Inaccessible Device message, went to the command line, tried using WUSA to install this update, get "insufficient disk space" message. My guess: it thinks I'm trying to update the mini-Windows running on the X: drive, not my damaged installation.

    How do I get this update applied to my damaged copy of Windows?

    Was this answer helpful?

    0 comments No comments