Inaccessible Boot Device error in Windows 10

Anonymous

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?*

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

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

0 comments

506 additional answers

Anonymous

2018-02-14T19:27:58+00:00

Been monitoring this thread and using the dism remove-package fix, to get one boot and doing an "In place upgrade" with some success. Like many on the thread, I told customers to not reboot so we could get a consistent fix. Here we sit 2 weeks later, no MicroSoft input. I am now finding these systems, we kept booted, failing and the fix now not working that we relied on in the past.

dism /image:D:\ /get-packages gets more packages in either the Install Pending State, Uninstall Pending State or Superseded State.

Many found Package_for_RollupFix.....16299.192.1.9 as one of culprits. It now has a Uninstall Pending state and shows as not present in the image when trying to remove.

A new package installed 2/13/2018, Package_for_RollupFix....16299.248.1.17 sits at Install Pending state, fails with an 0x80070609 error when removing, reporting that "A system reboot is required to roll back changes made" (fat chance)

Package_for_RollupFix.......16299.125.1.6 shows a Superseded state.

Is anyone else noticing this change and that previous fix is now not working?
Was this answer helpful?

0 comments No comments
Anonymous

2018-02-14T17:24:17+00:00

I have had another occurrence of the "Inaccessible Boot Device" on a different system. The first one I ended up rebuilding the entire system from scratch, however I used a new hard drive since the files on the original disk are still accessible. I have run advanced options, system restore, etc. all resulting in the same issue. System will not boot in safe mode before or after restoring. Nothing has been added or removed from the system for a long time.

The only thing in common between the failing systems is they were migrated to Windows 10 from either Windows 7 or Windows 8.1. I suspect the problem will occur on the other migrated Windows 10 systems sooner or later.
Was this answer helpful?

0 comments No comments
Anonymous

2018-02-14T16:37:22+00:00

Any other ideas for getting this running at least one more time (so I can do a full Windows 10 reinstall)?

I am sorry, I gave you wrong command. The image is offline during repair. So it should be something like this:

dism /image:D: /Cleanup-Image /RestoreHealth /Source:C:\$Windows.~BT\Sources\Install.esd /LimitAccess

Be sure your \Windows directory is in D:, correct accordingly.

Be sure in your dir ``C:\$Windows.~BT\Sources\Install.esd the file Install.esd really exists, just by typing

dir ``C:\$Windows.~BT\Sources\

The file install.esd should be there.

If not adjust the drive letter accordingly.
Was this answer helpful?

0 comments No comments
Anonymous

2018-02-14T05:24:39+00:00

Okay, I am just a simple user but I was able to use Showster's answer to get back up. I have not turned off my machine and it indicates an update will take place when I shut down. Now, I am terrified that In will be back to the blue screen of death next time I boot up. How do I do an in place upgrade or prevent my problem from reoccurring? As I say, I am a simple user so I need detailed help. Where can I get it or get an easy fix if I need to do something to go forward.

The bad update installed again overnight . I was able to get back on and am now doing an in place upgrade. I hope it works. Thanks to everyone who looked at my issues. Microsoft needs to do something about the update that is apparently still out there.
Was this answer helpful?

0 comments No comments