
Whenever I was called out to work on a computer that was giving trouble I would usually find out it has Norton on it - that meant that I had to go through the lengthy process of convincing the user/owner, who did not know better, that Norton was doing them more harm than good. Reason being is that their system often became bogged down by Norton's incredible desire to 'take over' one's computer. What about you - are you a Norton fan? If you are... poor you
I am definitely not a Norton fan. I work with software for the pc and many times in the past we have had problems with Norton mistaking our install process as virus activity, or its virus engine causing havoc with our application. We run Norton AV at my company, and it is the most intrusive AV I have ever seen. Basically when its scan kicks off every week, the pc becomes a sluggish snail, and I just step away from it because it is useless to me. I installed Norton AV on my home pc at one time and had so many problems that I uninstalled it and went to AVG. The uninstall really didn't clean up much, and I ended up doing a lot of cleanup in the registry on my own. I am definitely an anti-Norton person!
I am absolutely a fan of Norton. I think they make the best antivirus product available. However, I do not suggest using their other products like their System Works. You are asking it to do too much and trouble is likely to arise. If you use just their antivirus product, I think you can't go wrong.
The trouble I see is that people don't keep the software updated. I mean the program itself, not just the virus definitions. I use Symantec Antivirus Corporate Edition at work. Symantec is the company that makes Norton. They use the Symantec name for their business products but have kept the better known name of Norton on their products aimed at the home market. I have absolutely no problems with the product.
Now, if you purchased a copy of Norton in 2000 and never bothered to update it because you don't want to spend the money and then compare it to a free version which has been updated recently, what do you expect? Of course there will be problems. If you compare the free version released in 2000 and also never updated, I wonder what the results would be. The problem with not updating the software program itself (I am not referring to the virus definition files) is that any antivirus sofware program must work well with all software on a PC. When you install new software that was written long after the antivirus program you are running was written, chances for conflict are good. Newer release are updated to "play nicely" with these newer software packages you are installing.
Also, if you are comparing a product like Norton System Works with a program that just does virus protection, you are bound to find problems with System Works that won't exist with the straight antivirus product. However, when comparing the latest release of Norton Antivirus ONLY to the latest release of any other antivirus program, I believe Norton will hold its own.
My experiences Tena, have been with the newer versions of the Norton AV product. Usually we wont hear about any issues, and then Norton releases a new version or an updated definition, and then we get a flood of calls. I wouldnt have a problem if someone was using an old out of date version of the product and hadnt upgraded it for a while. I would tell them to jump in a lake. But when they've upgraded to the best and brightest Symantec has to offer, and it is causing major problems with other programs, that is when I have a problem.
I wonder then how well it is configured on your network. I have no problems at all...ever. Or, are you supporting home users?
We are supporting business users, and from what I have seen it has nothing to do with configuration. Here is an example of a 'situation' with one of the products we support where Norton tinkered with the product's registry settings thus causing a function to change within our product. I can't provide a link as the document is for registered users only and requires a user id/password. It is from ibm.com.
QUOTE |
CWBRXD Starts Automatically after Installing Norton Utilities Problem Summary: CWBRXD starts automatically after installing Norton Utilities. Resolution: Customers have found that if they run the Norton Utilities registry repair function on the PC, upon reboot they will get the message, CWBAR1007 - CWBRXD has been started. Norton uncomments the Client Access Start Incoming Remote Command registry entry, causing CWBRXD to start automatically. To prevent CWBRXD from starting, the customer will need to run regedit and go to the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunServices. Look for Client Access Start Incoming Remote Command and insert ### at the beginning of the data field. The ### will comment out the entry preventing it from running. The other option is to reinstall Client Access to restore the default registry entries. |
I believe the problem with Norton is two fold:
1. It requires a knowledgable user to 'handle' software, installs, and what nots... and most users are not. They just use a computer because they have to (work, etc.)
2. Norton is trying to improve a defective, bugged operating system known as 'Windows'.
3. Norton tries to tell you what your computer should be doing rather than you - I do not think we have software that smart.
4. Norton plants itself everywhere on your computer - it does it to the point that it is virtually impossible to get it all out without extensive editing of the registry.
This is all based on the fact that the user may or may not have the latest.
I believe that many of the dislikes with Norton among many people is self inflicted. I myself love the Norton (Corporate) product line. Most of the issues thus far mentioned are flections upon products such as Norton SystemWorks and or Norton Utilities. Everyone must remember that these products are built to serve a certain purpose and not actually recommended to use on just any PC.
QUOTE (JB@Trinidad) |
system often became bogged down by Norton's incredible desire to 'take over' |