Robert_Charlton - 12:10 am on May 23, 2012 (gmt 0)
More than I ever wanted to know.... this from notes as I was trying to sort it out. I think Microsoft is in process of issuing a fix, but I'm not sure.
From a long discussion, one of several, on the Microsoft Answers forum. This one started about a year ago, with a bunch of activity on the same problem in the past few days....
Why could update KB2518864 not be installed?
The problem has apparently been around, as one poster notes, "since the dawn of the .NET framework". Not all posters are discussing the same set of updates or precisely the same symptoms, but at the root they all appear to be the having variations of the same problem... that Windows Update/Microsoft Update on occasion prompts to install the same updates over and over, and other components in the update chain, including the MS Update site and Microsoft's FixIt scans, indicate no problems.
The canned post early on in the thread from the MS forum moderator, I should mention, gets called out by a poster who's been seeing this go on for a while....
The assessment is bogus....
...Now, when will Microsoft admit the problem and get around to fixing it?
The updates I'm having problems with are the most frequently mentioned recently, and they are KB2518864 and KB2572073 and KB2633880.
May 13, 2012
Those three (3) updates are superseded (replaced) by KB2604092; one dates from June 2011, another from October 2011 and another from February 2012.
There are two (2) possible explanations for this:
• .NET Framework 2 SP2 was installed sometime after 14 February 2012; or
• This problem actually started eleven (11) months ago.
Here's six pages of more up-to-date discussion...
Security updates KB2633880 & KB2633870 are not being installed or updated
If KB2604092 is installed and KB2518864, KB2572073 and/or KB2633880 are being offered again, run a manual check for updates shortly after 10:00 AM Pacific/1:00 PM Eastern (17:00 UTC) today and see if they're still being offered.
[Looks like MS is about to rerelease KB2604092 today.]
As the thread goes on, Microsoft continued to deny the problem even as it was also appearing that they were gradually becoming aware of it. I tried visiting the MS Update site several times and running their scan there, getting messages each time that I was completely updated. Eventually, one of these "took" and I haven't seen the shield for a while. Seems to be the consensus on the second thread.
This is why I feel it's probably not good to Update right away.