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-01-17T22:25:16+00:00

More computers are crashing in my office. It may be related to the act of restarting versus shutting down and powering back on. I know that sounds strange, but computers that ran fine all week, shutting down every night, have been crashing after a restart.

Also, I got the dism remove packages trick to work, but windows reinstalled the roll-up fix immediately after restart, even though quality updates are deferred for 30 days. It subsequently crashed on the next restart. This is turning into my worst nightmare.
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-17T22:26:42+00:00

Kin,

Agreed, I just restarted one of the computers and the same thing happened :( Resorting to backup's and restoring.

I guess the best thing to do is if you try it, disable internet, disable windows updates in system processes. Backup your files while your system is up if you haven't yet. Could also make an image at the time, then test it later in VM re-enabling windows updates to find a fix or workaround? Not sure what else can be done other than reinstalling after it fails.

I believe this needs to be addressed by Microsoft if it continues in the future.

Rollup Fix Patches seem to be an issue.

I'll keep following

Showster
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-17T23:01:02+00:00

Does anybody from Microsoft follow this thread?

Any response from the company?

Or are all Microsoft experts currently in a meeting in the tree houses?
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-17T23:15:35+00:00

I don't work for Microsoft but I'm making sure this thread is escalated. I also have two official pro-level support cases opened up trying to investigate what is going on. If anyone has a sample that you are willing to let me open up a professional support case for, send an email to sbradcpa-at-PacBell.net and I'll need a phone number from you to set up a support case.
Was this answer helpful?

0 comments No comments