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-02T22:58:34+00:00

    For the record, with nothing having worked, interestingly enough when I restored the OS from an old backup and did all the updates, the issue didn't reoccur.  All the software (besides some settings and browser plug-ins here and there) was pretty much the same and all updated first.  It seems the issue has occurred for people that were the most up-to-date and then did the update.  It hasn't occurred, even when this issue originally started happening, on even the same computers with the same configuration on which a bunch of updates were all done at once, having for instance not turned the PC on in months.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-02-02T22:55:32+00:00

    I have a similar issue to everyone else in this thread- Updates automaticallly installed and PC stuck in bsod loop. Start up repair fails. Can't boot in safe mode. 

    PC is home built, running win 10 on an i7 4770k

    After finding your instructions, I succesfully removed package "Package_For_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9" last night and the computer booted as normal- hallelujah! 

    Turning the PC off and going to bed, it then installed package 16299.125.1.6 overnight! Today I'm back to square one.

    In the package list, I can 192.1.9 as install pending and 125.1.6 as installed. Running the remove package again does not work for either packages, instead returning error 0x800f082f DSIM failed. 

    Microsft support suggested I try using a bootable USB to run repair- this didnt work. Then they suggested using "dism /online /cleanup-image /restorehealth" with the USB. This failed as "dism does not support servicing windows pe with the /online option". Now they suggest the only option is to reset/ rebuild my PC, but I don't want to lose various software that I no longer have install media and/or keys for.

    Hoping the collective wisdom of the internet may have some more suggestions?

    Thanks in advance.

    EDIT: I've just found the post giving the registry updates to fix error 0x800f082f so thanks to whoever posted it! http://www.varidan.com.au/how-to-fix-the-dreaded-windows-error-0x800f082f/

    However can anyone help with the cmd entries to make this registry update?

    There isn't a solution to this unfortunately.  I went through this earlier in the thread and did everything possible.  That registry fix doesn't work.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-02-02T22:52:43+00:00

    EDIT: I've just found the post giving the registry updates to fix error 0x800f082f so thanks to whoever posted it! http://www.varidan.com.au/how-to-fix-the-dreaded-windows-error-0x800f082f/

    However can anyone help with the cmd entries to make this registry update?

    Sorry, just ran through those instructions and they didn't solve the issues.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-02-02T22:11:29+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

    I have a similar issue to everyone else in this thread- Updates automaticallly installed and PC stuck in bsod loop. Start up repair fails. Can't boot in safe mode. 

    PC is home built, running win 10 on an i7 4770k

    After finding your instructions, I succesfully removed package "Package_For_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9" last night and the computer booted as normal- hallelujah! 

    Turning the PC off and going to bed, it then installed package 16299.125.1.6 overnight! Today I'm back to square one.

    In the package list, I can 192.1.9 as install pending and 125.1.6 as installed. Running the remove package again does not work for either packages, instead returning error 0x800f082f DSIM failed. 

    Microsft support suggested I try using a bootable USB to run repair- this didnt work. Then they suggested using "dism /online /cleanup-image /restorehealth" with the USB. This failed as "dism does not support servicing windows pe with the /online option". Now they suggest the only option is to reset/ rebuild my PC, but I don't want to lose various software that I no longer have install media and/or keys for.

    Hoping the collective wisdom of the internet may have some more suggestions?

    Thanks in advance.

    EDIT: I've just found the post giving the registry updates to fix error 0x800f082f so thanks to whoever posted it! http://www.varidan.com.au/how-to-fix-the-dreaded-windows-error-0x800f082f/

    However can anyone help with the cmd entries to make this registry update?

    Was this answer helpful?

    0 comments No comments