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-31T02:18:36+00:00

    Try the solution I posted on page 17

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-31T02:16:46+00:00

    Try my solution on page 17

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-31T00:07:44+00:00

    We noticed this after I posted this bypass solution at the time between the top of page 5 and all the discovery around page 10 of the post because we had/have no support from Microsoft.  It was a temp fix i found from another nice tech at the time.  Read the entire thread please.

    As of right now, there is no solution other than to resort to a backup...  OR.. Back up your current drive as an image to another drive so you can dump you data back on later....  After you reformat and reinstall...  That's what your left with... because of you know who.

    A lot of other kind folks on this post gave great information on how to try and fix the issues at the time at hand, some worked and some didn't, but without resolution from the source we're pretty much SOL.

    Blame the source...  Always back up your data on a daily basis.

    It's sad to think that there is and will be 1000's of other individuals and full networks of 100's to 1000's of computer that will be affected by this without any help from the source that causes the issue.  That is why we're here to begin with or we wouldn't be talking about it.

    Showster

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-30T23:41:32+00:00

    Is anyone else finding that this dism solution works for ONLY ONE REBOOT and then does it again. I removed four update via this fix and rebooted into windows successfully. Immediately paused updates and rebooted again. Now same BSOD and NO new updates showing in DISM to remove. 

    Yes, I have found this to be the exact case on the two PC's I have been fighting.  After first boot, tried turning off updates several ways, also with running the KB4078130 on the last try.  Never get up again after rebooting, BSOD.  The first successful boot must load something as it comes up, but I can't find it.  Worked since 1/23 reloading the image backup and starting over with suggestions from this forum.  Fail at this point every time.  Had to give up and reload from scratch.  Have over (50) win10 I5 computers in customers offices with instructions not to reboot.  Could be a disaster if they start failing with no change to get past just a one reboot fix.

    For everyone's information I am not using Symantec AV, using Vipre Endpoint Ver 10.

    Was this answer helpful?

    0 comments