Good analysis article thanks for sharing it Brink :)
It didn't say anything about KB2973201 which came with some funky side effects or known issues when or soon after release ?
You have to wonder is this ordeal a learning experience for consumers and Microsoft or just consumers to review these updates and hold back weeks before installing them after the dust settles

God only knows how long the vulnerabilities existed in the first place and if a end users holds off a few weeks will the sky suddenly fall by not installing them anytime soon :/

All I can say looking at all the articles is "What a freakin' mess."

If you read the re-released security bulletin carefully, and specifically read the Update FAQ, you see that "Microsoft strongly recommends that customers who have not uninstalled the 2982791 update [the old update that was withdrawn] do so prior to applying the 2993651 update [the new, re-released update]." They don't say you must do this, just that they strongly recommend it.

What happens if you don't? They don't say. Why does the 2993651 update, or Windows Update, not remove the 2982791 update first? This is unclear. In fact, at the same time, Microsoft recommends relying on Automatic Updates which will install the new update without removing the old one and not inform the user of the fact.

Looks like I'll be sitting on the "patched patch" for a while longer. I normally wait until Saturday to download and install patches, which saved me this time from the ones that got pulled since I hadn't installed any until after the problem patches had been pulled by M$. However, the fixed one sounds like it's no better that the original one.

I have both 2982791 and 2993651 and so far no problems.
As of a few minutes ago checking again, I have all Windows 7 updates.
I really don't know what to do except leave things alone and wait.

So far I've installed the new patch on Win 7 32 without removing the old one & no problems (knock on wood). However I haven't re-patched Win 7 64 Pro or Win 8.1 Pro yet...I think I'm going to sit back a while & see what comes out of this next. Both 7 64 & 8.1 were running fine after the updates (once again, knock on wood). I opted for every OS not to install the update that added the Ruble sign (didn't see the point).

I'm with Jack no need to possibly create an issue following the contradictory processes in prior articles,
If the windows update system issued the Important updates and they loaded without bsod ?

I'd say we've done all we can as a end user is supposed to load Important updates as they're available or soon after,
It's up to Microsoft to straighten out the mess they've caused some users,

Then let those users figure out if trust is lost or not