Declining WSUS botched updates and its effects on their replacements.
Posted on 2014-10-22
With regards to declining botched or messed up Microsoft updates in WSUS.
Say you have a botched Microsoft update that makes its way onto a few of your computers via automatic approvals or whatever, but doesn't manage to install on a few of your other computers. I have two questions relating to the effect declining that update has on future updates...
1. What happens to revised versions of that update, does Microsoft give it a new update number or does it keep the old one? IE, does my declining that particular update decline future improved or debugged version of that update?
2. Also, what are the effects of declining that update on the few computers that have already had that update installed? Is it uninstalled from the computers or does it remain on them, but cannot be installed on other computers?
Bonus question, lol. will there be issues that can occur if an improved update is released into an environment that has some computers with the botched update and others that do not. Like does the improved update try to re-write the messed up one, or does it uninstall it and re-install the new one (which would be better)?
I ask all these questions because a botched update managed to get installed on a few computers but not others. The update PRELIMINARY, doesn't appear to be all that bad. But I am wondering if I should decline it to stop it from getting to other computers, or if I should let it propagate out to all computers for consistencies sake and prevent any update patch revision "layering" inconsistency problems in future?