03-28-2012 08:23 PM - edited 03-28-2012 08:37 PM
I am using Norton 360 6.0 on 4 different machines and ALL have had the issue of the "Symantec Framework has stopped working" when adding rules to the firewall.
I was getting tired of it on my desktop and tried something different since nothing else was working to and it appears that Norton is aware of the issue and does not seem inclined to make it a priority with a fix...
I removed 360 with the NRT, rebooted. Checked to see if any stray Norton folders were left. Reinstalled 360 from the trial page. Added ALL my firewall rules and have NOT rebooted yet. I added at least 100 rules, some blocking, some allow and some automatic.
It just finished Liveupdate and wants to reboot. I tried to add one more rule before I reboot and it crashed.
So, I guess the "trick" is to add ALL the rules you want to prior to letting it update and reboot your machine and hope they stick after the reboot.
The rules stayed after a reboot, the crashing remains when adding new rules.
Please forgive the double post. No idea why that happened.
04-05-2012 12:21 PM
Sorry for the inconvenience. We are working to get a solution as soon as possible.
Thanks,
HarryP
04-21-2012 03:16 AM
Hello Harry! Do you have any news for us regarding the problem" "Symantec Service Framework has stopped working"?
More details here: http://community.norton.com/t5/Norton-360/Symantec
And here: http://community.norton.com/t5/Norton-360/fresh-Wi
And, it looks this issue first raised it's ugly head waaaaaaaaaaaaay back last fall NIS 2012, with details here: http://community.norton.com/t5/Norton-Internet-Sec
04-26-2012 10:51 AM
HarryP wrote:Sorry for the inconvenience. We are working to get a solution as soon as possible.
Thanks,
HarryP
Hello HarryP, 4 weeks since you let us know that a solution is being worked on for this issue. Is there any progress on said soultion?
04-26-2012 11:17 AM
Hi BullSpit,
Please see Tim Lopez' latest updates, posted today:
04-26-2012 02:32 PM - edited 04-26-2012 02:43 PM
SendOfJive wrote:Hi BullSpit,
Please see Tim Lopez' latest updates, posted today:
Thank you for those links. I guess they did not see fit to let us know here in the 360 forum.
With these occasional posts addressing the problem, I just hope that they are not making attempts to pacify us that are having this issue. At this point in time and as long as it has been occurring and since it was first reported about 6 months ago, it makes me feel like they are.
