1. Why do you think that your problems are related to .Net?
2. What exactly are those problems?
3. What does "blocking" mean? Can you tell the error message?
The presence of .Net shouldn't harm as long as it isn't used. It's just a 'framework' that's needed by some applications, written in the .Net languages.
I have an iMac/WinXP-pro hybrid and it worked fine following the initial installation six months ago. Now, I am noticing the beginning of problems created by updates that do not even apply to me. (or at least, I think so)
I am referring to the .Net collection.
I use my free-standing computer mostly for Internet searching and word processing plus a few photos and emails. I am not a server, I hate gaming (yes! I do) and gadgets only appeal to me if they have a relevant application to my personal usage.
I discovered by searching the origin of some error messages I am now getting that they originate in the bundle of .Net software (2 to 3.5) that I did not know I had.
After researching the purpose for these updates, I feel that I have no use for them. I uninstalled 3.5 easily but uninstalling 2 & 2.5 was blocked by Windows. Before I take the e-scalpel and hack them out, I would like to know if there is another more humane method available and will it really "damage" my system if I uninstall, as the Win. message pretended?
Today I stopped a "Windows CardSpace hotfix". I did not know what it was but again, after research, I do not believe I need that either.
Could CNET create a reference list written in normal language of these weird & wonderful updates, to check against?
Thank you very much to all for your clear responses in the forums. They are a great help.