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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-01-19T18:56:50+00:00

    Hi, just to add my notes with this issue:

    1. There seems to be a intentional lock after several re-boots that stops the "Inaccessible Boot Device" message and instead it re-boots, forever.
    2. Using USB boot, in my case the list of updates are logged as updated (as suggested at  www.windowscentral.com/how-fix-update-causing-inaccessible-boot-device-error-windows-10).  
    3. I can use the disk as non-boot on a different PC, so that's good... if I could find which files/registry entries are affected.  
    4. Windows support appeared do not have a clue. 

    Yep, this is insane.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-19T18:34:12+00:00

    GOOD LUCK, keep us informed.....

    Best Regards,

    Crysta

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-19T17:48:34+00:00

    Tried to create a restore point after removing 16299.125.1.9, but restoring to that point leaves Windows in a non-booting stage. Like others are saying, you get to boot once and that is it.

    16299.125.1.6 and 16299.98.1.20 also show up as Rollup updates, but removing those doesn't fix the INACCESSIBLE_BOOT_DEVICE error.

    I'm going to try the single earlier restore point and see if the removal of 16299.125.1.9 works for a single boot again. If so, I'll disable Windows Update service and see if the computer survives a reboot or not.

    After the restore it should come back to use the dism again. I had one computer that it didn't work on but finally it did. Be persistent, if you get errors then something isn't spelled right. Check and make sure it is exactly right. I took and disconnected the internet so it can't download any updates and disabled windows update in the manage/services area and it survived two reboots. Good luck.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-19T17:32:25+00:00

    Tried to create a restore point after removing 16299.125.1.9, but restoring to that point leaves Windows in a non-booting stage. Like others are saying, you get to boot once and that is it.

    16299.125.1.6 and 16299.98.1.20 also show up as Rollup updates, but removing those doesn't fix the INACCESSIBLE_BOOT_DEVICE error.

    I'm going to try the single earlier restore point and see if the removal of 16299.125.1.9 works for a single boot again. If so, I'll disable Windows Update service and see if the computer survives a reboot or not.

    Was this answer helpful?

    0 comments