Why did Microsoft re-offer the old .NET patches?

Right now it loks like you can work around the .NET patch installation problems by installing them (manually if you need to), then going into Windows Update and unchecking all of the patches so they aren’t offered again.

Microsoft should be drawn and quartered, but you’ve heard me say that before, eh?

When I get a definitive solution, I’ll let you know. In the meantime, I’ve been wondering why in the world MS is offering these old patches again. Ends up that Microsoft has issued “Minor Revisions” to the security bulletins. Usually, “Minor” means that you don’t have to re-apply the patch. This month, though, Auto Update is pushing the patches. Here’s what MS says:

********************************************************************
Title: Microsoft Security Bulletin Minor Revisions
Issued: May 22, 2012
********************************************************************

Summary
=======

The following bulletins have undergone a minor revision increment.

Please see the appropriate bulletin for more details.

* MS11-100 – Critical
* MS12-034 – Critical
* MS12-035 – Critical
* MS12-MAY

Bulletin Information:
=====================

* MS11-100 – Critical

Reason for Revision: V1.5 (May 22, 2012): Added entry to the update FAQ to announce a detection change for KB2656352 for Microsoft .NET Framework 2.0 Service Pack 2 to correct an installation issue. This is a detection change only. There were no changes to the security update files. Customers who have already successfully updated their systems do not need to take any action.

– Originally posted: December 29, 2011
– Updated: May 22, 2012
– Bulletin Severity Rating: Critical
– Version: 1.5

* MS12-034 – Critical

Reason for Revision: V1.2 (May 22, 2012): Added an entry to the Frequently Asked Questions (FAQ) Related to This Security Update section to explain this revision.

– Originally posted: May 8, 2012
– Updated: May 22, 2012
– Bulletin Severity Rating: Critical
– Version: 1.2

* MS12-035 – Critical

Reason for Revision: V2.1 (May 22, 2012): Added entry to the update FAQ to announce a detection change for KB2604092 for Microsoft .NET Framework 2.0 Service Pack 2 and KB2604110 for Microsoft .NET Framework 3.0 Service Pack 2 to correct an installation issue. This is a detection change only. There were no changes to the security update files. Customers who have already successfully updated their systems do not need to take any action.

– Originally posted: May 8, 2012
– Updated: May 22, 2012
– Bulletin Severity Rating: Critical
– Version: 2.1

Let me repeat, for emphasis: these patches were re-released on May 22. I have no idea why. The notification from Microsoft says that they are updates to the KB articles only. It sounds to me like somebody accidentally ran these down the automatic update chute when they shouldn’t have.