Inaccessible Boot Device error in Windows 10

Anonymous
2018-01-09T16:46:16+00:00

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?*

Windows for home | Windows 10 | Performance and system failures

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
2018-01-17T17:16:49+00:00

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

Was this answer helpful?

30+ people found this answer helpful.
0 comments

506 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-01-20T17:59:25+00:00

    I know I have been all over the map with potential causes, but it seems that anti virus software is really causing a lot of problems for people. Symantec seems like a big culprit. We use PCmatic pro. It just seems suspicious that my entire office is starting to crash when the issue doesn't seem that widespread. If it was random and not a total worldwide crisis, we would only be seeing 10% failure or less.

    Thoughts?

    I have had two computers with the issue, both from the same location. One had PCmatic pro, the other did not. They use a cable provider. One was an i3 processor the other was AMD. While using DISM, I took the computers offline until i disabled  WU. Both are up and running. Hard to think in the box on this one.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-20T17:52:26+00:00

    Turns out it's not anything we are doing. It's Microsoft (again!) See https://www.theverge.com/2018/1/9/16867068/microsoft-meltdown-spectre-security-updates-amd-pcs-issues

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-20T17:50:19+00:00

    I know I have been all over the map with potential causes, but it seems that anti virus software is really causing a lot of problems for people. Symantec seems like a big culprit. We use PCmatic pro. It just seems suspicious that my entire office is starting to crash when the issue doesn't seem that widespread. If it was random and not a total worldwide crisis, we would only be seeing 10% failure or less.

    Thoughts?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-20T11:57:39+00:00

    Hit this issue a few days ago with my old i7 Gulftown hexacore based Windows 10 Pro PC running SEP x64 v14.01 RU1 (3752).  Initially fixed with a recent image restore, but the BSOD returned after applying all of the Windows / Office updates.  Tried again with the same result.  Finally, went back to a November image and reapplied all of the Windows / Office updates from then, which took a while and involved numerous reboots.  When it was finally back up to date, I noticed that just one of the updates has failed to install, namely KB89083 MSRT.  The PC now boots consistently without issue, with the same version of SEP.  Interestingly, subsequent runs of Windows Update do not attempt to re-install KB89083, so my conclusion is that it is MSRT that causes the issue, not any of the other Windows updates and not SEP.

    Do you mean to say it's a Microsoft update which caused the problem rather than a Windows update (specifically the one you mentioned)?  Regardless, it's still an update which happens automatically through Windows AU, so not sure what that distinction really gives.  Also, it's strange then how removing one of the other updates for people is what allowed them to boot back in the first place.  I'm not sure the failure of an update signifies anything deliberate, as if this were the problem, Microsoft would've just pulled it.  It's also not an update that's recently listed.  Could just be unrelated.

    Was this answer helpful?

    0 comments