I know, I had 3 recurring updates... KB3021952, KB3032359 & KB3035131. Believe it or not I
suspect KB3033929 is "Patient Zero" in Micro$lop's latest batch of
botched updates. Reason? Call it a hunch:
Patch Tuesday: October's Rescinded 2949927 Gets Reissued as 3033929
Patch Tuesday: Is KB3033929 Causing Problems?
MS Update 3033929 Causing Reboot Loop
My latest Microsoft update problem
KB3033929 is a re-issue of the previously Issued-FUBAR-ed- Rescinded
KB2949927. KB3033929 is also quite ... busy superseding several previous updates including (but not limited to):
KB3009736, KB3004394, KB3001554, KB2847077.
But wait! There's more!
*[1]*The 3033929 update has affected binaries in common with the 3035131 update being released simultaneously viaMS15-025. Customers who download and install updates manually and who are planning to install both updates should install the 3035131 update before installing the 3033929 update.See the Advisory FAQ for more information.
But that's not all...
How is this update (3033929) related to the 3035131 update discussed in MS15-025?This update (3033929) shares affected binaries with the 3035131 update being released simultaneously viaMS15-025.This overlap necessitates that one update supersede the other and, in this case, advisory update 3033929 supersedes update 3035131.****Customers with automatic updating enabledshouldexperience no unusual installation behavior; [key word beingshould***] both updates*should install automatically and bothshould** ***appear in the list of installed updates. [mine didn't]*However, for customers who download and install updates manually, the order in which the updates are installed will determine the observed behavior as follows:
Scenario 1 (preferred): Customer first installs update 3035131 and then installs advisory update 3033929.
Result: Both updates should install normally and both updates should appear in the list of installed updates.
Scenario 2: Customer first installs advisory update 3033929 and then attempts to install update 3035131.
Result: The installer notifies the user that the 3035131 update is already installed on the system; and the 3035131 update is NOT added to the list of installed updates.
Wait, whut? this Super-Duper Update not only supersedes... a bunch of... previous updates, it supersedes it's "twin" KB3035131 born the same day?
No wonder Windows Update Cleanup is "confused"
Horrible, simply horrible.
Edit: Add bold to text