Bad Norton! Bad!
July 13, 2005 6:07 AM Subscribe
Bad Norton! Bad! Ever since my most recent LiveUpdate last Thursday, Norton Internet Security has been giving me some problems...
Since the LiveUpdate, any program that has had its permissions changed cannot access the internet (this includes Outlook, so I am unable to get my mail, and World Of Warcraft, which patched yesterday). Also ccApp.exe is hanging up on shutdown, so the machine is taking longer to shut down than it should. I can't find anything about these problems on Symantec's site. (Well, I did find something about the ccApp.exe problem, and their solution is "just leave it")
Is anyone else having this problem after the most recent patch, or had this kind of problem in the past? And if I can't find a solution, what's the easiest/safest way to roll-back and/or reinstall Norton?
Oh, and it's Win XP Prof running Norton Internet Security 2005.
Since the LiveUpdate, any program that has had its permissions changed cannot access the internet (this includes Outlook, so I am unable to get my mail, and World Of Warcraft, which patched yesterday). Also ccApp.exe is hanging up on shutdown, so the machine is taking longer to shut down than it should. I can't find anything about these problems on Symantec's site. (Well, I did find something about the ccApp.exe problem, and their solution is "just leave it")
Is anyone else having this problem after the most recent patch, or had this kind of problem in the past? And if I can't find a solution, what's the easiest/safest way to roll-back and/or reinstall Norton?
Oh, and it's Win XP Prof running Norton Internet Security 2005.
Response by poster: Kololo - If I run LiveUpdate now, it says everything is up to date, and I haven't changed the settings telling it to not update certain things.
posted by emptybowl at 7:06 AM on July 13, 2005
posted by emptybowl at 7:06 AM on July 13, 2005
Try using System Restore to go back to last Wednesday. If that works, you could try running LiveUpdate again, or wait for a newer update to come along, when hopefully it will be fixed.
posted by Boobus Tuber at 9:04 AM on July 13, 2005
posted by Boobus Tuber at 9:04 AM on July 13, 2005
Warning: Personal Opinion Follows.
Norton has always been, to some extent, crap. Norton Internet Security in particular is way too invasive, bloated, controlling, etc. Ditch it. Get you a quality software firewall, or better yet, a router, and a decent antivirus. I recommend AVG Free Edition, but check around; I hear good things about Nod32 (though it's not free). And use Firefox rather than IE.
posted by attercoppe at 9:33 AM on July 13, 2005
Norton has always been, to some extent, crap. Norton Internet Security in particular is way too invasive, bloated, controlling, etc. Ditch it. Get you a quality software firewall, or better yet, a router, and a decent antivirus. I recommend AVG Free Edition, but check around; I hear good things about Nod32 (though it's not free). And use Firefox rather than IE.
posted by attercoppe at 9:33 AM on July 13, 2005
I'd agree with attercoupe, I think AVG and either Zonealarm or Kerio is a far better and free solution. Kerio requires a bit more technical knowledge (which ports to block/allow), but either of them will work well.
posted by Boobus Tuber at 10:15 AM on July 13, 2005
posted by Boobus Tuber at 10:15 AM on July 13, 2005
**DISCLAIMER**: I work for Symantec QA, but not on this product: **DISCLAIMER**
I started having this exact problem about 3 weeks ago. A temporary workaround I found is to disable the firewall, or manually add a new rule for the program that can't see the network. (I'm at work right now, can't get to the interface to outline exactly how to go about creating a manual rule, but it's somewhere under the settings for "Personal Firewall" or the like).
Although this might sound like corporate shilling, I;'ve done competitive analyses of several other companies' firewall/AV products, and although pretty much all of them have a far better/less obnoxious interface, their core technologies are frequently not very good (AVG and ZoneAlarm in particular).
posted by DoomGerbil at 3:55 PM on July 13, 2005
I started having this exact problem about 3 weeks ago. A temporary workaround I found is to disable the firewall, or manually add a new rule for the program that can't see the network. (I'm at work right now, can't get to the interface to outline exactly how to go about creating a manual rule, but it's somewhere under the settings for "Personal Firewall" or the like).
Although this might sound like corporate shilling, I;'ve done competitive analyses of several other companies' firewall/AV products, and although pretty much all of them have a far better/less obnoxious interface, their core technologies are frequently not very good (AVG and ZoneAlarm in particular).
posted by DoomGerbil at 3:55 PM on July 13, 2005
This thread is closed to new comments.
posted by Kololo at 7:03 AM on July 13, 2005