Re: Uninstall Norton Anti-everything 2006 ?

Al Dykes wrote:

I want to uninstall the AV that came with this Compaq; It's Norton AV 2006 with all the bells and whistles.

Does this uninstall cleanly? Is there a howto somewhere?

Al,

Five Methods for the Removal of Symantec/NAV/NIS

*** Method I ***

Jim Byrd, an MS MVP and frequent NG contributor, put this together:

(http://groups.google.com/group/microsoft.public.windowsxp.general/msg/3fdc095258ac1269?hl=en&;)
Short Version: (http://tinyurl.com/zn99z)

Note that Jim is not a big fan of Registry Cleaners. This method did not work for me. Even after hours of searching through the Windows Registry keys, I could not find the keys that were interfering with several of my apps, most of which, BTW, were not even AV/PFW-related. Still if you have a few months to devote to using Regedit, ...

*** Method II ***

This method was put together by Don Pelotas at Kaspersky Labs.

(http://forum.kaspersky.com/index.php?showtopic=5233)

Although geared toward KPSS/KIS/KAV this is a proven method for the removal of NAV/NIS, at least to the point of being able to install another AV and/or PFW. This works in almost all cases. At this point, you would at least have AV/PFW protection, and could decide how much more clean-up is necessary or desired.

*** Method III ***

This is my method, and note that it is a work in progress, as one never really gets rid of a Symantec install. I have borrowed much of it from the first two methods. Also note that if you use other Symantec products (eg., Ghost), you will have to either be really careful or reinstall (recommended) after the removal of NIS/NAV.

1) If NAV is installed and running, it is recommended that you download all necessary tools/utilities for its removal, and then disconnect from your network (internet).

2) Backup your System, Registry, Data, etc. Goes without saying. Use Lars Hederer's ERUNT Utility (Jim Byrd concurs with this).

(http://www.larshederer.homepage.t-online.de/erunt/)

3) If NIS/NAV is installed, from the taskbar icon/GUI, note the version number, including build and anything else pertinent. This is _really_ important, particularly if the only copy of your OS is on an OEM restore disk. The inept Norton removal tools are not sophisticated enough to determine which version has been installed. If you don't know, you cannot run the correct tool, and Symantec makes it clear --- Do NOT run this tool on any other version. (Ed. Note: This kind of thing happens when your company is run by the Marketing Division, and not the Engineering Division.) Kill the NIS/NAV tasks.

4) Start -> Control Panel -> Add/Remove Programs -> Uninstall NIS/NAV.

5) If you did step 1, run the Norton removal tools.

(http://service1.symantec.com/SUPPORT/tsgeninfo.nsf/docid/2005033108162039?Open&src=&docid=2004093015165236&nsf=tsgeninfo.nsf&view=docid&dtype=&prod=&ver=&osv=&osv_lvl=)
Short Version: (http://tinyurl.com/4kave)

(http://service1.symantec.com/SUPPORT/nav.nsf/docid/2001092114452606)
Short Version: (http://tinyurl.com/12s3)

6) Install and run CCleaner (watch the Yahoo Toolbar) - free for Personal Use, read the EULA. Clean up the System, Advanced, and the Registry and File Integrity Issues keys.

(http://www.ccleaner.com/download/builds.aspx)

7) Install and run Reg Seeker - free for Personal Use, read the EULA. Select all and delete both red and green items.

(http://www.hoverdesk.net/freeware.htm)

8) Install the jv16 PowerTools 2006 from Macecraft - 30 day free evaluation period.

(http://www.macecraft.com/)

Run:

a) jv16 Registry Cleaner
b) RegSupreme Registry Cleaner
c) RegSupreme Pro Registry Cleaner
d) jv16 Registry Finder

Run the Registry Cleaners in agressive mode (let the utility make a backup each time.) If you are squeamish about the agressive mode, reboot and check out all of your software after each Registry cleaning. Running all three is certainly overkill, but then that is what this method is all about.

Run the Registry Finder, and look for Symantec, Norton, NAV, NIS, etc. Not all of these will be Symantec keys, of course, but zap those that are.

9) Download, install and run Nir Sofer's Registry Scanner - free for Personal Use, read the EULA.

(http://www.nirsoft.net/utils/regscanner.html)

Again, look for Symantec, Norton, NAV, NIS, etc. Not all of these will be Symantec keys, of course, but zap those that are.

10) Download, install and run Nir Sofer's ActiveX Helper - free for Personal Use, read the EULA.

(http://www.nirsoft.net/utils/axhelper.html)

Again, look for Symantec, Norton, NAV, NIS, etc. Not all of these will be Symantec ActiveX components, of course, but disable/delete those that are.

11) Download and install Microsoft Windows Script containing Visual Basic Script Edition (VBScript.) JScript, Windows Script Components, Windows Script Host, and Windows Script Runtime Version.

(http://msdn.microsoft.com/library/default.asp?url=/downloads/list/webdev.asp)
Short Version: (http://tinyurl.com/7nn6)

Note that you may need IE/ActiveX/WGA for this. This is an _absolute_ must if NIS/NAV has been on your system, and you want anything that uses scripts (WMP, etc.) to work as advertised.

12) This fixes "Virtual Device Driver failed DLL initialization" errors:

(http://support.microsoft.com/kb/314452/EN-US/)

This caused me grief for over a year, and could not be resolved as long as one or more of the Symantec Registry keys that was installed would not allow the fix. This fixes many 16-bit error problems.

13) Re-boot, and install an AV app.

As I said, this method is a work in progress. To my knowledge, everything on my WinXP box that was malfunctioning due to the Symantec install has been resolved. But then again, I have said that before. Still, if you can read this, this method worked for me. And I have _never_ needed _any_ of my backups. Yet. [g]

*** Method IV ***

1) Fdisk, delete all partitions, reformat the HD.

(http://support.microsoft.com/kb/255867/EN-US/)

2) Use a disk-wiping utility.

3) Install a clean copy of the OS.

*** Method V ***

1) Purchase a new, virgin HD.

2) Install a clean copy of the OS.

*** Addendum ***

Method V may actually be the _only_ way to get rid of a Symantec install. Only time will tell. And, unfortunately, Methods IV and V may not be realistic solutions for those with the only copy of their OS being on an OEM restore disk.

BTW, the jv16 Registry Finder utility alone, in my case, was worth the purchase price of the jv16 PowerTools. It found and solved the 16-bit Symantec Registry key problem that had eluded me for over a year. Many of my Terabyte tools/utilities would not work without this fix.

Ron :)
.

Relevant Pages

  • Re: Last Norton Liveupdate Broke Firewall!
    ... assistance twice from live tech support, it has all been to no avail. ... reference to Symantec and Norton as I was advised by Symantec. ... running but the second I install the Symantec Redirector for the firewall ... Currently I've reinstalled Norton SystemWorks2003, ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: Last Norton Liveupdate Broke Firewall!
    ... assistance twice from live tech support, it has all been to no avail. ... reference to Symantec and Norton as I was advised by Symantec. ... running but the second I install the Symantec Redirector for the firewall ... Currently I've reinstalled Norton SystemWorks2003, ...
    (comp.security.firewalls)
  • Re: SymAddln message
    ... corrupted and if you uninstall Norton Program, still the registry entries are ... Symantec folders. ...
    (microsoft.public.windows.mediacenter)
  • Re: Thinking about buying Nortons AntiVirus
    ... Have been using Norton since Peter Norton wrote the product many, ... NAV has had problems, I don't deny that in its long history. ... not a single Symantec I have installed is ... tell you it's bothering the install process. ...
    (microsoft.public.windowsxp.general)
  • Re: fFrewall, Antivirus Installation Issues
    ... I tried to install a new version of Symantec, Norton Antivirus ... very effective but suggest *not* to use the 'Clean the Registry' option. ...
    (microsoft.public.windowsxp.general)