Inaccessible Boot Device error in Windows 10

Thank you, thank you, thank you!

I had the same error and tried many other possible repair solutions from other sited.  I followed this and uninstalled the last package and my system is back alive and working again

in my case D was my drive

and I had to add a space in the ?Dism /Image:D:\  /Get-Packages"   command to get it to work  space between "\ /"

Thanks

Mike

The AMD that you refer to is the method of getting into 64 bit mode and 32 bit compatibility.  AMD released the  x86-64 instruction set in April 2003.  Intel originally tried something else with their Itanium processor released in 2001.  Now most everyone follows the AMD's x86-64 method.

So Intel  machines may need to remove a patch that says AMD on it just as well.  I just recovered another Intel Core i3 Laptop.

To repeat some of the earlier posts (which maybe some people didn't read), and

This applies ONLY to those who had January Updates that cause the Inaccessible Boot device message:

Do NOT fuss around with BCD fixes.  They are of no help here.

You probably don't need to a SFC or DISM /Check-Health either

In general, I will first outline the method.  Then I will show you exactly how to implement the fix.

Do the DISM Remove package command, try the reboot and see if you are now into windows.

If so, immediately perform an in-place upgrade of 1709.  That will fix the problem.

If you fail to do the in-place repair/upgrade you will most likely not get a second chance to reboot no matter how many packages you remove.

I used originally used Showster's method only to discover it was a one time shot.  Fortunately, I had imaged the drive on another machine and simply reimages and applied the patch.  If you can, remove the drive that won't boot and Image it to another drive before doing this.

Please Note:  For this problem (and only this problem) System Restore does NOT WORK! Even if you create a restore point on your first boot.

It's the fact that the original rollup fix is a two part process.  In installs the files that it can, then reboots and installs the files that were in use and couldn't be installed while windows is running.

When people first installed the bad patch, the second part of the install process could not take place (because of the bluescreen).

Once the bad package was removed from the image, you were able to boot, however you could not stop the second part of the bad patch from installing just prior to loading the first boot of windows.  That is the reason you only get one chance to boot.

The patch that is now offered on windows update, does not cause blue screens.  you can install it, but here's what will happen.

It will install the first half of the update. Then when it reboots it will bluescreen (,because the good second part of the patch has not yet replaced the files installed on the first successful boot).    You would need to have a successful second boot for the good files to finish replacing the bad one, and you won't get two boots.

The full details are in the next post:

Ok -- AMD is the first chip for MSFT to port the OS; Intel released the 64 bit Merced in 2003 which is way before Advanced Micro Devices was a smile on a gamer's face.  Thanks for the note as I'm hopeful the history lesson helps ;-)

AMD in this patch context refers to the 64bit platform, not the chip on the machine.

AMD is the one that first introduced 64bit platform.