04-07-2012 04:54 AM - edited 04-07-2012 04:55 AM
I had this very same problem. I used the "contact" button and was able to get live chat. It took three times to get the proper solution but this is what we did.
You will need to Norton_Removal_Tool.exe and the latest NIS2012 files without Definitions. I am sure you can find them on their site. That is where the tech downloaded them from.
1. Find you key (there is a txt file that has your license key) It will not be deleted, but just in case you delete it by accident you should grab it now.
2. REBOOT into Safe Mode with Networking.
3. MANUALLY remove all Norton/Symantec files from Program Files, Common Files.
4. Run the Norton_Removal_Tool.exe and follow prompts.
5. Restart - Reboot Computer
6. Install the latest version without the defintions. Here is an example of the file
7. Let the new install look for issues to fix - do a quick scan.
8. When that is complete, go into your Program Control and set your rules.
It seems there was a corruption during an update at some point and when we use the removal tool it is NOT removing the faulty file. Manually removing this file is what needs to be done. Which file was it. I do not know.
So did it fix it? Personally I was very unsure that this fixed the issue (because I used the removal tool TWICE before manually uninstalling)--
To test to see if it worked I blocked 15 .exe files I did not want to access the net. I applied, and left the Program Control settings section. Went back to NIS, went to go back into my Program Control and BINGO I did not get the error and I was able to access my Program Controls. I added 50 more .exe files for giggles and applied, left. Went back and Program Control was working fine.
I was told there is no way to back up our Program Control Settings and in my opinion that is enough to make me want to leave Symantec after a decade. I made it very clear via Feedback that this is what NIS users want!
Due to my complaints I was graced with a 30 day extension to my subscription. I feel that anyone that has been waiting as long as I was waiting for the resolution--should also be graced. It truly caused me great delays and loss of my computing time-- it is a nice way to even the score :)
I am not saying this solution will work for everyone-- but it did work for me. Good Luck!
04-10-2012 03:58 AM
The only way it seems this will be fixed is if more users start a petition/complaints.
I for one need more than 100 -- AND I also want the option to save my Program Control settings.
This is helpful when there is a Program Update (not subscription update) and or when you must uninstall-reinstall the program.
Of course it would not work or be advisible to use a backup of your Program Control settings and then re-use them after a format because paths may not be teh same, but I feel confident that they can easily build a warning into the programming.
I (a customer for over 10 yrs) vote to have the option to back up my Program Control settings AND have over 100 rules.
I for one sign, seal and deliver my vote!
04-10-2012 06:52 AM
Somewhere in this thread they already said something to the effect "A cold day in Hot." to that one. Having a way to save security settings is a big deal it seems.
04-18-2012 04:16 AM
I'm running Vista with IS 2012. I've been getting the message "Sysmantec Service Framework Stopped Working and was closed" more and more. Run live update and the problem continues. Any suggestions?
04-18-2012 06:19 AM
This sounds like a job for the Norton Removal Tool. First, Export your ID safe if you use it. Uninstall Norton by the Control Panel method and reboot. Then download and run the Removal Tool and reboot again. When that is complete, sign in to your Norton Account to download a fresh copy of NIS. Remember to run Live Update, rebooting where required, until you are current. Import your ID safe.
Please let us know how you get on.
Windows 7 x64 SP1 N360v18.104.22.168 NU16 SSR 2013 Secunia PSI SpywareBlaster NoScript MBAM free SAS free
04-18-2012 07:10 AM
04-18-2012 10:28 AM - edited 04-18-2012 10:53 AM
I'm also getting this crash but with norton 360, running the latest version, it's crashing whether I try and add a new rule or if I try to modify an existing rule, very annoying issue and it's been happening for quite a while now!