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 No 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 No comments

506 additional answers

Sort by: Most helpful
  1. Anonymous
    2018-02-01T16:34:29+00:00

    Thank You wiz,

    Hopes this helps those with an HP!

    I do not, but it sounds very much like I would expect......

    I just happened to notice that he mentioned HP......

    Best Regards,

    Crysta

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-02-01T16:30:03+00:00

    FOR THOSE WHOM ARE WONDERING IF THE LATEST PATCHES HELP YOU?

    Born's Tech and Windows World

    Android, Linux, iOS, Windows, Gagdets and more Geek stuff

    Windows 10 V1709: Update KB4058258 and KB4074608

    Posted on2018-02-01byguenni

    [German]Microsoft released the cumulative update KB4058258 for Windows 10 Fall Creators Update on January 31, 2018. The stability update KB4074608 has also been released. And there are other updates. Here are some information about these updates.

    https://borncity.com/win/2018/02/01/windows-10-v1709-update-kb4058258-and-kb4074608/

    Best Regards,

    Crysta

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-02-01T07:44:23+00:00

    Thanks Crysta,

    I have recovery images on an external HD that is unplugged after each backup. When plugged in it will show them but stops when trying to load them & returns to

    I have new bootable ISO 1709 USB thumb drives made directly from the MS site yesterday. I also have a unused new copy of Windows 10 Pro. These all show up on my other comps fine & try to load. But will not even attempt to load on the bricked up comp with blue screen.

    Also inside of this drive X: I have several system backups that it won't identify now. I back the system up 2-3 times a week. There are no bad sectors on the internal HD & all files show no problems in scans.

    As soon as you turn on that comp it goes in to automatic repair mode then to blue "Choose an option" screen. None of the options or advanced options work except command prompt. The comp will not go past this point so I can't get a screen copy. In DiskPart I get a list of drives C - H, with 1 being the DVDRW & the rest being on 1 HD. I do not have multi drives hooked to that comp. The update formed my HD into 5 drives = 1 OS, 1 system, 1 HP recovery & 2 unknown small drives (4 unchangeable partitions now). Partition Magic or my repair disk couldn't even break them up.

    I know it sounds like it would be simple to load something, but it will only run my repair disk & Partition Magic which can make no changes to that system now. The HD is good, the backups are good, the USB ISO drive is good, the Win 10 updates caused a "Meltdown" of that comp.

    Thanks again.

    Do you have a Smartphone or Camera to take a reasonable HD ScreenShots(forgot to mention it as an option). At this point I am am not sure how much it will help but try anyway.

    How do you make these Recovery Images? For example I am using Paragon 2015, HDM 15, I load it into memory from an USB Drive as a Bootable. I access my Images which are on internal drives or on my Network through Paragon HDM in WinPE which is only running in memory.

    I am unfamiliar with a system that one just plobs a Drive ladened with OS Images on it, via USB and expect it to do something????

    I am not going to guess at all, with any of this, SPECIFICS, SPECIFICS, SPECIFICS.

    My Crystal Ball broke when I was born, and I have never got beyond FAILURE when it comes to mind reading.

    Have you tried one of your USB ISO drives that is 1709 and go into Troubleshoot or Repair? 

    I AM NOT ASKING YOU TO DO ANYTHING, JUST LOOK UP TO, BUT NOT INCLUDING IMPLEMENTATION. 

    It might give you a different view of your system. If you to not have any other Recovery system that will work, you might need to try a Repair. I just don't want you make things worse until you are ready to blow your bricked Image away.

    However, if you can get a working system again, Like you are used to, you still have your images that I do not understand at all but you seem to.

    I know I am sort of like slashing at the air, but we don't seem to have allot of choices......

    Best Regards,

    Crysta

    PS Update: How do you usually use that HP Recovery Partition?

    If you have a recent computer, you may have Secure boot set in BIOS.  This will prevent you from booting from an external device.

    If you just want to get your system bootable and recover from backup without regard to what is currently on the drive, the easiest way to do that is a system reset.

    after a couple of blue screens, the PC should go into startup repair.  select advance options and do the system reset.  You can then boot normally and it retains your latest data.  You can backup your latest data if you need it.  Then restore the drive from one of your backups.

    If you have a recent PC, it may be set to secure boot in the UEFI BIOS.  to boot from an external device, you will need to change that BIOS Option. 

    You will need to fail the boot and go into Advanced Recovery Options and  one of the options is to change UEFI options which will get you into BIOS.  Turn off secure boot to enable booting from an external device.

    The HP recovery partition will put you back to whatever version of windows that the system shipped with. depending on your model, you can get to it through F11 at the initial HP screen or if you have a UEFI BIOS you will need to turn off secure boot as described above. Once secure boot is off you will have more boot options and should be able to enter recovery mode.

    HP recovery will generally erase your drive and give you an old version of windows and all the original programs that the system shipped with. Then you will then need to upgrade with your flash drive. 

    wiz

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-02-01T01:50:54+00:00

    Thanks Crysta,

    I have recovery images on an external HD that is unplugged after each backup. When plugged in it will show them but stops when trying to load them & returns to

    I have new bootable ISO 1709 USB thumb drives made directly from the MS site yesterday. I also have a unused new copy of Windows 10 Pro. These all show up on my other comps fine & try to load. But will not even attempt to load on the bricked up comp with blue screen.

    Also inside of this drive X: I have several system backups that it won't identify now. I back the system up 2-3 times a week. There are no bad sectors on the internal HD & all files show no problems in scans.

    As soon as you turn on that comp it goes in to automatic repair mode then to blue "Choose an option" screen. None of the options or advanced options work except command prompt. The comp will not go past this point so I can't get a screen copy. In DiskPart I get a list of drives C - H, with 1 being the DVDRW & the rest being on 1 HD. I do not have multi drives hooked to that comp. The update formed my HD into 5 drives = 1 OS, 1 system, 1 HP recovery & 2 unknown small drives (4 unchangeable partitions now). Partition Magic or my repair disk couldn't even break them up.

    I know it sounds like it would be simple to load something, but it will only run my repair disk & Partition Magic which can make no changes to that system now. The HD is good, the backups are good, the USB ISO drive is good, the Win 10 updates caused a "Meltdown" of that comp.

    Thanks again.

    Do you have a Smartphone or Camera to take a reasonable HD ScreenShots(forgot to mention it as an option). At this point I am am not sure how much it will help but try anyway.

    How do you make these Recovery Images? For example I am using Paragon 2015, HDM 15, I load it into memory from an USB Drive as a Bootable. I access my Images which are on internal drives or on my Network through Paragon HDM in WinPE which is only running in memory.

    I am unfamiliar with a system that one just plobs a Drive ladened with OS Images on it, via USB and expect it to do something????

    I am not going to guess at all, with any of this, SPECIFICS, SPECIFICS, SPECIFICS.

    My Crystal Ball broke when I was born, and I have never got beyond FAILURE when it comes to mind reading.

    Have you tried one of your USB ISO drives that is 1709 and go into Troubleshoot or Repair? 

    I AM NOT ASKING YOU TO DO ANYTHING, JUST LOOK UP TO, BUT NOT INCLUDING IMPLEMENTATION. 

    It might give you a different view of your system. If you to not have any other Recovery system that will work, you might need to try a Repair. I just don't want you make things worse until you are ready to blow your bricked Image away.

    However, if you can get a working system again, Like you are used to, you still have your images that I do not understand at all but you seem to.

    I know I am sort of like slashing at the air, but we don't seem to have allot of choices......

    Best Regards,

    Crysta

    PS Update: How do you usually use that HP Recovery Partition?

    Was this answer helpful?

    0 comments No comments