Norton Toolbar / Norton Identity Safe

[jwseed]

I just started to have this problem after installing Norton's latest version back earlier this month (July of 2012). I've used it Norton 360 for years and never had a problem. Now my computer continues to crash, usually when I use Chrome, but at other times as well. 

When I disable the Confidential plug-in, everything works peachy (actually my computer runs faster than it ever has)  but then it automatically enables itself and I'm back to crashing all over again.

I notice that this all started years ago and it is apparantly not fixed yet. (Even though back in 2008 Norton said the problem has been "fixed".)  My patience is wearing thin, as everything I've tried that has been posted in this forum has not worked. I am days away from canceling my Norton subscription.

Norton, please help, or else I'll have to leave.

PS I've told Google the same thing.

[cphenson]

Hello - what is the status of a fix, if any, for this problem?  It has been making my life miserable for months until it suddenly occurred to me that the only other constant between 2 new laptops was a newly purchased Norton anti-virus program. Typing that into the search box produces hundreds if not thousands of examples linking Norton Confidential to chrome freeze.  Norton has clearly been aware of this problem for some time and just as clearly its a Norton problem not a Google one. So, is there a solution or not?  I have the latest updates for both chrome and firefox and norton.  Please do not ask me to go through a tedious recitation of when and how the problem occurs.  I've read it half a dozen times from other users in this forum in the last  thirty minutes.

I look forward to your reply..

[SendOfJive Norton Fighter]

---

jwseed wrote:

I notice that this all started years ago and it is apparantly not fixed yet. (Even though back in 2008 Norton said the problem has been "fixed".) 

---

How can that be?  The first public stable release of Chrome was on December 11, 2008 and Norton did not support the browser until the release of Norton Internet Security 2012.  The problem couldn't have existed prior to NIS 2012. and Chrome itself barely existed in 2008.

[bethy0543]

SendofJive:

Does it make any difference?

Why are you focused on that one thing?

If a person is having this problem for 2 years or for 10 years and is a paying Symantec subscriber, what difference does it make?

Does it make the problem not exist--or better yet, does it make Symantec not responsible?

[SendOfJive Norton Fighter]

Hi bethy0543,

I was responding to a post that included comments about this issue that were not, and could not be, true.  I think accuracy is important.  There is no insight to be gained from allowing misunderstandings about an issue to be perpetuated.  Whatever else you want to believe about this problem, it is definitely not four years old, which was the concern introduced in the post by the other user, not me.

[bethy0543]

Whether this problem has been ignored by Symantec for one year, two years, three years or four years makes no difference to me.

The fact is, that Symantec has chosen to ignore the problem, lie to thousands (if not millions) of their paying subscribers and chosen to not fix the problem.

You can quibble about and make an issue of the number of years (to try to negate the issue for yourself) all you want...but the issue is still in existence, and hurting so very many of us.  Symantec is hurting us.

Why????

You cannot answer this question.

Only those in control at Symantec can.

It would be nice if people would quit making ridiculous excuses for them, and allow them to take responsibility for their chosen actions, or chosen in-actions.

[SendOfJive Norton Fighter]

Everyone is entitled to his own opinion, but not his own facts.
                                                                 - Daniel Patrick Moynihan

[bethy0543]

Exactly.

The facts still remain that Symantec hasn't fixed this problem and yes, it has been going on for years.

I personally have been tortured by this since last August.

This is a fact, whether you want to believe it or not.

~Bethy

[SpeeyClip]

Yes, another Norton 2012 user having problems with Google Chrome crashing.  Google Chrome only crashes on my PC when I exit G-Mail displaying a window "Norton Confidential not responding".  I will give Norton "chat room" tech specialists an A for effort in that they have during two lengthy sessions taken control of my PC twice this month and reported that they had found the "bug" and that it was repaired and that I would not have the problem again.  In both cases the crash problem disappeared for a single day and then returned.  An A for effort and an F for completion of the "fix".  I mentioned during one of the Norton "chats" that there's a lot of buzz on the web about "Norton Confidential not responding" plus crash and apparently crashing Google Chrome.  I asked why they did not make a public statement on the problem and publish a "fix".  Response was that there are too many variables i.e. third party issues, etc.  Reality is that this is one dumb corporation.  Norton nearly lost the market several years ago because of a lame product and if they don't get their product working with Google Chrome it's gonna be more than my PC that crashes.    Spin will only sell for awhile.

[SpeeyClip]

The spin statement is not holding up.  Other IS products are not crashing Google Chrome.