03-22-2012 04:25 PM
I'm following up with the engineering team and will continue to check the status of the fix to ensure that this gets addressed. I'm sorry that I can't provide any ETA for a fix at this time, but if a moment comes where I can, I most certainly will.
03-23-2012 03:22 PM
Thought I'd add one more name to the list. I saw that some people were receiving the error when clicking "Configure." Norton lets me go so far as selecting the .exe. Once I've selected, it shows me the drop-down box to Block, Allow or Manually Configure for about three seconds, and then it crashes. Virus protection seems to continue working, as Windows 7 complains immediately if I disable Norton for any reason, and it hasn't come up with an error. The Program Rules definitely stop working because once it quit, seven of the programs I blocked immediately started harassing me about their updates.
I have been with Norton for years, but last year I decided to piggyback on my husband's Kaspersky account. After about two weeks, I renewed with Norton because of the firewall and program rules. Kaspersky has it, but their interface is ridiculous. I recently renewed Norton, this time for two years. When I set it up, I immediately added all my programs. I saw that someone had posted a "magic number" at which the firewall has problems, and that it is somewhere over 100. I only have about 20 programs in my rules, so it seems unlikely that is the problem. Mine has only been installed since March 8.
I have Windows 7 Professional 64-bit, Norton 360 version 220.127.116.11.
03-25-2012 04:58 PM
Soooo glad I stumbled across this thread. Got the popup offer to move to 2012 in 60 seconds and figured it was about time. So glad I didn't.
Count me in the group that is 'hands on' with their firewall rules. My Mom's PC is set to automatic, that works for her. But I develop and test software for a living and as a hobby. I just counted and I've got 161 rules. So that probably means I'd experience the problem being discussed here. One of the primary reasons I've not left for ZA is that custom rules remain an option since their inception in the early days.
I'm not about to try 2012 yet. One of the biggest pains in moving to the next release of NIS is loosing all the custom rules - so I usually wait until a holiday to pull the trigger.
We're likely in the minority and this is probably a use case that Symantec QA does not test - large lists of custom rules. We're such a minority that the much needed import/export will never come to fruition either.
It's unreal how reliable 2011 has been. It has literally never crashed nor stumbled when minor updates were pushed. I run a pretty harsh environment with around 150-175 processes active 24/7.
Although my 2012 license is partially going to waste, I am thankful that I was able to use it to keep 2011 going.
03-25-2012 07:22 PM
And the fact is that they have not put ANY SORT OF PRIORITY on this mess. Make me wonder. And makes me wish that there was something better. Oppps. Anything is better than something that does not work. About time to start discussing a Class Action with my Dad.
03-26-2012 05:12 PM
I just realized this is the board for NIS, not 360 (duh on my part), and that this has been going on since November. It was bad enough when I thought it had been going on for a month. I've only had this problem for a few days, as my first addition of program rules at the beginning of March worked fine, but I'm already sick of adjusting my workflow around Norton - a program that is supposed to work in the background. I received an update after my last post, and I just tried to update my rules, and it crashed as usual. This is ridiculous.
03-26-2012 05:24 PM - edited 03-26-2012 05:25 PM
IpWallaby, have a look here:
03-26-2012 05:31 PM
Yeah, I did a fresh install, too, and I have the latest updates. The people in that thread are experiencing the same as I am - no joy. I've been with Norton for years. Never thought I'd have to check the forums for a four-month-long, multiple program problem before renewing my subscription. No, stupidly I renewed for two years this time. At least I'm still within the money-back timeframe, but according to their site, that refund could take months to materialize, as well.