I would start adding flames to the fire about this as I am upset about how long this issue has gone on without a fix. But first let me provide things I have tried.
I have tried running in admin mode.
I have tried install 19.5.x.x from www.norton.com/nis12
I have tried adding a few programs to the program rules then, clicking apply shutting down NIS and either rebooting or restarting the app.
I have tried switching the symhtml.dll from the original 2012 install DVD with the current one (6.0.x on disc, 6.5.x on computer) but all it did was wipe clean.
I did the remove and reinstall routine.
I have even made sure IE is the default browser (due to the html)
I have verified my .net installs (I don't have 1.1 since Win7 warns against and 4.5 since it6 is stsill in beta)
It also appears that your are using parts of perhaps google chrome? Could the fact they are updating it to a new version every other day (exaggeration of course) be a possible cause.
I have looked for every remedy on the internet and have not found one. Now the part where I go mean.
Is this problem going to be a "version" upgrade required fix. Meaning you will not solve it or say it will take to much time when you have your 2013 products coming down the pipeline in 3-4 months. So if you want the fix you have to buy the 2013 product.
Also this problem is not just restricted to your 2012 NIS, it is in your AV 2012, your 360 and even your 2013 and appears to have happened in some of the 2011 products. If so that this problem showed up in the 2011 product, why did you not find a way to avoid it for most of your 2012 line up and now your 2013.
Well here is an addendum.
I got a call today from someone who sounded like they knew what they were doing. He assured me that my install was perfect, that all files that should be present from microsoft .net were there and everything from NIS was present. He then said well if it happens again just uninstall and reinstall. I told him that would erase all the program control rules that were setup. He insisted no it wouldn't. He says let me show you how. He took me into the microsoft screen for uninstalling programs and
clicked on the uninstall/change. He says make sure you select the top option, that you plan to reinstall a Norton product and to keep your settings. I informed him that according to Norton and the Norton forums that program control settings ARE NOT SAVED (was polite and didn't yell) but he assured me they would be and I would be able to add to the program control rules. Well somewhere around 280 the crash occured. I did what he said would not delete the data, but guess what HE WAS JUST AS WRONG AS SYMANTEC IS WITH HOW THEY ARE "WORKING" on this problem.
I have been with Norton/Symantec since the days of floppy disc, blue in the corporate colors and Peter Norton appeared on the box. It seems every year Symantec just goes farther and farther away from what they once were. Tech support went. Refunds/Upgrades if you just bought a product, well thankfully that worked out. But has anyone been able to get tech support that didn't follow what seems to be a script. I have been assured that tech support is fully trained and do not follow a "script".
The rep said that they have pretty much figured out the issue and will be issuing a patch within about a month as they need to fully test the fix.
I asked the rep what files could I backup on a constant basis so I would lose all my work, he said there were none. I said I think windows 7 64bit sp1 is shutting down too quickly for Symantec to save the log/database or whatever they use to store the program. I was assured that Norton is "constantly" saving the databases/logs or whatever.
Now for those who say why do you need to make your own program control rules, Norton does it for you. well have you noticed how more and more programs take the liberty to sends ads through their programs. Have you noticed how many companies have had to admit to "spying" on its users by taking private data they said is only meant to "improve" what they offer. They figure Google can do it, why can't they. So I don't want to be spammed in a program by ads, by offers, by whatever they try to send through the program, and I also do not want them hiding a clause in the End User Lic. Agreement that says they reserve the right to collect data they assure will not be sold or used for any other purposes. Well they got bought, opps change in EULA, and the new company revises its privacy rules, oh sorry but we decided to market your data to help pay for the purchase of the company. So that is one main reason I CUT programs off in program control.
Also using manual controls where you say allow or block does not work properly. I tried it with apps I knew made internet connection attempts, and caught less than 50%, 40% of what they did catch, they only allowed you to choose to block the current instance and not forever. Oh guess what you can't go into program controls to modify things, because it crashes the program.
Symantec this is pure sloppy on your part. I know you are "innovating" "adapting" "improving" the performance of your program after you were blasted hard about the 2008 or 2009 version (can't remember when they switched to the 2010/2011 model). However test your product more efficiently. That means don't try one change and if it works remain convinced it means the feature works. All customers should be given a license extension who have reported the problem. This problem now is going into what (since 11/2011) so 5 plus months. How many customers don't even know they have this same problem as they perhaps are not as informed about software applications? How many have done reinstalls like instructed only to have the problem return and not know where to look to see if others are having the issue or don't have the time? (sorry I forgot to put ? at the end of my qustions, it was late and right after another failure).
I know your 2011 product works, why? Well I looked at how many rules I had, it was over 2000. So right now you 2012 can only handle about 10% of the rules of 2011. That is a travesty.
I am sorry to norton tech/engineers/mods about being so upset, but how would you feel if you were actually in our shoes and didn't now have the programming or inside knowledge of the software and were told to hold on wait for a fix and by the way you shouldn't have a need to use that feature.
Tim you have been quiet, maybe because you are tired at the mud slinging against you or for some other reason. But how about at least give us a heads up on what Symantec believes the problem might be. All these posters who are having the problem then could provide you an excellent of real world testing to help you. Remember the machines in the office are not the same one your users have at home via their desktop or laptop. So give us something to work on for you and the engineers with an understanding that if it screws your system up that is not Norton's problem. I am sure many people know how to clone their drives so that a damaged windows install can simply be cloned back over or they have test machines of
their own that they can run the test there.
But PLEASE educate/train/instruct your tech support lower level support so they are able to be more capable of handling issues and are informed of issues so they don't waste the customer time online promising a fix only not to even know where a feature is located, despite the customer telling them (my first tech support help spent 3 hours going in circles and then couldn't find the program control I had to move the mouse during his remote session to the feature).
