Question

Q: Inaccessible Boot Device error - cause? fix?

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...

Answer

A:

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

Showster,

It worked.  Thank you, Thank you. This repaired the Inaccessible Boot Device error on my Dell XPS8500 PC.  I have Windows 10 Professional operating system. 

<moderator Susan note:  I'm going to flag this as the answer just to let folks know of a workaround.  The true answer to this is to find the root cause of the problem and ensure it never happens again. Microsoft is working on a long term fix>

https://support.microsoft.com/en-us/help/4075150/how-to-recover-devices-from-an-unbootable-state-after-installing-the-j

Follow that KB first and be aware you have one shot at those commands.  Posters here have reported that if they futz around do various other commands, they lose the ability to follow that KB.  So hopefully you have come here first and read this post first.

Note to those reading this:  Make sure you put a space between the two \ and / in this command:  Dism /Image:D:\ /Get-Packages

More guidance - https://www.reddit.com/r/pcgaming/comments/7sbkxc/howto_fix_inaccessible_boot_device_caused_by/

Worse case scenario (1)  - do a refresh of the operating system that doesn't lose your data but will mean you'll need to reinstall the programs.

Once you complete the dism boot with a Windows 10 ISO and go into troubleshooting and choose to refresh the operating system.  Look here:  https://www.tenforums.com/tutorials/2294-boot-advanced-startup-options-windows-10-a.html for more details.

Worse case scenario (2) reinstall the operating system.  It's my understanding that the issue is no longer triggered by the Feb updates and thus if you reinstall by downloading media from https://www.microsoft.com/en-us/software-download/windows10 that you won't catch the faulty code.

Be aware that both this issue (inaccessible boot device) and missing usb devices have the same root cause - a key driver is being uninstalled and is not being reinstalled during the patching process.

I would strongly recommend going forward that if you have a configuration that you must keep - have a plan to make a full backup of your system.

If you are still getting this error on clean install or refreshed systems AFTER Feb 2018, please post here or pop me an email at sbradcpa-at-PacBell.net (change the -at- to @) and I'll set up a support case.

<End moderator note>

Did this solve your problem?

Sorry this didn't help.

119 people were helped by this reply



 
Question Info

Views: 126,175 Last updated: July 19, 2018 Applies to: