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-02-27T00:24:01+00:00

    Ira?  I'm checking on your question about how best to uninstall a pending install where the system hasn't been rebooted.  Hang tight.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-02-27T00:23:26+00:00

    I just edited it, let me know if that's good enough.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-02-27T00:09:55+00:00

    I agree that it is confusing.  There are many things unrepeatable with this issue and many inconsistencies.  I can only say that I have had a couple (few?) cases where there was no package to remove after a second boot attempt.  This was before we identified the limit of "one boot only".  A system restore followed by failure to boot then allowed seeing and removing the rollup package which then resulted in a successful boot.  Then the inplace upgrade restored repeatable boots.  I can't explain why; just reporting my experience.  "No guarantees".

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-26T17:21:53+00:00

    Status: You can't boot. DISM doesn't work.

    Try this: From the recovery environment do a system restore.  YOU STILL WON'T BE ABLE TO BOOT but I have had a few cases where (after doing the system restore) the DISM remove-package command then was successful and allowed a successful boot.  THEN IMMEDIATELY do the in-place upgrade and follow all the other cautions listed in this thread.

    If you use imaging backup software, I have also been successful restoring an earlier image of the Windows drive and then being successful using the DISM remove-package command.

    Which restore point do you choose?  You can start with the latest and work back.  I haven't found any consistency.

    Hope this helps.

    IRA, a system restore is a two part utility. The first part happens from the recovery environment.

    But the second part needs a good boot to finish.   If the system Blue Screens because of an invalid boot device,

    it won't complete the system restore.

    I don't know, there may be circumstances that system restore will put the system back into a state where you get a second bite at the apple, but it seems unlikely.  Most of the broken machines that I've fixed had no restore points.

    But it's worth a try if all else fails.

    wiz

    Was this answer helpful?

    0 comments