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-13T15:07:15+00:00

    I ran into this issue last night. I did the dism fix to remove the most recent "amd64" package and got my PC up and running again. Yay!

    Unfortunately, I left it running, and it re-installed the same bad patch and rebooted automatically and now, as others have noted, the same fix won't work a second time (I tried removing some additional packages via dism, too - made no difference). 

    I don't think I have a Restore Point. Is my only option now to Reset?

    Unlike most reports, I was able to use the DISM fix twice and have been running fine ever since. The difference I think may be that I didn't know about the DISM fix to start with and tried a system restore before I did anything else (from the rescue environment). That didn't work actually, but then I went looking for other answers, found the DISM fix and was able to get back into Windows where the system reported that the restore had been successful. I then found two more packages which had appeared and removed those successfully too. I'm not sure it will help you at this point (sorry!), but maybe someone else.....

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-02-13T14:54:58+00:00

    I ran into this issue last night. I did the dism fix to remove the most recent "amd64" package and got my PC up and running again. Yay!

    Unfortunately, I left it running, and it re-installed the same bad patch and rebooted automatically and now, as others have noted, the same fix won't work a second time (I tried removing some additional packages via dism, too - made no difference). 

    I don't think I have a Restore Point. Is my only option now to Reset?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-02-13T00:10:55+00:00

    You can have dual boot on either MBR or GPT drives but the boot drive itself can only be one or the other.

    They are mutually exclusive.

    This happens if you install Windows on SSD drive, it will go with GPT partition table, and later overwrite the partiton table  by installing another OS with MBR partition table. The MBR partition table editor, e.g. fdisk, sfdisk, or cdisk does not know GPT, so it overwrite part of the GPT partition table, but would not clean the rest completely. Technically you will be fine using MBR, and the first copy of GPT will be readable and possibly  bootable too. It will not current though :)

    Presumably you want to install XP  and windows 10 on the same drive.

    You always need to install XP first.

    If it's windows Vista x64, 7 or 8, they can boot from a GPT partition

    For 32 bit versions of Vista, treat as if it were XP

    No way should you be trying to install XP or Vista x86 on a GPT formatted drive.

    Windows 7, 8, 10 will install GPT when your BIOS is set to UEFI  or Both UEFI and Legacy and not to Legacy Only.

    Set your BIOS to Legacy Only.  Clear all partitions, and when you install Windows to an SSD it will be MBR.

    If you already have windows 10 installed, and you need to find out what kind of drive partitioning scheme you have,

    See:

    http://www.thpc.info/how/gpt\_or\_mbr.html

    The right way to do this is to:  (detailed link below these generalized steps)

    1. Backup your data

    2, Set the machine to Legacy Only mode (MBR)

    1. Clear the drive of all partitions. (AN easy way is to pretend you are installing Win10 and do custom0

        then delete all the partitions.

    1. Install your Vista or XP System in a partition that leaves enough space for a windows 10 partition
    2. Then install windows 10 in the other partition.

    Details can be found here For XP and should work for Vista x86 as well:

    https://answers.microsoft.com/en-us/windows/forum/windows\_10-windows\_install-winpc/have-windows-10-wish-to-dual-boot-with-windows-xp/a949c0b6-88d9-4bdc-a0a2-e74fd9a5b0a3?auth=1

    If you already have windows 10 installed,  and you don't want to do the above procedure,

    Download virtual box from oracle, install it and create a virtual drive with XP or Vista x86 on it.

    For Windows Vista x64, Windows 7 or Windows 8 Dual Booting try this link:

    https://www.techadvisor.co.uk/how-to/windows/how-dual-boot-windows-7-or-8-with-windows-10-3633084/

    Hope this helps

    Wiz

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-12T18:40:58+00:00

    You can have dual boot on either MBR or GPT drives but the boot drive itself can only be one or the other.

    They are mutually exclusive.

    This happens if you install Windows on SSD drive, it will go with GPT partition table, and later overwrite the partiton table  by installing another OS with MBR partition table. The MBR partition table editor, e.g. fdisk, sfdisk, or cdisk does not know GPT, so it overwrite part of the GPT partition table, but would not clean the rest completely. Technically you will be fine using MBR, and the first copy of GPT will be readable and possibly  bootable too. It will not current though :)

    Was this answer helpful?

    0 comments