Norton Internet Security / Norton AntiVirus

[AstroMax]

>>> Now when I even so much as try to open up my firewall settings Nortonb crashes

Yes, it crashes but I think it is still working in background. Only interface is gone.

Until Norton fixes it (it's a bug for sure, not a feature...) I am also running Windows 7 firewall Control.

NORTON WAKE UP!

Fix it and stop suggesting to reinstall!

[gwm Contributor]

My laptop is not to the point of crashing this early yet---it crashes when I APPLY a rule.

This is from my desktop:

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    ccSvcHst.exe
  Application Version:    11.2.0.9
  Application Timestamp:    4ed5768a
  Fault Module Name:    SYMHTML.DLL
  Fault Module Version:    6.5.0.23
  Fault Module Timestamp:    4ee5934c
  Exception Code:    c0000005
  Exception Offset:    0012911d
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1033
  Additional Information 1:    0a9e
  Additional Information 2:    0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:    0a9e
  Additional Information 4:    0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

[Tim_Lopez Administrator]

All,

We're still trying to research this issue but are not able to reproduce this issue.

We need to get some technical information from users that are facing this issue. 

If ANY of you are having this issue and would allow us to work with you to gather the info needed to research this further, please send me a Private Message and we'll work with you. 

[jmason Regular Contributor]

Tim_Lopez:

I see you are still soliciting for more information.

Are the people in Norton even trying to produce a utility that will alow us to import/export the firewall rules or not?

If not, the way I see it, then this is going plainly nowhere. I will not be surprised if this is how Norton treats other software problems its customers have encountered and reported to the company. You just keep asking for more information. And you will never have enough of them unless you can reproduce the problems and be able to fix them. Until then, all our ships are dead in the water. Your engineers are trying to figure out what's wrong with the ship engine's design. And even if we keep begging you, you simply refuse to throw us a line to get us out of YOUR trap. You want to keep us on the faulty ships so you can continue to milk information out of our pains. Ultimately, you are more concerned about fixing YOUR ships than helping us. We are all waiting for something or more from each side. But the fact is, Norton has already profited from the broken products it has sold. That is how your customers would look at the situation.

[gwm Contributor]

You sure hit THAT nail on the head.

Just give me a utility so I can DOWNGRADE all my machines.

[elsewhere]

The request for a firewall rule import/export utility is essentially a product feature enhancement request and is not really relevant here.

Please re-read Tim's post; the 'allow us to gather some technical information' statement implies that they want to collect information directly from one of your machines that has the issue.

[Tim_Lopez Administrator]

Hello jmason,

While I understand your frustration, please know that we are serious about trying to resolve this issue. 

Since I last posted that I needed to work with someone to research this issue, no one has sent me a Private Message offering to let us research this with them. We can definitely get enough information, if someone would allow us to work with them. 

If you're having this issue still, we'd love to work with you and research this!

We need to be able to reproduce the issue so we can identify the issue and resolve it. If we can't reproduce the issue, then we have to rely on assistance with whoever is having the issue. 

The feature request to import/export rules is a separate discussion. While I understand how it would come in handy right now, the problem would still exist and still needs to be corrected. Developing such a feature and ensuring that the rules are forward compatible is something that would take a great effort or development as well as testing, and would have to be incorporated with a new product version. However, if we're able to work with someone who is having this issue, we can finally work towards getting this issue corrected which would resolve it for everyone to their satisfaction. 

The focus we have right now is getting this issue resolved for everyone that is having this issue, and then after that we can look in to ways to implement new features and such. 

The sooner someone comes forward and allows us to work with them, the sooner we can get all the info we need to locate the issue and correct it. 

Sorry again for your frustration. I assure you that we're taking this issue seriously and hope that someone will come forward and allow us to assist. 

[Tim_Lopez Administrator]

---

elsewhere wrote:

The request for a firewall rule import/export utility is essentially a product feature enhancement request and is not really relevant here.

Please re-read Tim's post; the 'allow us to gather some technical information' statement implies that they want to collect information directly from one of your machines that has the issue.

---

Thanks elsewhere - I've updated my post to make it a little more clear to that point. 

[jmason Regular Contributor]

elsewhere:

If you do not get our point, please do not put words in our mouth. I think I can speak for many of us here. We are NOT asking for a "product feature enhancement." We don't care if Norton incroporates the ability to import/export rules in the next release or product. We just want something like the Norton Removal Tool (NRT). I don't consider the NRT an "enhancement" but an independent utility program to facilitate complete uninstallation of Norton products. We want something like that, a small utility program that we can use to import/export firewall rules so we can isolate the cause of our problems with NIS 2012.

And please do not point out that something I said here is relevant or not, especially in a thread I started.


Tim_Lopez and the Technical Team:

I don't doubt you people are serious about fixing the problem, as I do the same with the engineers who are trying to find out what's wrong with the ship's engine in my analogy.

You yourself have admitted that nobody has contacted you to offer more information. Has it not been obvious to you that it is unlikely that you will be getting any more from us after all this time?

If you go over the stories in this thread, you could see that people, like me for instance, are even willing to install NIS 2012 twice, manually enter the 100+ rules, then upon failing twice, downgrade to NIS 2011 and enter the rules again in trying to make their systems work. We are willing to do those things but not give you any more information. Why? We may each have our reasons. It may simply be our personality or due the nature of our work. May I even suggest that some of our systems may be critical to national security; thus, secrecy is of utmost importance to us? You don't know. You will probably never know. What you know now, and the fact is, nobody is offering more of what you're asking for. It is unlikely that somebody will do so in the near future. You will have to start working on the problem with that precondition.

Can you keep your fingers crossed and hope that somebody will eventually change his/her mind and approach you later? Yes, you certainly can, but in the meantime, we the users are hurting from the stalemate. And, as I pointed out earlier, your company has already profited from all of us - however you and the technical team are putting things.