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-09T02:43:21+00:00

I also have the same problem, system restore does not work

Please hel me
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2018-02-07T20:36:40+00:00

Those of you saying “All the patches that caused problems have been fixed”, thatbis simply not true. I have now had (2) systems that have been completely reloaded, that upon download updates. Have BSOD’d again! This is getting really OLD!

As far as I can tell, if DISM won't get you to at least one boot, the only remaining option is a system reset. This at least preserves the data and some settings.

As I have stated earlier, I have worked on one intel and 4 amd systems.

The Intel would system restore from the recovery environment but still not boot.

One of the AMD systems just froze after the update rather than Inaccessible boot device.

That one responded to a system restore. I figured out which update caused the problem and then hid it.

The other 3 were AMD systems and required DISM to remove the patch and then got the system to boot.

Since I had imaged the drive (using another machine), I was able to repeat the process after I discovered there would be no second boot.

The only way I could fix the problem was a repair install.

All the patches that caused problems have been fixed.

I would assume that whoever green lighted the posting of the bad patches has either been fired or severely reprimanded.

I am sure that for the immediate term, you won't see this happening again.

wiz
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2018-02-07T04:46:06+00:00

If windows is up and running, you need only do a repair install. got to

https://www.microsoft.com/en-us/software-download/windows10

and download the iso image. once its done, click on it to mount it and then run the setup.

It will reinstall windows 10 keeping all your programs and data.

After that is done, your machine will reboot and startup normally.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments

Anonymous

Again is there a procedure to ID the bad patch, delete it before it tries to load on a reboot?

For reboot pending check up the registry in these places:PendingFileRenameOperationsat "HKLM:\SYSTEM\CRebootRequired  at "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update"RebootPending "HKLM:\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\" System Center Configuration Manager wants to reboot by looking at Invoke-WmiMethod -Namespace root\ccm\clientsdk -Class CCM_ClientUtilities -Name DetermineIfRebootPending | Select-Object RebootPending

There is a script from Microsoft checking in these places. The script did not work on a workstation for me though (it is meant for Microsoft Servers). https://gallery.technet.microsoft.com/scriptcenter/How-to-check-if-any-4b1e53f2/

EDIT the registry keys break up after I paste them here,

PendingFileRena

0 comments