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-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
Anonymous

2018-01-23T05:41:30+00:00

Ah, that's smart. In my present case scenario, I have WinPE separately on a drive and only the native (upgraded) OS to the computer on hand. That being the case, would the DISM commands look like the following?

"DISM /Image:C: /WinDir:Windows /SysDriveDir:C:\ /Cleanup-Image"

In other words, both directories pointing to "C:" (or in my case, having checked with Diskpart, "D:")?

Thanks! :)

AH Yes! good ole List Vol in that thar DiskPart !!! :)

DISM /Image:C: /WinDir:Windows /SysDriveDir:C:\ /Cleanup-Image /?

That should give you a help with your next option/features but it also tests your approach.

Dave, You are certainly on the right track. Test, try things but be careful, unless it is an Image that you have a good solid backup of. If you make mistakes you can simply Recover the Image.

Dave, I am probably not telling you anything new, BUT we learn by doing! We learn more by mistakes than successes. I can't tell you how many Images I have screwed up learning. Not always on my Test partition neither. O.o RESTORE!, RESTORE! and try it again. Restore takes about 15-20 minutes, invaluable......

Take care, I am going to bed now, I will answer anything more in the morning.....

Crysta
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2018-01-23T05:02:11+00:00

"The /SysDriveDir option specifies the path to the location of the BootMgr files."

Wouldn't the path you want to reference there also be the C: partition (or whichever letter the OS is designated to) rather than WinPE?

Did I say it Ref WinPE, if so that would be a fau pau. However some 3rd party Recovery systems that have WinPE in them sometime embed themselves in the BCD and thus come up on the Boot Menu. I would NOT do that unless one has a separate System Recovery with centralized Boot Environment implementation on a partition(This the way I run). In my case it is called 'R' and is also where my WinRE files are, that way THEY ARE NOT on 'C'.

That is why one has "/SysDriveDir".

On 'R' I have Backup Images extra BCD backups that I can copy over if the active one gets corrupted, etc....... It is quit custom. Some OEM Companies build a Recovery partition and hide it. Sometimes they put the Boot files on it as well. Then one need a facility to unhide...

If this is not similar to your configuration and every thing is on 'C' than you don't need "/SysDriveDir".

Best Regards,

Crysta

Ah, that's smart. In my present case scenario, I have WinPE separately on a drive and only the native (upgraded) OS to the computer on hand. That being the case, would the DISM commands look like the following?

"DISM /Image:C: /WinDir:Windows /SysDriveDir:C:\ /Cleanup-Image"

In other words, both directories pointing to "C:" (or in my case, having checked with Diskpart, "D:")?

Thanks! :)
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-23T04:49:02+00:00

"The /SysDriveDir option specifies the path to the location of the BootMgr files."

Wouldn't the path you want to reference there also be the C: partition (or whichever letter the OS is designated to) rather than WinPE?

Did I say it Ref WinPE, if so that would be a fau pau. However some 3rd party Recovery systems that operate in WinPE, sometimes embed themselves in the BCD and thus come up on the Boot Menu. I would NOT do that unless one has a separate System Recovery with centralized Boot Environment implementation on a partition(This the way I run). In my case it is called 'R' and is also where my WinRE files are, that way THEY ARE NOT on 'C'.

That is why one has "/SysDriveDir".

On 'R' I have Backup Images extra BCD backups that I can copy over if the active one gets corrupted, etc....... It is quit custom. Some OEM Companies build a Recovery partition and hide it. Sometimes they put the Boot files on it as well. Then one need a facility to unhide...

If this is not similar to your configuration and every thing is on 'C' than you don't need "/SysDriveDir".

Best Regards,

Crysta

PS I just went back and looked at Page 12 and what I wrote there(is that where you were looking,Dave?). Were you also meaning doing this in WinPE? If so sometimes one needs to get a bit more specific than one usually has to, in WinPE to get results. In other words sometimes I have noticed that one needs to state the obvious.....
Was this answer helpful?

0 comments No comments