Inaccessible Boot Device error in Windows 10

We run VIPRE Endpoint Security, however, after installing KB4058258 version .214, it seems like everything is running ok now.  I had to use DISM to remove the bad packages, but once done, rebooted and then installed the above KB4058258 package manually.  Windows updated, rebooted fine and just did a couple reboots to be sure and it was good.  Vipre has never seemed to be the problem.  As a test I have a PC without any ANTIVIRUS at all that I test with which is newer Core I5, 8GB, 256SSD and it also had the same BSOD problem for booting.  

Its definitely the packages microsoft released and it would seem there was a couple bad ones.  If I upgrade from version .125 to .214 then everything seems to be ok.  If I am at .192 or .188 those PCs FAILED!  I had to roll back to .125 after uninstalling the bad packages and then it worked ok.

Hopefully this helps you.

Thanks

Duane

It would seem that the newest patch upgrade of .214 is a working and viable solution.

What I had to do is follow the steps for the DISM uninstallation of the packages and make sure that .6 or .9 was taken off and then in some cases if that still did not work, I did a restore back to the most recent restore set.  Tried the uninstall of the most recent package again and then after this and getting booted into windows again, TURNED OFF UPDATES, PAUSED THEM and it IMMEDIATELY tried to reinstall the same BAD UPDATE again.  Once that was done, I MANUALLY installed the KB4058258 and then rebooted and it seemed to update fine.  Once back in windows, I rebooted again and once again JUST TO BE SURE.  It seems that if you can get from version .125 to .214 it will correct the issue.

I have tested this and updated 10 pcs now that had the BSOD happen for the "Inaccessible Boot Device".  This seems to have done the trick.

If people would post their results, I would appreciate it.

HOPEFULLY MICROSOFT SEES THIS and builds off their latest .214 KB4058258 version so the thousands of techs and computers that have been affected are safe from here on out.  This was a HARDSHIP on a lot of companies and it NEVER SHOULD HAVE HAPPENED!

Thanks all.

IT Admin

Duane

I followed the above and had a successful boot, however I restarted and got this again. Just like you mentioned.. this steps didn't work the second time. 

However, I was able to get in by restoring a restore point which for me was the day before this started. After the restore point was successful, I followed the above instructions AGAIN to boot up for the second time. With that said, I will not reboot until I can do the in place upgrade.

Backing up files now... 

Damn it Microsoft.. Test your **** please. We are losing hours and days of productivity due to these bad software updates.

As far as I can tell, if DISM won't get you to at least one boot, the only remaining option is a system reset.  This at least preserves the data and some settings.

As I have stated earlier, I have worked on one intel and 4 amd systems.  

The Intel would system restore from the recovery environment but still not boot.

One of the AMD systems just froze after the update rather than Inaccessible boot device. 

That one responded to a system restore.  I figured out which update caused the problem and then hid it.

The other 3 were AMD systems and required DISM to remove the patch and then got  the system to boot.

Since I had imaged the drive (using another machine), I was able to repeat the process after I discovered there would be no second boot.

The only way I could fix the problem was a repair install.

All the patches that caused problems have been fixed. 

I would assume that whoever green lighted the posting of the bad patches has either been fired or severely reprimanded.

I am sure that for the immediate term, you won't see this happening again.

wiz