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-10T14:22:28+00:00

I removed both Rollup Fixes and my 64bit Quadcore Intel Notebook rolls again. As an FYI -- most of the reading referred to AMD and in-fact the Rollup Patch shows AMD in the name. So, if your issue is Intel based and none of the Windows PE, Boot repairs work I'd encourage removing the patches as noted.
Was this answer helpful?

0 comments No comments
Anonymous

2018-02-10T01:49:42+00:00

Perfecto!!!! This worked when all else failed! Thanks for the sharing and passing on the info.
Was this answer helpful?

0 comments No comments
Anonymous

2018-02-09T20:36:41+00:00

ApexInd, One thing you didn't mention, that is buried in the thread, is that when you are logged in during that one, and only one successful reboot, run an in-place windows 10 upgrade from a current Windows 10 Load disc found at:

https://www.microsoft.com/en-us/software-download/windows10. I needed it because my original load discs were old and didn't sit at the 1709 level which I found was a requirement. It can take an hour or more to run but when done the boot problem is resolved and all apps are in in good shape. Sometime it takes a couple of reboots to get the network card to work. Hasn't worked every time but usually because I missed something getting that one good boot up and never had a chance to run an In-Place upgrade.
Was this answer helpful?

0 comments No comments
Anonymous

2018-02-09T17:38:13+00:00

I want to thank everyone for their input on this thread in helping to resolve this issue. It's been an extremely frustrating week while this bad update took out more than a few production PC's at our company resulting in 3 days of downtime. I ended up having to reload Windows 10 and software completely, and as i write this, i'm having to reload yet another this morning...

Running DISM per Showster's suggestion to remove the bad patch had seemed to work for one reboot on all the affected machines, only for them to fall into the same pattern of failing to boot the next day and bringing them to the "Advanced options" boot screen. Nothing else has worked under those options to repair the PC, whether you choose Startup Repair or booting into Safe mode. Nothing. The system halts the boot process every time.

I'm glad MS has resolved this with the .214 patch to KB4058258 update, but after this week it seems per our experience that the bad version of the update cannot be fully removed from the troubled machines. The only way I've been able to get my downed computers running again is through a complete system reset (reload of windows 10), where then windows update loads in the .214 in place of the previous...

We've all seen bad patches before and I understand that folks at MS are human, but because of the sheer amount of heartache this has caused our company this week i have to ask.... What the heck happened here? What did you guys at MS miss that ended up with PC's just deciding to catastrophically fail one day?

This simply should not happen.

As we've all seen the aggressive nature of WIndows updates and entire builds being pushed out since WIndows 10's release, I just knew i might find myself in this situation one day where work is needlessly disrupted.

Get it together, Microsoft. Test your ****. This is unacceptable and is the kind of nonsense that costs people money and lost time.

-Another frustrated IT Admin.
Was this answer helpful?

0 comments No comments