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-22T20:43:00+00:00

    I did you suggestions and they did not work. I do thank you for the download link for the KB4073290 patch. Keep it simple.....and short. People might read what you post.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-22T20:39:02+00:00

    For 0x8000ffff, I tried:

    • Renaming ..\windows\winsxs\pending.xml
    • Renaming ..\windows\SoftwareDistribution
    • Renaming ..\windows\system32\Catroot2
    • Set both  "Exclusive" and "TotalSessionPhases" data to "0".
    • Mounted the Components registry file and removed some value(was mentioned in a Microsoft article, didn't archive the solution's steps).
    • Ran DISM's /scanhealth and /restorehealth commands(tried a second time choosing a 1709 version Windows 10 disk "install.esd" file as the source).
    • Ran chkdsk
    • Ran SFC

    Still getting 0x8000ffff when adding or removing packages using DISM. That computer is also getting the clean install treatment.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-22T20:36:37+00:00

    You can install the update with DISM /image: ?:\ /Add-Package /Packagename:?  command

    See my Post at the bottom of previous Page. Check those Registry Keys. To make it easier I suggest NirSoft "Registry Scanner" Some A/V see these types of tools as malware BECAUSE Bad People use them too.

    Have you been Running SFC and DISM/ RestoreHealth after you remove the Packages in WinRE or better yet WinPE, as well as CHKDSK /b /x(necessary in WinRE usually)?

    One must keep their Image Healthy.....

    I have put several dissertation up Thread on all of this stuff, I am not going to repeat it......

    Best Regards,

    Crysta

    Update: the above applies if you have problems with DISM....

    As for Installing a package with the Add-  command yes you can, but under these condition your mileage my very. Do your best to keep your Image Healthy.....

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-22T20:03:35+00:00

    Things I tried for each successful boot(had to keep restoring to a 1/11/18 point to get a single boot):

    • Disconnected network cable before boot and disabled Windows Update through services.msc
    • Removed 16299.98.1.20 and 16299.25.1.6 along with 16299.192.1.9 before successful boot.
    • Installed KB4073290 while in Windows.
    • Installed KB4073290 using DISM, which allowed a single boot as always.

    Now the working restore point was automatically removed, so I believe this computer is going to get the clean install treatment. I have another system I can't even remove 16299.192.1.9 from because DISM fails with 0x8000ffff no matter what package you are removing or adding. Remember when you used to be able to repair install Windows XP from outside of Windows? What doof(s) at Microsoft decided the only way to offer an repair install(i.e. in-place upgrade) should be from a booting copy of Windows?

    You can install the update with DISM /image: ?:\ /Add-Package /Packagename:?  comand

    Was this answer helpful?

    0 comments