After significant help from the helpdesk, they re-installed v6. All working well since then.
Not sure about updating to the new "patched" version now !
After significant help from the helpdesk, they re-installed v6. All working well since then.
Not sure about updating to the new "patched" version now !
Hello Again TightGit,
Well after sending in copies of Norton Power Eraser scan results and no answer, yet I emailed Mr. Weiss about the old cpu and old .NET Framework. He told me to contact customer support at norton.com/chat.
After they went Remote Desktop with me, I finally asked if the Norton 360 ver 20.1.1.2 would work with my setup (old cpu and .NET Framework ver 1.1 thru 4.0 The answer was that it Would. So he suggested that I contact Microsoft to troubleshoot Win XP sp3 .NET Framework.
Instead of doing that I thought maybe I could work on this a little longer.
With Norton 360 ver 6 running fine, I went online and discovered that there are a lot of fixes for .NET Framework.
However, My computer doesn't run perfectly and the scans from NPE led me to believe this was where to look. Also I remembered that an old printer driver program would not close properly when cpu was being shut down. So I uninstalled it using Control Panel Remove Programs. Afterwards I ran NPE again to see if it made a difference in the scan results. Guess what removal of that old program made the condition much worse. There were multiples of the same .NET files showing up in the scans.
So I knew I was getting close to the root of the problem. Having saved the install disk for the program I found a DOS Uninstall tool therein to remove the program more thoroughly.
That cleared up the problem with .NET Framework files and Norton Power Eraser. There wasn't a problem with the files themselves but with the way they were being used (apparently old program would not release or wasn't compatible, perhaps versions of .NET provided by the 3rd party not recognized by Norton products). Anyway ...
So I clicked on New Version Check and upgraded to Norton 360 ver 20.1.1.2 and everything was great until I checked my email and the same problem with "Symantec Service Framework encountered a problem and had to close." I ran NPE again and that was Good.
So I uninstalled using both tools and reinstalled using the link directly. Now all appears to be fine.
Now I know there are tools that can clean up old programs after their uninstall leaves fragments behind, also know about tools that clean up the registry. Some maybe too thorough, while others not thorough enough. A judgement call. Norton has been around a long time and I do trust their expertice.
See attachment for NPE scan results
daw
Hello again Daw and thanks for your continuing battle with Framework.
I'm afraid most of that is over my head!
I've got a stable system with the earlier version of 360, so I'm not going to risk the wrath of Mrs TightGit by altering anything.
I've a new computer on order which will run Win 7, so hopefully the new 360 will be ok on that.
All the best.
Either try 20.2 (which has just been released) or go back to v6 : that's what the helpdesk has advised me to do. v6 works fine (for me) with XP.
Has 20.2 definately addressed the framework problem?
If not, I'm sticking with my previous version, as it's such a hassle to keep uninstalling/installing.