Hello mrmxyzptlk,
I trust that you followed and read the links in the Topic that I posted above. If so, you will realise that you are far from alone in this and like all the others quoted in those links, you are being frustratingly inconvenienced, for which I commiserate with you.
Please also read this Topic:
McAfee Conflict , in particular the comments from
Ai_Tak (who was helping you in your previous postings, here:
http://www.lavasoftsupport.com/index.php?showtopic=7018).
QUOTE
Ai_Tak Dec 14 2006, 06:23 PM
I find it to be very annoying of mcafee to still have this problem that they "fixed" but is causing problems. This artificial incompatibility with ad-aware they have created doesn't help my image of the mcafee company (which wasn't so great to begin with). One thing I can say, other anti-virus programs don't have this problem with ad-aware.
QUOTE
daved Dec 21 2006, 11:49 AM
My concerns are these:
1- Why didn't Ad-Aware delete this entry from the registry?
QUOTE
Ai_Tak Dec 22 2006, 03:22 PM
Bug in the uninstaller most likely, normally wouldn't cause a problem for re-installing ad-aware, no other program needs to look at that (except to cause artificial incompatibility).
And then there is the whole of
Ai_Tak's final post which I won't quote in full here but which is informative - as with the links that contained
regedit instructions in my post above, you could look to see if any of the items mentioned are present in your son's computer.
Yes, sometimes there are traces of a program left after uninstallation and it would appear that Ad-Aware SE may be leaving a registry entry. I have uninstalled plenty of programs that left behind whole folders of files, etc, let alone registry entries. This has never prevented me from installing a different program that performs the same or similar functions, immediately afterward.
This problem first appeared in June 2006, 8 months ago, with the release of an upgrade of McAfee's programs . Then in September 2006, McAfee issued a "patch" that was supposed to correct/stop this situation arising. Yet here we Ad-Aware volunteers are, 5 months later, still explaining the situation to posters caught up in the aftermath.
Regards,
Spike