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
    2019-05-23T20:42:08+00:00

    OK. Apologies if this is repetition, I hope you will forgive me for not wanting to wade through 50+ pages.

    I solved this problem by changing IDE to AHCI in BIOS. It is possible that the reverse might work too.

    Basically the CMOS battery had failed causing BIOS to revert to default for disk access mode (wrong). Check the CMOS battery if this works and if it's low on voltage replace it and set to the correct value again afterwards.

    Other BIOS settings may change because of this too.

    Tricky

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2018-03-18T00:18:32+00:00

    My laptop has been giving me assorted problems relating to updates for the last 18 months but they've gotten significantly worse in the last couple. (I did try to call microsoft support last year and, while friendly,  ultimately made things worse.) I tried following the instructions above even after trying chkdsk, scanbow, amd the auto repair amd refresh options but ran into a major problem: when I run the dism for d: drive, it says I don't gave access. But when I run it for c: (which I thnk is where my windows is) it says I need the latest version of the dism...which I can't get to because I can't boot! Any thoughts, insights, advice, etc. would be greatly appreciated.

    Cathy K

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2018-02-25T17:35:12+00:00

    Susan,

    I'm reposting this question with my original typo fixed.  Wondering if you have any advice for this case?

    "Any advice when a system is sitting at 1709 ver 16299.192 and has ALREADY DOWNLOADED KB4074588 (ver 16299.248) and is just waiting to restart to finish installing the update?  I would like to prevent the completion of the update with its possible death trap until Microsoft gives us a positive fix.

    Thanks,

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2018-01-12T17:07:35+00:00

    I will try DISM the next time it happens. I believe it is an issue with the latest security updates, but it is affecting all types of machines. Mostly older computers, but we run Intel processors primarily.

    Was this answer helpful?

    0 comments