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-17T10:46:25+00:00

    We have the same problem. Upgraded from wins 7 pro to wins 10 pro. I have 2 problems. Memmory Management error and Inaccessible error. Paid almost $1,000 and useless now. Did u fix the problem? Pls, let me know

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-16T22:44:17+00:00

    Hi,

    I've mentioned this before, but have you tried downloading a Build 15063 ISO and booting from it to get to the Command Prompt for your BootRec commands ?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-16T12:48:26+00:00

    Hello,

    I would have to assume your system is not starting "properly", hence

    not even allowing you to start into "Safe Mode with Command prompt" ?

    But even in the case your system is unable to boot or you're unable to

    login, there's always the possibility to start with the so-called

    "Recovery Environment" and make any modifications via the command line.

    To make any registry modifications there, you would have to run

    "regedit" as usual, but have to and issue "load hive" (to make the

    required changes to your "PC's" registry instead of your "recovery

    environment's" registry).

    ("Recovery Environment" is either available via your Windows 10

    installation media or via "F8" during your PC's boot in case you did

    install/setup it before ...).

    You find several how to instructions for doing so, e.g.

    http://www.winhelponline.com/blog/edit-registry-offline-windows-re/

    Anyway, "inaccessible boot device" can be caused by several

    circumstances, but in case you are also suffering from it since having

    upgraded from 17046 to 17063 or 17074, it is very likely it's also

    caused by some legacy file system filter not been installed/used after

    Microsoft obviously decided to block it per default now.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-16T11:36:45+00:00

    Not sure my issue has anything to do with Veritas, but in any case, how can this registry key be added if Windows can't be logged into?  You did this through command prompt?

    Was this answer helpful?

    0 comments