The subject computer has XP Home Edition with Service Pack 3.

Starting a few months ago, every time Automatic Updates ran, the update to .NET framework 1.1 SP1 failed.  Multiple online troubleshooting sites recommended uninstalling NetFramework, then reinstalling it.

After about a zillion tries, I finally managed to uninstall NET Framework.

Now for the 24-dollar question:  Should I download and reinstall version 1.1, or install the latest version (4.0) instead?

Thanks in advance,

Jeff

Don't reinstall. That version (1.1) may change how you logon and is not easily undone.

Install 4.0 only if required by printer software or another app using .NET.

Personally, I believe .NET is responsible for most of Windows XP's performance issues.

Thanks for the quick response, Allyn.

I have downloaded the installation file and the service pack, but will not install either.

Is it safe to assume that if a program needs some version of NetFramework, it will display a notification when it does not find it on the computer?

Jeff

Generally, your presumption is correct. If needed, a printer driver suite will either install from its compressed archive or will download the required version.

Behind every good computer... is a jumble of wires 'n stuff.

I have encountered logon changes with two of the .NET versions with multiple Windows XP systems. A security update corrected that issue with version 2.0 as I recall.

When I installed 1.1 (offered by Windows Update for some reason to PCs with later versions) on a PC after installing later versions, the Windows logon appeared and prevented direct startup without logon and could not be changed in User Account settings. It's an inconvenience, not a major issue.

After my experience, I see no reason for anyone to install 1.1 unless specifically required for older software. Given that more recent printer drivers are using newer versions of .NET, installing 1.1 seems a waste of time.

That kind of sounds familiar, .NET &/or IE (from long ago)...

Try: control userpasswords2


Probably mentioned in here:

"Getting the log on screen at startup now and after being idle"
http://www.pcqanda.com/dc/dcboard.php?az=show_topic&forum=2&topic_id=430420

--------------------------------------
BANK OF AMERICA.COM ONLINE BANKING SUCKS IN THE HUGEST WAY IMAGINABLE

Newegg.com's new image gallery layout sucks in the hugest way imaginable too !
And now they're using JavaScript to "turn" pages to boot ! SUCKS

Good info link. I see TTech was there, too.

Oh, now I know what you were referring to. The way you worded it, "That version (1.1) may change how you logon and is not easily undone." sounded very ominous. It's an easy thing to delete the ASP.Net user account.

Behind every good computer... is a jumble of wires 'n stuff.

Net 1.0 used to add an ASP.net user which then required you to log on because now there was 2 users and as I recall 1.1 update corrected that.The 1.0 workaround was to uninstall asp.net user and then it would boot straight to the desktop again.I have never experienced any problems other than the extra user that was installed with 1.0 which M$ thought to add for developers coding with Net so they could do it without messing up their regular user account.This what I remember but it's been quite a while for installing updating XP.
Edit I guess I should read the links before commenting lol.

Might try:

"Microsoft .NET Framework Repair Tool"
http://www.microsoft.com/en-us/download/details.aspx?id=30135

".NET Framework Cleanup Tool User's Guide"
http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx


I would not install any .NET - unless, until its needed.
And unfortunately (IMO) it is used by a good bit of programs.

--------------------------------------
BANK OF AMERICA.COM ONLINE BANKING SUCKS IN THE HUGEST WAY IMAGINABLE

Newegg.com's new image gallery layout sucks in the hugest way imaginable too !
And now they're using JavaScript to "turn" pages to boot ! SUCKS