October 2011 .NET patches

[Glenn9999]

I install .NET patches and they claim they have run successfully. But, they keep showing up in Automatic Updates/Windows Updates. I've had this problem and tore down .NET and reinstalled it before, but I have to ask since it keeps happening every time they put out new updates...is there an easier way to fix this? If I recall, Microsoft put out a fixit with one set of the .NET patches (they never document what those do exactly), that I tried and didn't work. I don't see any documentation on this either...

Any way to solve this?

The current ones I'm having this on:

2011-10-11 Security Update for Microsoft .NET Framework 2.0 SP2 on Windows Server 2003 and Windows XP x86 (KB2572073)

Security Bulletin IDs: MS11-078

Listing of File URLs:

MSIPatchRegFix-x86 - msipatchregfix-x86_205e4dab26db6e7522b87929efc4e211e6f12a3e.exe (109 KB)

KB2572073-x86 -ndp20sp2-kb2572073-x86_4ad74bba2900758125d10ae429f99d9552b08df3.exe (11546 KB)

----------------------------------------------------------------

2011-10-11 Security Update for Microsoft .NET Framework 4 on XP, Server 2003, Vista, Windows 7, Server 2008 x86 (KB2572078)

Security Bulletin IDs: MS11-078

Listing of File URLs:

KB2572078-x86 - ndp40-kb2572078-x86_9ae8fe7992049bb05ffc296ec7679f1060b59481.exe (10962 KB)

----------------------------------------------------------------

[englishman]

I've got the same problem with KB25772073. Any solutions ?

[dencorso]

Many other .NET updates cause this type of errors for different users. The only prescribed solution is to remove and reinstall .NET fully, which is a tedious process and not always solves the issue (and sometimes it solves the issue for the updates originally giving that error, but causes other updates to give the same kind of error). The best and most harmless workaround is to access Windows Update manually and hide the problem updates. After doing that automatic updates will stop offering them again and again.

[Glenn9999]

Many other .NET updates cause this type of errors for different users. The only prescribed solution is to remove and reinstall .NET fully, which is a tedious process and not always solves the issue (and sometimes it solves the issue for the updates originally giving that error, but causes other updates to give the same kind of error). The best and most harmless workaround is to access Windows Update manually and hide the problem updates. After doing that automatic updates will stop offering them again and again.

I'm aware of this and done this, but I would have to think enough have had this problem that Microsoft has come up with something. On a related note, I get these MSIPATCHREGFIX.EXE files every once in a while with .NET patches. What do those do, do you need to run them, and how? I'm thinking that somehow it relates to some issue in .NET or they wouldn't be linked along with the patches.

For post #2: http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx

Edited October 13, 2011 by Glenn9999

[dencorso]

Obviously MS has decided to ignore the issue or has no good solution for it (I'd bet on the latter). I've done the remove-reinstall ballet a number of times, with variable success... and here is a place in which YMMV, for sure. In any case, when I can demonstrate the system has the problem updates installed and working (which is the usual case when automatic updates reports success in the first installation), I now hide the problem updates after the second offer and move on. The only advantage I see in performing the remove-reinstall ballet at least once, for XP, is to take the opportunity to get rid of .NET 1.1 in the process. And, BTW, I always run the Clean-Up utility, reboot, then further clean up the registry and delete some folders related to .NET that remain, then run the Clean-Up utility a second time and reboot again, before beginning the reinstall, leaving 1.0 and 1.1 out. This is my 2¢.

[MagicAndre1981]

try to repair the .net frameworks with control panel->Add/remove software and install the updates again.

[RaymondRT]

I have the same problem with KB2572073 and KB2572078

Update said both installed successfully but keep reappearing.

Uninstalled from Add/Remove Programs, and Update installed them successfully again.

Still kept reappearing.

Uninstalled from Add/Remove Programs again and downloaded them as stand-alone installers.

Again, they installed successfully but keep reappearing.

Windows Update History shows the successfully installed TWICE. Grrrrr

Deleted the "SoftwareDistribution" folder and tried again.

Both installed successfully but they STILL keep reappearing.

Finally, I went to Windows Update and checked the box "Don't show this update bla bla bla"

Peace at last...

[USIKPA]

I have a slight variation of this issue.

Having once learned the hardway that .NET Framework security updates are best to be installed separately, I downloaded KB2572078 via windows update first. Before I proceeded with the next update for NET Framework 4 this time around, I suddenly realized an event id 1103 in the event viewer.

".NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Tried to start a service that wasn't the latest version of CLR Optimization service. Will shutdown"

Now what? There seems to be a discussion on the web of the similar event, that dates back to 2010 and KB976569 installation issues, so I am not sure this is the same.

Would appreciate any clues how to deal with it.

[myselfidem]

Same trouble with last updates (7 updates) NET FRAMEWORKS !!!!! Installation always fails

But solved like this in my case:

- Removing all the Net Frameworks on my computer exept NET FRAMEWORK 1.1

- Installing Windows Installer 4.5 for Win XP (KB 942288-v3-x86.exe): (Choose the one you need)

http://www.microsoft.com/download/en/details.aspx?id=8483

- Downloading and installing NET FRAMEWORK 2 and langpack (French for me)

- Using Microsoft Update and all the updates was installed successfully!

More help:

http://blogs.msdn.co...ting-guide.aspx

Windows Installer error code: http://support.microsoft.com/kb/923100/en-us

Edited October 22, 2011 by myselfidem