Inaccessible Boot Device error in Windows 10

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

This morning one of our older Intel-based PCs (G35 chipset) running W10 Pro unexpectedly got the BSOD after a reboot after 2 weeks of working properly. But in this case, I don't know what needed rebooting, my best guess is a Norton Security update.

I had created a manual System Restore point back on 1/15, but restoring to that point with Windows RE didn't fix the problem (it was the only restore point available). Using dism according to the above instructions did. I removed the rollup fix that was installed on 1/09. There was another security patch installed on 1/10, but I left that alone. After a successful reboot, I paused Windows Update, set another System Restore point, and then downloaded and installed KB4073291 (the x86 version of KB4073290) to ensure that the rollup I just removed wouldn't get reinstalled. So far, so good.

Thanks, this fix worked for me too! :) Why is Windows 10 so unstable!!

Ok, I'm done with this.  I simply restored from an old backup image I had of the disk.

DISM is effectively broken as half its functions fail.  I called Microsoft earlier, as I mentioned I would, and that was a terrible experience.  45 min waiting only to forcefully go through basic troubleshooting steps after which I was told to do a clean install and that a level 2 technician would tell me the same thing (in a nice foreign tone).  As I was effectively asking to be transferred anyway, either the call dropped or I was hung up on, but either way I didn't get a call back (even though my number was taken down in the beginning).  Not like it matters I guess; they wouldn't know s*** anyway.

Anyone getting the 0x8000ffff error after removing the update with DISM, getting in once, and then getting the BSOD again, you're pretty much screwed.

But don't forget we love ya for it ;)