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-02-16T22:01:59+00:00

    My apologies, it may have been the January update just now installing on two workgroup computers.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-02-16T21:48:41+00:00

    I actually never had this problem until the February update and now it's shown up on at least 2 older computers with Intel processors.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-02-16T19:49:53+00:00

    JoelITP,

    Use a metered connection. That works for me on Home! It stops updates.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-16T19:42:28+00:00

    Are you monitoring any Microsoft Moderated forums that are addressing this problem?  I find it hard to get back on the link Susan Bradley referenced.  It says, "Stay Tuned".  I don't usually use a consumer oriented produces like Feedback Hub to resolve problems like this.  I expect Microsoft to address this problem themselves and help to dealers that sell and support their products.  I have seen one time boot option starting to disappear and I have customers coming to work in the morning to computers with BSOD each day at a rate of at least two a day.  They have been instructed to not reboot so I know one of the updates MS is downloading is forcing a reboot.  I have tried to take proactive approach and run an "in place upgrade" on remaining pc that are not broke, (ie. shooting with a shotgun not a rifle) Very costly approach and today I find that after performing on 10 pc's one still got a BSOD the next morning.  Want to closely monitor Microsoft's solution but don't know the best place.

    Was this answer helpful?

    0 comments