Link to home
Start Free TrialLog in
Avatar of ConsJMEA

asked on

Windows update KB2633880, KB2572073, KB2518864 Microsoft.Net Framework keep repeating after successful install


My system information:  Windows XP Pro SP3

I recently have had Automatic Updates appear for Security Updates for Microsoft .NET Framework KB2633880, KB2572073, KB2518864

I click install updates and I watch them install successfully.  And then they come right back wanting to install again and again and again.

I have read this proposed solution but I want to know if there are an alternative solution without the need of uninstalling and reinstalling Microsoft .Net Framework.

Avatar of IanTh
Flag of United Kingdom of Great Britain and Northern Ireland image

what version of net framework have you got installed

have you checked for virus's
Avatar of Don
Flag of United States of America image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Try this:

net stop wuauserv
del /s /q C:\windows\softwaredistribution
net start wuauserv

recheck for updates
AGAIN, there is a detection flaw with these 3 updates...need to wait for revision
Avatar of ConsJMEA


by: dstewartjrPosted on 2012-05-22 at 08:56:07ID: 37997910
AGAIN, there is a detection flaw with these 3 updates...need to wait for revision

Thanks for your comment and I will wait for revision.
You may want to subscribe to for further discussion on this issue, among others.
I had this problem at home and on 5 machines at work I'm responsible for. I updated root certificates (maybe not necessary, but why not) and updated Java. Problem went away. I'm guessing this set of updates relies on the latest Java platform to log the installation.
Seriously doubt it, Microsoft and JAVA(Oracle) are 2 entirely different vendors...I would say it's more likely a reboot has taken place, since that's only thing that I've done and dont see it being re-offered.
From that article

Microsoft has not, at the time of writing, issued an official advisory we can detect. We've asked Microsoft for comment and will update the story again when we learn more. ®
I has waited and today the problem has gone away. It looks like Windows Update has solved some internal flaw. In this case the best solution was to do nothing.