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-17T00:29:30+00:00
Edit: clarification at bottom, spelling

I've tried all of the solutions I've seen in this thread without prevail on a particular machine I'm working on (I'm IT). I ended up doing some experiments that resulted in a fix. Here is the final fix I came up with.

I've had this fix fail on machines as well, so it isn't by any means a foolproof fix, but hopefully it gets some people out of a jam.
- Do other repairs (System restore, DISM to remove packages, DISM restorehealth, reg edit to set Exclusive flag to 0)
- If still can't boot into Windows after these repairs, put another hard drive in system
- Do fresh install on new hard drive - then after it is running (I installed from a flash drive with 1709 installer, otherwise you may need to update the fresh install to 1709 before continuing), Load up recovery environment (Shift+Restart button)
- Load up the system registry of the fresh install (regedit on command line, select "Local Machine", File->Load Hive, \Windows\System32\config\System) - name it something arbitrary, but something you will remember (I name mine "system-fresh")
- select the key you just named (system-fresh), File->Export
- Export the entire system registry to a file you can access later (Put it on a flash drive) (file: E:\system-fresh.reg)
- Shut off machine, plug in hard drive with original OS on it. Boot into recovery environment again
- Make a backup copy of \Windows\System32\config\System ("copy D:\Windows\System32\config\System System.old")
- Load up system registry of the broken install (same method as done with fresh install - make sure to name the hive the same (system-fresh)
- File->import: E:\system-fresh.reg
- May not be able to import all of it due to permissions issues, but I've had it work after it errors
- Reboot - hopefully it'll get into the OS this time.
- Run in-place upgrade to fix OS issues, or else you may end up with it failing again after working a single boot.
If clarification is needed on instructions, let me know. I skipped over a lot of the details of how to go about this process, but can elaborate if needed.
Was this answer helpful?

0 comments No comments
Anonymous

2018-02-16T23:35:43+00:00

I'm still monitoring this and am pushing Microsoft to come out with an authoritative KB or some better communication.

Still the best solution is pull off those offending patches, do an inplace refresh. Worst (horrific case) is to totally rebuild. Again as a shareholder of Microsoft, I apologize that I don't have a better solution.
Was this answer helpful?

0 comments No comments
Anonymous

2018-02-16T22:41:41+00:00
The in place upgrade will only work if:
1. You got an inaccessible boot device after January 2018 upgrades.
2. You got the system to boot after using the DISM command to remove the defective packages.
3. You then did an inplace upgrade with version (1709) that you obtained using the media creation tool.
4. You do not check the box "get the latest updates".
I always removed the hard drive, connected it as an additional hard drive and imaged the drive before doing any work on it. That way, if things didn't go right, I would get additional chances to solve the problem.

As for Microsoft providing an official method to fix the issue: I don't think we will ever see a KB article about it. See my earlier comments as to why.

wiz
Was this answer helpful?

0 comments No comments
Anonymous

2018-02-16T22:16:43+00:00

Want to closely monitor Microsoft's solution but don't know the best place.

Ditto.
Was this answer helpful?

0 comments No comments