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-02-11T00:05:45+00:00

    Ok -- AMD is the first chip for MSFT to port the OS; Intel released the 64 bit Merced in 2003 which is way before Advanced Micro Devices was a smile on a gamer's face.  Thanks for the note as I'm hopeful the history lesson helps ;-)

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-02-10T14:53:47+00:00

    AMD in this patch context refers to the 64bit platform, not the chip on the machine.

    AMD is the one that first introduced 64bit platform.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-02-10T14:22:28+00:00

    I removed both Rollup Fixes and my 64bit Quadcore Intel Notebook rolls again.  As an FYI -- most of the reading referred to AMD and in-fact the Rollup Patch shows AMD in the name.  So, if your issue is Intel based and none of the Windows PE, Boot repairs work I'd encourage removing the patches as noted.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-10T13:54:38+00:00

    Thank you so much for this!  I thought for sure I was dead in the water, and I had already tried a bunch of other troubleshooting tips I had found online (but none worked).  I watched a bunch of YouTube videos, too, but no one had this exact fix listed.  My Rollup Package ended up being the first one I removed, which was dated January 15, 2018.  I was skeptical that removing it would do the trick because Automatic Repair loop didn't start happening until Feb. 8th or 9th, but it worked!  I don't typically reboot my computer that often; I usually leave it running so maybe that's why I didn't experience the issue until weeks later.

    Anyway... THANK YOU!

    Mark

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments