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-23T16:17:21+00:00

Does anyone have a link for Pausing Windows 10 updates via AD Group Policy?

Thanks

Dan

This is the only doc I have that gets you close in the Registy. There are links in there that might help. Yes I know it is old but most will work in W 10 1709. This is some of what the WSUS & SCCM Environments use to control the local end points:

Configure Automatic Updates using Registry Editor https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd939844(v=ws.10)

Here is something else that might help you to for, local, Servers and Azure: http://gpsearch.azurewebsites.net/#

Best Regards,

Crysta
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-23T15:54:52+00:00

Does anyone have a link for Pausing Windows 10 updates via AD Group Policy?

Thanks

Dan
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-23T06:24:28+00:00

Anyone know how to actually change values through the command-line interface? All I can find is how to add, copy, or remove...

EDIT: Just tried to run regedit.exe and it works! The UI actually pops up. Only problem now is that it's of the Windows Preinstallation Environment (off the disk) so the "HKEY_LOCAL_MACHINE" (or any other) folder needs to be selected and you need to use the "Load Hive" option under the "File" dropdown, load the "Software" (or whatever appropriate) hive from the "Windows/System32/Config" path on your Windows drive, give it whatever name after you open it, make your changes, and unload it back.

In my case, I was almost sure given some of the errors in the DISM log listed as well as from the behavior of the SFC tool that the issues may be caused by a pending Windows restart. From the start I wanted to find a way of potentially disabling that identifier. I'm surprised, having looked in the registry, that my values for "Exclusive" and "TotalSessionPhases" under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\SessionsPending were already 0 (0x00000000).
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-23T06:13:02+00:00

I'm saying the ones I'm tracking are Intel based chips.

Hi Susan, add mine on your list. Currently using the i5-8400 and this same BSoD message pops up. My computer is only a couple weeks old and already crashes. Darn it.

My computer was working beautifully until yesterday. Then when I tried to turn it on...

INACCESSIBLE_BOOT_DEVICE

Sigh.

I've tried the sfc and even a chkdsk (a bit risky, I know). Even did a standard auto Repair via the WinRE, not that it fixed the issue but I was running out of options. I even removed any Pending Updates and it still fails to boot. I can't even start my OS into Safe Mode. I also did a couple of System Restores (I only have a few Restore Points to choose from because my PC is new) and still no change.

You guys are lucky that some of your fixes work and you still manage to enter your OS. At least you have a chance to stop the Update. I don't even have that luxury. I'm stuck in the BIOS loop and the WinRE.

I'm going to do a few more tries later, but if all fails, I'd just Reset and if that still fails... Then I guess I'll reinstall the whole thing.
Was this answer helpful?

0 comments No comments