---

EvilMishMash wrote:

 

To me it seems as if it took a complaint post on Facebook to get things rolling.  

 

---

Hello EvilMishMash,

Things have been rolling with this for a while. It wasn't any facebook posts that caused any movement. There's just not really an update to give, so I hadn't given one. I'm still going to honor my word to give everyone an update on the situation as soon as I have something to update with. I can definitely understand the frustration associated with this issue. Trust me, I'm probably the person most anxious to have this issue fixed. 

---

Tim_Lopez wrote:

---

EvilMishMash wrote:

 

To me it seems as if it took a complaint post on Facebook to get things rolling.  

 

---

Hello EvilMishMash,

 

Things have been rolling with this for a while. It wasn't any facebook posts that caused any movement. There's just not really an update to give, so I hadn't given one. I'm still going to honor my word to give everyone an update on the situation as soon as I have something to update with. I can definitely understand the frustration associated with this issue. Trust me, I'm probably the person most anxious to have this issue fixed. 

---

Rolling with this for going on 6 months.

Tim, thanks for making an appearence in the 360 thread(s) to let us know you had not forgotten us there.

I think I'm hallucinating. 

I just installed the 2013 beta on my test machine that had 2012 installed.  ALL OF THE PROGRAM RULES I HAD DEFINED ARE STILL THERE!

Now I was able to crash the framework in the way that we're all now familiar with.  BUT.  After dismissing the crash, the list of programs was displayed.  Now I can no longer crash it.  Today is day 1, I'll reboot and tinker some more. 

So, major kudo's for preserving my existing custom rules.  No extensive testing here because my rules were simple.  So I'm assuming any in depth customization is brought forward.  This really makes for a much easier upgrade path.

PLUS, I was a bit premature in announcing my ability to re-create the crash.  I was just impatient.  After starting over with a 2nd install/upgrade, I noticed significant network I/O when I clicked on Program Control.  The 1st time around I clicked around on other parts of NIS because I knew that would cause the crash and give me control back.  The 2nd time around I waited about 20 seconds and the window appeared.  Looks like they were checking 'trust' the first time around.  Now when I click on Program Control, the dialog appears instantly.

It still can not be resized though 

Hello,
I have the same problem. When I want to edit the firewall rules, Norton crashes.
Has this issue been fixed now?
If not, when will it be?
Thank you. 

They've been working on it a loooooong time.  This has been an issue for so long that many of us that have been with this topic feel we are owed an extension on the software that we paid our hard earned money for....

That we cannot use as it was intended.

Like that will ever happen.

Mark

"Hello,
I have the same problem. When I want to edit the firewall rules, Norton crashes.
Has this issue been fixed now?
If not, when will it be?
Thank you. "

I removed Adobe Shockwave Players (and it's many bundles are now gone) deleted  my IE8 browser and NIS 2012 crashed, this does not happen that often, I Do Not try and change NIS's firewall rules, I believe that would only cause a problem.....Best......Gorpy1

So if NIS opened a window that says:

"Let the FBI turn on my webcam."

"Recomended"

You'd let them....

"... I Do Not try and change NIS's firewall rules, I believe that would only cause a problem...."

Well if someone is that dumb that should sell their computer and buy an etch a sketch, If you know there could be a glitch why exploit it and if it is a problem with so many posts I'm sure Symnatec's people are working to correct it, They always have before.......Best..........Gorpy1

Hello rh,

It would be great if this could be discussed on the beta forums since it involes the beta.

Norton 360 7.0 / Norton Internet Security 2013 / Norton AntiVirus 2013 Public Beta - Norton Communit...

I just checked our internal defect tracking database and we're tracking this issue with both 2012 and 2013 separately. It hasn't been corrected in either yet, but 2013 still has a ways to go before it's released.