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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-01-15T21:30:26+00:00

    Hi,

    I think my second point would still be valid...

    I am assuming that most of those with this issue are running the new Fall Creator's Update...

    I would imagine that the internal "Windows Recovery" has the same glitch as the Installation Media..

    As mentioned, the RebuildBCD command initially identified the OS, but when selecting "Yes" or "All" for the repair, then claimed that no OS was found...

    Even a download of a "Questionable" ISO of a previous Windows 10 build may solve the problem... Just don't install it...

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-15T21:36:16+00:00

    My take on this issue is that the problem is either the update or the process that installs the update. It is apparent that during the installation something goes wrong; however, if the PC is reset and the update is applied again, everything works fine. It doesn't seem like there is a compatibility issue with specific programs or hardware. I think the actual install of the update is the problem.

    I have not seen anyone say that the Command Prompt options work or fix the issue. For most of us (maybe all), the computer is hard broke and needs a Restore or Reset. So in that mindset the BCD comment is interesting, but not directly applicable to the problem.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-15T21:39:46+00:00

    I have had multiple machines be restored only to have the issue happen again and again until updates were paused.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-15T22:46:13+00:00

    We just had another computer go.

    A restore point was created yesterday 1/14/18 by an update.

    The computer worked from 9 AM to 4:30 PM today before it crashed.

    We tried restoring from yesterday's restore point but it went into "the blue loop" or "the bloop" if you prefer...

    We're now trying a restore point from 1/11/18

    I'm not sure if an update ran today that was the cause.

    I'm not sure if there's a way of finding that out.

    We had some Symantec updates today but others in this thread use different AV, so this seems like a Microsoft/Intel issue.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments