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-06T14:09:21+00:00

    Also fixed my issue. How can we prevent this!!!!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-02-06T10:52:08+00:00
    1. I stopped windows update service as I will be making a snapshot of all drives before enabling any Microsoft updates. It will be me who decides when to start it. When a catastrophe like this occurs, it will only take the time to restore image on drives, no work in progress, angry users etc.
    2. The system will be clean after reboot as the repair from the wim (windows install image) restores the files. This is the only way to fix, simply it restores the system32/drivers files with the ones that were in the install disk and worked.
    3. Point 2 is only an assumption. I will try reboot over the weekend, I can't afford do it now.
    4. My dvd which is genuine Microsoft Windows 10 disk  contains .wim.  It is the only reason I used wim and I want to know about these "innovative formats" of Microsoft as little as possible to survive :)

    Good Luck!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-02-05T22:00:45+00:00

    Your patch may work, haven't had the time to try it, but I believe that it may not work

    In any event, disabling windows update is unnecessary.  The bad patch is gone.  It is not windows update that is causing the issue.

    You may want to disable it anyway to prevent a crisis similar to this one, however, I believe that Microsoft has learned an important lesson about thoroughly testing it's patches prior to posting them.

    However:

    It's the fact that the rollup fix is a two part process.  In installs the files that it can, then reboots and installs the files that were in use and couldn't be installed while windows is running.

    When people first installed the bad patch, the second part of the install process could not take place (because of the bluescreen).

    Once the bad package was removed from the image, you were able to boot, however you could not stop the second part of the bad patch from installing just prior to loading the first boot of windows.  That is the reason you only get one chance to boot.

    The patch that is now offered on windows update, does not cause blue screens.  you can install it, but here's what will happen.

    It will install the first half of the update. Then when it reboots it will bluescreen (,because the good second part of the patch has not yet replaced the files installed on the first successful boot).    You would need to have a successful second boot for the good files to finish replacing the bad ones.

    btw: The official Microsoft Windows 10 contains and ESD instead of a WIM.  DISM works equally well with WIM's or ESD's.

            I don't believe you need to convert them.

    Wiz

    What can we do if we received the "bad update" but have not done the first reboot to receive the BSOD. In other words. If windows is still up and running, can you simply uninstall the same updates that we are uninstalling with the DSIM method and not have to face the BSOD to begin with?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-05T20:58:26+00:00

    Your patch may work, haven't had the time to try it, but I believe that it may not work

    In any event, disabling windows update is unnecessary.  The bad patch is gone.  It is not windows update that is causing the issue.

    You may want to disable it anyway to prevent a crisis similar to this one, however, I believe that Microsoft has learned an important lesson about thoroughly testing it's patches prior to posting them.

    However:

    It's the fact that the rollup fix is a two part process.  In installs the files that it can, then reboots and installs the files that were in use and couldn't be installed while windows is running.

    When people first installed the bad patch, the second part of the install process could not take place (because of the bluescreen).

    Once the bad package was removed from the image, you were able to boot, however you could not stop the second part of the bad patch from installing just prior to loading the first boot of windows.  That is the reason you only get one chance to boot.

    The patch that is now offered on windows update, does not cause blue screens.  you can install it, but here's what will happen.

    It will install the first half of the update. Then when it reboots it will bluescreen (,because the good second part of the patch has not yet replaced the files installed on the first successful boot).    You would need to have a successful second boot for the good files to finish replacing the bad ones.

    btw: The official Microsoft Windows 10 contains and ESD instead of a WIM.  DISM works equally well with WIM's or ESD's.

            I don't believe you need to convert them.

    Wiz

    Was this answer helpful?

    0 comments