Inaccessible Boot Device error in Windows 10

Does anyone here also have Vipre EndPoint Security or Vipre Business Premium that is consistent with all the machines they are having problems with? Still looking for patterns.... I manage about 1500 PCs and have had about 30 go down so far. Today for the first time, I had a machine go down for the SECOND TIME with this problem. A week ago, and then again today, SO, the bad update HAS NOT BEEN TAKEN DOWN BY MICROSOFT!

I tried installing a MSU package offline unfortunately it was on an AMD PC this morning that WENT DOWN due to MICROSOFTS UPDATE. AGAIN.....  Very Frustrating.  I used DSIM to take out the packages, however, then when it rebooted, still got the BSOD and had to eventually take out the hard drive, back up the data and do yet another restore that kept this user down 2-3 hours until It reinstalled everything again.  This is BAD.  This is the first AMD system that was affected and its NOT OLD.  Its less than a year old, Core I5, 8GB, etc.  I seen where on OLDER AMD there may have been a problem, but this just happened today.  Should I install the patch that is available on the other AMD systems to prevent this from happening?  They are brand new Lenovo Core I5, 8gb, SSD, etc.  Or just turn off updates and leave them.  I still have about 50 PCs on Windows10 Pro that have not rebooted and they are pending reboots.  Which package is bad?  What ID??  So i can go in and uninstall this update?  We cannot afford for PCs to keep dropping.

Some of them come back up after using DSIM from command prompt when you go into Troubleshooting and remove it, but I have now 3 pcs that have been affected by this that I could not just remove the package.  The BSOD still came up and had to do a restore with keeping user files, just had to reinstall office, etc again to get them going.  Just a lot of downtime.

Appreciate any feedback.

Thanks

IT Admin

there are half a dozen places with pending updates, pending deletions and pending xml and other stuff.

When I looked there were over 500 items in the pending renames and pending deletes.

It's a very complicated process.  Much easier to do a repair install after the first boot.

The repair install will kill all the pending stuff and replace all the bad files and/or registry updates with ones that work.  Since the update that caused the problem is no longer an issue, you should be fine.

Wiz

Your patch may work, haven't had the time to try it, but I believe that it may not work

In any event, disabling windows update is unnecessary.  The bad patch is gone.  It is not windows update that is causing the issue.

You may want to disable it anyway to prevent a crisis similar to this one, however, I believe that Microsoft has learned an important lesson about thoroughly testing it's patches prior to posting them.

However:

It's the fact that the 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 ones.

btw: The official Microsoft Windows 10 contains and ESD instead of a WIM.  DISM works equally well with WIM's or ESD's.

        I don't believe you need to convert them.

Wiz

What can we do if we received the "bad update" but have not done the first reboot to receive the BSOD. In other words. If windows is still up and running, can you simply uninstall the same updates that we are uninstalling with the DSIM method and not have to face the BSOD to begin with?

I am with Todd.  I have told customers to no reboot until a solution is available so most (and me) would be saved from the grief of new install if we can get the bad patch off before reboot.  My fear is that Microsoft will soon initiate one of their auto-reboot soon causing the senerio you describe and break any machines we have left. 

Again is there a procedure to ID the bad patch, delete it before it tries to load on a reboot?