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-29T04:28:00+00:00

It's a wonder why we haven't had one official response to resolve the main issue. Agreed Crysta, it will continue. Eventually, they won't be able to hide forever. Especially on an issue this wide spread.

Showster

hehehe I know it is NOT funny, BUT I never expect OFFICIAL RESPONSES! So if they come on occasion I might be presently surprised. Most of the time what they have to say no matter which Corp it is, is simply useless.....

We bought these balls of Bandaids and Plaster Casts one way or another, now we must make the best of it. For years now, I have advocated that each user must become their OWN IT/Network IT/Admin/InfoSec/DevOPS person for a PC/Workstation/Server farm(mine is more like a paddock under my TV) or it is going to cost you many more times than what one payed for the equipment in the first place. Some listen, Most do not. It has been that way since the early 70's for me on Main Frames. There is always some Reason/Some Obstetrical/Some Buffoonery OR mostly Some Blame Game so that they didn't have too. Then it was in an Engineering department, these people were professional, and it was no different then, then it has been these last couple of weeks on this thread.

I am not trying to point any figures, I just saying you and others are not unique and no different than people 45+ years ago and all the way through.....

Have a Great Evening, and Goodnight,

Best Regards,

Crysta

@Phantomofmobile
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-29T04:12:04+00:00

It's minor widespread, not major widespread is the problem.
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-29T04:02:25+00:00

It's a wonder why we haven't had one official response to resolve the main issue. Agreed Crysta, it will continue. Eventually, they won't be able to hide forever. Especially on an issue this wide spread.

Showster
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-29T03:50:37+00:00

Did Microsoft release the patch yet? The main fix? Please post it!

Showster

I am not sure there is going to be a "Main Fix" Showster. Microsoft has been dribbling Patches out in total silence over the last couple of days. Look at my feed backwards and you will see what I mean. I was having 'cookie' problems with Microsoft.com so I am slow with the one I posted here. Only Reason, allot of BSoD going on here.

Several of us are trying to keep up with each other and Microsoft's proceedings???? It is not easy.....

In the Catalog: "2018-01 Windows Update" you will see some but not all which I am tracking. WU/MU may or may not present even when it is suppose to.

My best suggest is one I made earlier:

Watch:

Patchmangement.org That is where you will witness Susan Bradley and others.....

On Twitter:

https://twitter.com/PhantomofMobile

https://twitter.com/woodyleonhard

https://twitter.com/rodtrent

Susan rarely Tweets. These folks, including myself are on Twitter mostly for Technical Reasons. Some are Professional Reporters. If you watch close enough, one can get to know some of the critical MS people in various disciplines BUT none of them are saying very much at all about Meltdown or Spectre.

It really only stands to reason. None of them whats their words to haunt them in a/several Court Cases

Take Care Showster. This is the beginning of a several year....something.....

Best Regards,

Crysta

@Phantomofmobile (A take on "Phantom of the Opera")
Was this answer helpful?

0 comments No comments