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-19T19:04:46+00:00

An important note:

on another machine presenting the same issue, the acpi service registry entry had a “DeleteFlag” entry set to “1”.

I’ve tried setting it to 0, tried removing the whole acpi entry from registry and importing the known-good that i have, tried replacing acpi.sys with a known good file. Nothing has worked so far.
Was this answer helpful?

0 comments No comments
Anonymous

2018-02-19T18:58:26+00:00

I'm sooo sorry I missed your emails. Got them now. You gave a great hint as to what is going on. Something appears to be messing with the acpi.sys file during the update process. Now let's see if we can figure out what.
Was this answer helpful?

0 comments No comments
Anonymous

2018-02-19T18:52:53+00:00

Hey Susan,

unless I got your address wrong, I did send them? Email me at handstand2001 at hotmail

handstand2001
Was this answer helpful?

0 comments No comments
Anonymous

2018-02-19T16:52:06+00:00

Handstand? Can I please (pretty please?) get copies of your cbs.log files from those impacted machines? I'd love to dig into the details more and figure out what is causing this driver to get unloaded.
Was this answer helpful?

0 comments No comments