06-29-2012 05:25 AM
Philip_B wrote:Well, the problem wasn't fixed after all. Will try again to fix it tomorrow.
Hi Phillip_B,
I removed the solution from the post that was marked as the solution so that others will continue to look at the threrad and attempt to assist.
07-03-2012 09:27 AM
I thought maybe that when I downgraded to Norton 360 v5 without first using the Norton Removal Tool that was the cause of my problem continuing. So I used the Norton Removal Tool. Then I reinstalled Norton 360 v5. Was my problem eliminated? Nope. Now I'm at a complete loss. I know I have not had this problem since Norton 360 was first installed. But I am not sure when it began. I was sure it was when v6 came out. Now i'm not sure.
07-03-2012 06:07 PM
Philip_B wrote:I thought maybe that when I downgraded to Norton 360 v5 without first using the Norton Removal Tool that was the cause of my problem continuing. So I used the Norton Removal Tool. Then I reinstalled Norton 360 v5. Was my problem eliminated? Nope. Now I'm at a complete loss. I know I have not had this problem since Norton 360 was first installed. But I am not sure when it began. I was sure it was when v6 came out. Now i'm not sure.
It may be some Windows update made some change that does not play well with the combination of your apps and Norton. The timing must have coincided with your Norton upgrade.
When the was program working, were you able to see what the chat tech had done? Is it something you could duplicate yourself to test again?
07-04-2012 02:59 AM
Yes, it could be a Windows Vista thing. It was never working when the the Chat Tech was doing his magic and yes I could see what he was doing. he tried the security settings on the Norton folders. He added my apps to the firewall. He was the one who downgraded to v5.
I was toying with the idea of seeing if my original Norton 360, (no idea on the version) disk dated 2007, would work.
07-10-2012 01:13 PM
I went back to my backups to search for the event logs and I did find that this problem began February 10, 2012 at 1:15pm.
So I am not crazy in thinking that this is a recent problem.
