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: Oldest
  1. Anonymous
    2018-03-15T09:25:00+00:00

    Margie,  I wish I had good news for you.  I can't be sure, because I don't use drive encryption, but I believe that you need windows loaded to be able to access.  My advice is to contact microsoft on this one

    Just to be sure, you are getting an "Inaccessible boot device" blue screen after installing the january windows rollups?

    These procedures only work for that specific issue.  There are many other conditions that cause "inaccessible boot device" errors.

    good luck.

    wiz

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-03-15T09:38:45+00:00

    DSC_22.

    If you follow my 3 page post around page 30 of this thread and you reboot without doing an in-place upgrade, you are left with having to do a windows reset.

    This of course knocks out all your programs, but keeps your data intact.

    reinstall the programs and you are back in business.

    You might even try rbalin's method of putting the programs back (without re-installing) about page 34 dated 02/14/2018.

    It sounds like it might work.

    I didn't need to do that because I took an image of the drive before I worked on it.

    When one procedure failed I would simply re-image and try again.

    Note that using an imaged drive may remove the possibility of using any system restore points. (unless it's a bit by bit image),

    Good Luck,

    Wiz

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-03-15T12:19:21+00:00

    I woke up this morning to this error message on my PC.  What is the best fix for this issue?  Is it Showster's work-around above or is there now a long-term Microsoft fix?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-03-17T14:37:36+00:00

    Unbelievable  Windows 10 301 just bsod my 32bit pc.    I was able to dism it off and restart but now there is no mouse or key board access  This is crazy!

    Was this answer helpful?

    0 comments No comments