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-31T17:33:58+00:00

BTW: I called Microsoft several times on this issue. They were of no help.

The support staff was being overwhelmed (by similar issues I suspect), because wait times were over 45 mins.

I explained that I had access to more that one machine and I could mount the affected hard drive in a working machine to

gain access to it to help resolve the issue. I explained that I had done all the necessary checks: checkdsk, sfc, etc.

I explained that a I had images of the affected hard drive and if one strategy failed, I had another hard disk with the image waiting.

I explained that system reset worked, but that was not a desirable outcome. l had over 50 programs installed and didn't want to have to load, configure and update all of them.

I explained that I had performed disk, CPU and memory checks and all the hardware was in order.

I explained that taking a blank hard drive, I could install windows 10 (1709) and it worked fine.

I just wanted to back out the last update that crashed the system.

1st tech: put me on hold for 5 minutes and then hung up.

2nd call, couldn't wait the 45 minutes and gave up after 30.

3rd call indicated that support times were heavier than normal, then said that support was closed (there was still an hour to go).

4th call 2nd tech: Consulted with his supervisor for 4-5 minutes then came back and asked me how old the PC was. I replied "4-5 years"

He then asked me the model. "HP Pavilion P6120f". Checked with his supervisors for another 3-4 minutes, then came back and said, "Your PC is not COMPATIBLE with Windows 10". Seeing that I was at a dead end, I terminated the call, but then I thought back. Windows 10 practically FORCED me to upgrade from Windows 7. It nagged me constantly to upgrade and it had been working fine on Windows 10 for over 2.5 years.

Once I had figured out the procedure to recover the working build, I called Microsoft to report it so that others could get their PC's fixed.

5th call 3rd tech: Could not understand that I was reporting a successful recovery. Wanted to know what the problem was. I am sure she just took down the basic procedure to humor me. Wouldn't let me talk to anyone in the next support tier.

I'm glad we have this arena to share information.
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-31T17:44:41+00:00

I am curious, have any you heard of the CMDLine Utility "DISKPART.exe"? A command in DISKPART >> List Vol(one exits DISKPART with the command 'Exit')?

In any CMDLINe(online, offline in WinRE or WINPE) try DISKPART /?

This haphazard pocking with "Dir" is unhelpful, IMHO.

Best Regards,

Crysta
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-31T17:57:56+00:00

Good point on version of repair disk. Used an original OEM Win10pro load disk. Not sure a 1709 version even exists. Must determine how to create a 1709 recovery disk and try on the next PC that goes to the BSOD. Thanks for the info.
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-31T18:15:35+00:00

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

Go there and create recovery media based on 1709 now.
Was this answer helpful?

0 comments No comments