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-15T21:36:16+00:00

My take on this issue is that the problem is either the update or the process that installs the update. It is apparent that during the installation something goes wrong; however, if the PC is reset and the update is applied again, everything works fine. It doesn't seem like there is a compatibility issue with specific programs or hardware. I think the actual install of the update is the problem.

I have not seen anyone say that the Command Prompt options work or fix the issue. For most of us (maybe all), the computer is hard broke and needs a Restore or Reset. So in that mindset the BCD comment is interesting, but not directly applicable to the problem.
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-15T21:30:26+00:00

Hi,

I think my second point would still be valid...

I am assuming that most of those with this issue are running the new Fall Creator's Update...

I would imagine that the internal "Windows Recovery" has the same glitch as the Installation Media..

As mentioned, the RebuildBCD command initially identified the OS, but when selecting "Yes" or "All" for the repair, then claimed that no OS was found...

Even a download of a "Questionable" ISO of a previous Windows 10 build may solve the problem... Just don't install it...
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-15T21:18:11+00:00
Hi,

I just wanted to point out an important issue when using the command prompt and FixBoot type commands...

You need to boot with the correct media type... If the machine is Legacy Bios you would select Optical Drive, for instance... If the machine is using UEFI Bios you would need to select "UEFI Optical Drive"... Same with a Flash Drive...

Another important issue... the new Fall Creator's Update 16299.15 (1709) seems to have a bug in which some of the FixBoot commands have bugs...

This was driving me nuts trying to figure out why

BOOTREC /REBUILDBCD would identify a OS, but then claim no OS found after selecting it to fix...

Booting with build 15063 installation media and selecting Repair resolved the problem and the Inaccessible Boot Device error was repaired the first try...

I'm including the command sequence I use in case anyone wants to know...

Click "Repair your computer" on the lower left of the "Install" screen....

Click the "Troubleshoot" or "Advanced" depending upon which appears...

Select "Command Prompt". (Capital letters not necessary)

Type BOOTREC /FIXMBR, and then press ENTER.

Type BOOTREC /FIXBOOT, and then press ENTER.

Type BOOTREC /REBUILDBCD, and then press ENTER.

NOTE... If you have multiple HDDs\SSDs, it would be best to unhook all except for the OS drive..
Most of us who are having this issue do not have to boot from external media, so the correct BIOS/UEFI method is already in place. After one or two failed boot attempts, Windows Recovery is automatically invoked and it attempts to repair the partition, probably using the same commands listed above, and failing to repair the problem about 99% of the time. Personally, I would try chkdsk c: /f first followed by System Restore if available before attempting these bootrec fixes.

What's both distressing and aggravating is that Windows Recovery can see the C drive with no problem whatsoever, so it has the correct drivers and configuration to mount the "inaccessible" boot drive. Why then can't this data be used to correct the problem on the boot drive or its registry?
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-15T20:48:24+00:00
Hi,

I just wanted to point out an important issue when using the command prompt and FixBoot type commands...

You need to boot with the correct media type... If the machine is Legacy Bios you would select Optical Drive, for instance... If the machine is using UEFI Bios you would need to select "UEFI Optical Drive"... Same with a Flash Drive...

Another important issue... the new Fall Creator's Update 16299.15 (1709) seems to have a bug in which some of the FixBoot commands have bugs...

This was driving me nuts trying to figure out why

BOOTREC /REBUILDBCD would identify a OS, but then claim no OS found after selecting it to fix...

Booting with build 15063 installation media and selecting Repair resolved the problem and the Inaccessible Boot Device error was repaired the first try...

I'm including the command sequence I use in case anyone wants to know...
1. Click "Repair your computer" on the lower left of the "Install" screen....
2. Click the "Troubleshoot" or "Advanced" depending upon which appears...
3. Select "Command Prompt". (Capital letters not necessary)
4. Type BOOTREC /FIXMBR, and then press ENTER.
5. Type BOOTREC /FIXBOOT, and then press ENTER.
6. Type BOOTREC /REBUILDBCD, and then press ENTER.
NOTE... If you have multiple HDDs\SSDs, it would be best to unhook all except for the OS drive..
Was this answer helpful?

0 comments No comments