Broadband Tech > Security > Security > SP3 vs McAfee led to Norton disaster

SP3 vs McAfee led to Norton disaster

not a good idea to cross-post, because people can't follow threads in two separate forums...I read your thread in the ms forum, and it sounds like you need the NAV removal tool from Symantec...let me search over at Symantec site and I'll post back here...or should I post there? Tell me what to do, as it is confusing when you start two threads in separate forums, LOL. :)

reply to Kirby Smith
"How to install Norton AntiVirus 2002 in Safe mode", »service1.symantec.com/SUPPORT/na···06172206

"How to uninstall Norton AntiVirus by using the Rnav.exe removal utility", »makeashorterlink.com/?J19523D91

reply to Kirby Smith
McAfee is leaving stuff behind, that conflicts with NAV, I had a similar problem when I upgraded a W98 to XP all went well but McAfee 5.21.

It would not work right with XP, So I uninstalled McAfee and installed NAV, nothing but trouble, I had to go in the registry and remove everything that's related to McAfee, then did a search on my hard drive for McAfee stuff and removed it, rebooted, then NAV worked.
--
TrojanHunter Stands For Privacy!!!!!!!

reply to Kirby Smith
I use to have lockups with McAfee.

Ever since I switched to AVG (free) over a year ago, I've been a happy camper.

McAfee and Norton = Big, fat, buggy

AVG = Lean, tight, and free

Why is there any debate?

said by bigtuna:

---

AVG = Lean, tight, and free

---

said by bigtuna:

---

Why is there any debate?

---

reply to Kirby Smith

Caution McAfee Removal.

reply to Vampirefo

Re: SP3 vs McAfee led to Norton disaster

said by Vampirefo:

---

You get what you pay for, AVG is a good free AVP, FREE being the keyword here, But it's not as good as McAfee nor
NAV.

---

reply to Kirby Smith
Thanks everyone for your help. I'm at work at the moment and can't test your suggestions. If I get time tonight I'll see if they work and let you know.

Sorry about the cross posting, but I started with a SP3 report that evolved into an AV disaster.

kirby

reply to Kirby Smith

Well, now that my home's power has returned, I'll try some of the suggestions. (One might expect, if one were not a cynic, that the power company would put enough switches in their circuits that half a town wouldn't need to be blacked out to repair one pole taken out by an errant automobile.)

Vampirefo: No McAfee or Norton services are shown in manage/services. I must have killed enough program components during my morning flail to keep them from running. I will, though, try to clean them out more fully per the instructions above.

kirby

reply to Kirby Smith
For those following this epic, my late report is due to Norton Anti(?)Virus damaging my computer's access to the internet.

Following the advice above, I cleaned out every vestige of McAfee and Norton in the registry, other than some personal information that clearly didn't initiate any action. I then reinstalled Norton Antivirus 2002. Again, the BSOD problem occurred. The blue screens would occur without my actually doing anything with any of Norton's menus. Further, as each BSOD caused a reboot (I hadn't fixed SP3's default in that respect), the BSODs occurred sooner and sooner after login. Worse, and very bad manners, I noticed that my BIOS would take longer and longer to detect my RAID setup! OUTRAGEOUS!

Again, I had to go into safe mode to stop it and remove Norton. This gets very old very quickly.

The real disaster, however, wasn't apparent until I had finally cleaned Norton out again. My connection to the internet wouldn't work. More specifically, my access to my router wouldn't work. ipconfig/all showed no DNS entry, IP address, etc. Ipconfig /renew complained that there was an internal error and that I should pull the connection and /or reboot. These actions, of course, did nothing to fix it. I suspect Norton blasted my TCP stack, or maybe my BIOS, because running chkdisk and system file checker had no effect. I will probably have to re-image my C: and D: drives with Sunday morning's backup to get back to functionality. And if that doesn't work, re-installing my BIOS firmware is an even more tedious process.

Anyway, this does not encourage me to use Norton, to understate the obvious.

kirby

reply to Kirby Smith
Could be kirby..But I think you also have something else going on in that system..could be a trojan/worm..maybe hardware..but if it all goes away after you completely divorce yourself fron Norton..then You have you solution.

reply to Kirby Smith
My hardware configuration could well be a problem. I would doubt a trojan, though, as I run TDS-3 and Wormguard.

kirby

reply to Kirby Smith
Update: Attempting to restore a previous image from my tape drive within the existing Win2k program just led to a corrupted mess. I expect I will have to split my RAID 1, repair one hard-drive's C: partition, get the tape backup program (Onstream 1Safe) working on it, delete the "C:" partition contents on the other hard drive, restore to it, and then boot to the other disk. If that works, then remirror. Alternatively, if the previous doesn't work, I have yet another, non RAID drive formatted for operation on IDE1 running Win2k SP1 that I could re-install and use for this recovery process. I am hoping I can get to last Sunday morning's image and then try SP3 again after I've contacted McAfee.

What a pain in the keister.

Also, I have reviewed Norton's web site forum for like service issues. I was disappointed to find that few of the requests for help since SP3 came out have been answered, and no-one seems to have had a similar problem. I have not yet called McAfee's $$$ hot line to find out about fixing their glitch that started this, or maybe it was SP3 that should be blamed.

kirby

reply to Kirby Smith
Did you install SP3 from a disk or the Internet?

reply to Kirby Smith
MicroSoft CD that was delivered last week.

kas

reply to Kirby Smith
Thought so..was wondering Kirby if you had all your security stuff...you know McAfee and anything else running when you did the install....so many people do..and they have other things running in the startup when they do that SP3 install.

I think that is a risky thing to do.

reply to Kirby Smith
I would highly doubt that anything relating to SP#, NAV or mcafee messed with your bios.

reply to Kirby Smith
Name Game: I kill practically everything when installing major stuff. Both anti virus and anti trojan programs were killed. Ati MMC was killed. No applications were running other than Explorer. There could have been one or more unnecessary processes running. I didn't go through the process list looking for other things to kill, but will try to do so next time. Neither SP1 nor SP2 were seemingly bothered by running processes (not to be confused with applications, although I'm not sure why), nor did McAfee develop a defect after those installations.

mboy: your doubt is encouraging. I do wonder, though, why the time it took the Highpoint controller to report the RAID configuration to whatever part of the BIOS runs the monitor got longer and longer after each BSOD and reboot.

Let me take this opportunity to thank youall for the help so far, and to apologize in advance for likely future delays in my response to any further suggestions. For what I hope are obvious reasons, my access to the internet is very limited. I will be able to review this thread on Thursday, but l will not be able to try a serious attack on restoration until Friday. After Thursday PM internet access will not be available to me until I fix the problem, or Tuesday arrives.

kirby