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-01-24T01:08:22+00:00

    Has anyone tried uninstalling anti virus or installing this update

    https://www.windowslatest.com/2018/01/18/direct-download-links-kb4073290-windows-10-build-16299-194/

    (which was released separate from Windows update, but geared towards AMD processors)?

    I would be interested to see if the update can help Intel processors too.

    My anti virus (PC Matic Pro) said a lot of people are having issues with non-Microsoft anti virus programs.

    Yes Bobby A/V as usual with Patching and sometimes D/L in General is problematic from False positive to striping out Bytes of software/files. If people are smart they will stick strictly to Windows/Defender/Essentials/EndPoint. The biggest problem are the deep hooks the A/V Engineer sink illicitly into the Kernel. Well Spectre is deep in the Kernel too.

    Nope, kb4073290 is for Both Intel and AMD. There was first an x32 only Patch released. This is the counter part. I have installed it. For me it went fine but I have not had any of the problems you have. "They" it is supposed to calm these problems down????? Is the Patch in WU/MU now? It was only in the Catalog for a couple of days.

    Best Regards,

    Crysta

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-24T01:07:22+00:00

    I tried every solution in this thread to solve my issue with stuck in Win Pre install environment. Nothing worked. Could not even run dism. Booting from USB could not see any partition on the SSD.

    What I had to do eventually was do a clean install from USB. Had to download intel drivers to run so Windows install could see the partition. There were 2 partitions both 237 gigs on a 256 gig drive so obviously Windows corrupted the drive.

    This happened on a refurbished laptop with an older 1511 install. while Windows was doing an update to 1605?, Auto update pushed a 1709 update right over the update that was already running. no way to stop it and no error message until reboot did not work. 

    The clean install was fine since there was no personal files on the computer but I would have been very disturbed if this was a computer I had been using for some time.

    Microsoft needs to push updates less aggressively or this will happen again.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-24T00:36:17+00:00

    Has anyone tried uninstalling anti virus or installing this update

    https://www.windowslatest.com/2018/01/18/direct-download-links-kb4073290-windows-10-build-16299-194/

    (which was released separate from Windows update, but geared towards AMD processors)?

    I would be interested to see if the update can help Intel processors too.

    My anti virus (PC Matic Pro) said a lot of people are having issues with non-Microsoft anti virus programs.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-24T00:30:22+00:00

    Thank you Crysta,

    I actually devoted a couple hours yesterday just plowing through this entire thread from page 1 until here. It was strangely inspiring to see that people had the same problems as me, and everyone just working hard to fix it.

    The DISM method worked for me I think. I don't know what made this time special, but when I removed some Updates, Restored my System to a Point on January 10, it just worked.

    I have the Windows 10 Home and was worried I only have this one normal boot to enjoy (before the Updates install themselves again) and I thought "Heck it. I'll just try and reboot, have it install itself, and let it have it's own way." And if I get stuck on the same BSoD again, ah well. I would just reinstall and start freshly clean. New PC and all.

    Well, the I rebooted the PC and it did install the Updates.... Loading screens, a few restarts later, and I'm back inside my OS again. Normal.

    I restarted my machine just to make sure. It still loaded normal. I don't know how long this might last, maybe a few days, a couple hours, or maybe the next restart would do it, but it seems I can use it normally again... for now.

    That is good BUT ONE should NOT have to do a clean Install because of a Patch....... :(

    The only thing that I can come up with is said above, but what, on some PC's does/is something corrupted by the Patch OR is DISM?????

    If you personally want to be a WSUS Server of a Managed "Home" PC and control but keep your PC up to date. the KB is above to get you started. It is about "Automatic Updates". You do have RegEdit BUT not GPO. If you did this you would also need to learn how to control the System with Forced R/O permissions too. This is not for the faint of heart but might give you some solace while all these other machinations are gone through.

    Let me know......  however it is only a medium term solution.....

    Long term, is for these problems/corruption to be solved by Microsoft/Intel.

    Best Regards,

    Crysta

    Was this answer helpful?

    0 comments