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-04-03T23:55:37+00:00

    I had this issue back in February and was able to fix it by doing the DISM remove.

    I had the issue again a few days ago and was again able to fix it by doing the DISM remove.

    After booting back up I saw the Windows Upgrade Assistant was going to re-apply it so I uninstalled the Assistant, turned off all scheduling related to the assistant, set the business profile, turned off updates for 365 days, etc.  Appears it was too late, the next boot it bricked my system a 3rd time.  

    I was able to remove some of the updates, but the main Rollup Fix is listed a permanent.  Through the recovery console I was able to have it roll back to the old windows (I think it copied Windows.Old back to Windows), but now I can't boot. 0x0000000f

    It appears the MBR is all jacked up.

    I tired doing:

    bootrec /FixMBR (says successful) but it just goes back the 0x0000000f error if I try to boot.

    bootrec /FixBoot (says access is denied)

    bootrec /RebuildBcd (fails)

    Tried doing:

    bcdboot c:\Windows  (Failure when attempting to copy boot files.)

    When I try:

    bcdedit /enum I get:

    The boot configuration data store can not be opened.

    The requested system device cannot be found.

    This is the worst experience I've ever had using Windows (have been using since 3.1 days)  A forced upgrade that bricks your OS repeatedly...  

    I'm a Android Software Developer and have not been able to work from home the last few days because of this.  Maybe this is why MacOs seems to be used more and more in the workplace here in the valley...  I like Windows but when I have to spend hours of my time trying to fix a bricked system because of a forced upgrade that I don't even want, it's becoming a money losing proposition.

    Rant aside, is there any way to remove this "permanent" RollupFix or to recreate my MBR?  I'd really like to have my working system back rather than reimage, have to reinstall my programs, then pray that it doesn't just brick my system again...

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-03-31T17:03:15+00:00

    Msny thanks my friend.  This worked like a champ on Windows 10.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-03-30T21:51:37+00:00

    Inassecible boot device. Help meee

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-03-27T08:06:32+00:00

    when I try to log on into my computer blue screen appear and said '':(Your pc ran into a problem and needs to restart.we're just collecting some error info, and then we will restart for you" after that it just said "preparing automatic repair"

    Was this answer helpful?

    0 comments