I get the following message when checking for updates: Is this a problem with Net\Framework or what?

Could not load the latest version number.
Configuration system failed to initialize
Unrecognized configuration section system.serviceModel. (d:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Config\machine.config line 134)


Running version 3.3.1 pro. Machine info:

***** Machine **********************************************
Operating System: Microsoft Windows NT 5.1.2600 Service Pack 3 (5.1.2600.19660
Detected Version: WindowsXP / Server2003 (WindowsXP / Server2003)
x64 Process / System: False / False
Date/Time (UTC): 08/24/2011 11:37:19
Date/Time (Local): 08/24/2011 08:37:19
.NET Framework: 2.0.50727.3623
CurrentCulture: English (Canada) (en-CA ~ en)
CurrentUICulture: English (United States) (en-US ~ en)
Administrator: True
UAC Enabled: False
On Battery: False

***** DisplayFusion ************************************
Name: DisplayFusion Pro v3.3.1
Build Date: May 20, 2011 12:28
Pro: True

Thanks for the suggestion. Unfortunately it is easier said than done when it comes to reinstalling .NET 2.0.

Windows refused to let me:

Repair the installation.
Remove the installation.
Reinstall over the old one.

Of course, Windows update has also installed Vers 3.0 and 3.5 of .NET Framework. Who knows what effect that has had?

Went to the web to find that others (of course) have had similar problems. None of the fixes using files extracted from various installers etc. etc. have worked.

What idiocy! I've wasted 2 hours and have nothing to show for it. In future I guess I shall avoid any applications that rely on this trainwreck called .NET Framework.

{End mini rant}

After a couple of weeks of heartbreaking labour I managed to sort out the NetFrameWork boondoggle. I really can't say what exactly I did to make it work again, but it involved uninstalling and reinstalling several applications (including my accounting software - mission critical! and DisplayFusion) many times in differenct orders. FINALLY I was able to completely remove all versions of the dastardly NetFramework and start from stratch. Everything appears to be working now - my fingers are crossed.

So a bitter taste remains. Why did it get screwed up in the first place? Why is it so ridiculously difficult and opaque to remove stuff like this from Windows? My grade to the software developers that are responsible for this mess - F-MINUS.