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-01-18T20:15:33+00:00

    Bobby?  Can you post up your support incident number?  Thanks in advance.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-18T21:08:11+00:00

    This worked on an AMD system:

    1. BSOD after installing Jan-2018 Cumulative Update.
    2. System Restore to restore point established before step 1.
    3. Reboot after System Restore to an again working system.
    4. Allow Windows Update to again install the Jan-2018 C.U.
    5. Before rebooting the system, installed KB407391.msu downloaded from the Microsoft Update Catalog (330MB, 15 min. to install on an older, slower system).
    6. Rebooted after installation complete. Successful restart, no BSOD.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-18T21:52:16+00:00

    OKAY Dave,

    "I can do that"  😉 hehehehe (You probably know the reference.)

    I am aware from what you have said with your degrading progress that you can't boot into anything. Had you thought of this the first time you were able to Boot up at least to Safe Mode, that is when you should have LOCKED DOWN WINDOWS UPDATE/MICROSOFT UPDATE(not trying to whip on you).

    However, others maybe just starting this process so should be aware of this earlier.

    I will be frank with you Dave, I have AU/WU/MU LOCK DOWN all of the times!!!! You are obviously experiencing for the FIRST TIME why, I do! When I was on W 7 and early W 8, that adoption came in extraordinarily handy.....

    I am also an Insider Fast Ring(I have 6 partitions possible for OS's) so that partition is living out on the edge but LOCKED DOWN with regular Image backups as are my other 3 active OS. I NEVER EVER rely on MS to take care of me and mine, I have been let down to many times. With MultiBoot, Recovery Points don't work, so I use Tweaking Registry Backup every time I logon. I have had Recovery Points fail me too, in the past. I read some where(here I think) where somebody was trying to recover and found only one Restore Point left that wouldn't work.... well go figure MS, that's what keeps 3rd parties in these support businesses/efforts.

    It sound like this particular PC is in rough shape, so be careful not to make it worse.

    WinPE.....

    • Windows ADK downloads - Windows Hardware Dev Center
    • You want at least DISM, Tools(SFC,CHKDSK) and WinPE Components, there maybe others that you want???? They of course wouldn't go into WinPE.
    • When Installation is complete, look in "Program Files" on 'Start Menu' or 'Tool Bar' if you use that method under ADK, for the CMD Icon saying something about WinPE.
    • Have your USB(formatted NTSF default) or DVD(Erased) ready to go.....
    • Using Admin Rights on Context Menu for CMD file, start it.
    • I prefer to create an ISO so I can make several disks but I think one can go directly to disk(USB/DVD).
    • If ISO and USB, get the latest copy of Rufus and build a single partition(Best) USB drive, then "Eject" it or "Burn" to DVD.
    • Reinsert the USB and restart to see if it worked. It should Boot right into the USB Drive, then right into CMD.
    • Play away.....

    You might find NirSoft handy to, I use his Registry Scanner allot.

    Best Regards,

    Crysta

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-19T00:06:25+00:00

    I copied the files from \Windows\system32\config\regbackup back into config And now I’m stuck on the windows logo spinning wheel.  I don’t get the blue screen for inaccessible boot device anymore but I can’t get into the system ...  now not sure what the heck to do LOL .  If anyone can help me that would be great I really don’t want to do a clean install on this PC as there’s a lot of  configuration on it now.

    Was this answer helpful?

    0 comments