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-19T15:51:34+00:00

Here is the incident number: 118011717482863We closed the case and they are going to refund my incident fee. He said the issue is different from the AMD one and that they are working on a fix that would be released 'soon'.

He recommended disabling Windows updates for the time being, i have opted to ask everyone not to restart and wait for the update to come. Then we can install, test on a few computers, and then let everyone install and restart.

Best solution so far is avoid the update, but if you get hit, dism remove package, and then don't restart again until the fix is released.

I removed the package last Friday and it restarted fine, but then while I was in the shower, I guess the update installed again and rebooted on its own, and now back to BSOD, but when I tried to remove the package again, I still got the BSOD. Very frustrating to have had removed it only to have my PC restarted. I should have kept an eye on it and disabled the updates but it was early in the troubleshooting of all of this.

I'll probably wait a bit to see what update comes out, but I won't be able to install it unless I can do it via a USB.

Maybe I'll just do a clean install but reallly don't want to.
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-19T13:42:42+00:00

Here is the incident number: 118011717482863We closed the case and they are going to refund my incident fee. He said the issue is different from the AMD one and that they are working on a fix that would be released 'soon'.

He recommended disabling Windows updates for the time being, i have opted to ask everyone not to restart and wait for the update to come. Then we can install, test on a few computers, and then let everyone install and restart.

Best solution so far is avoid the update, but if you get hit, dism remove package, and then don't restart again until the fix is released.
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-19T04:41:29+00:00

Let's get back to the main issue at hand. What is the resolution to the BSOD issue? Why are we dealing with this? Get a hot fix sent out and lets be done with it. Mean while I've moved on... Point is, make sure you back up your data, or just do a fresh reinstall because it's always going to FAIL when a Microsoft Package_For_RollupFix31bf3856ad364e35~amd64~~16299.192.1.9 windows update comes out. Thank you Microsoft for the support.

Showster
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-19T02:57:40+00:00

What Susan is talking about is called an In Place Update.

The important thing to remember is it is runs on a running, working Windows PC, everything yours is not doing. It will run in it's own WinPE and do a full UPGRADE. You will loose your installs and data ON THE OS DRIVE ONLY.

That is why I didn't suggest that way, otherwise known as a Clean Install.

If you noodle around in WinPE and on your other PC for doc, you may find away to rebuild your Registry/Config??????

Or loose everything on the OS partition.....

Best Regards,

Crysta
Was this answer helpful?

0 comments No comments