07-22-2008 01:53 PM - edited 07-22-2008 02:32 PM
Now it seems working!
I'm sure that it starts red, then become green.
I try a reboot.
Hope I'm not speaking too early.....
BAD news... red and not working again after a reboot....
07-24-2008 10:32 AM
For me it seems to work too since last weekend. I am feeling now much more safe when the green check is here.
That green appeared 20.7. where norton showed that last update was the day before (where I only saw red ).
I had the same experience after reboot. For some time it was really again red and I thought it was only a short success, but after some hours a click on the red icon told that it is busy with some protection checks and later
the green icon came up again and was not lost since some days where I did not reboot, I did turn off standby.
Did I read correctly that some Norton developer promised here to publish when there are updates related to this problem?
I didn't see a message, maybe this new green check in restricted user account was not planned.
Hope it stays green and really protects in future.
07-29-2008 01:19 AM - edited 07-29-2008 01:20 AM
Any update on the eta of this patch?
3 of the 3 computers I've installed this liscence on (vista, 2xXP) are all still experiancing the same problem.
07-29-2008 04:00 AM
The "your pc is not protected from intrusion attempts" problem did not seem to exist 07/26, then returned on a restart 07/27 on two different Vista 32bit SP1 PC's with single Administrator-level accounts. On my XP Pro SP3 notebook, the problem has never appeared.
I have no evidence that the problem, at least on Vista systems, has been resolved.
07-29-2008 09:24 AM
Sorry I do not understand. What is your problem and how is your set up. I have no issues with 2 admin accounts and no limited accounts, and am not aware that anyone else does either. If your problem is indeed different to that already commented upon by Symantec then you might care to amplify.
07-29-2008 03:59 PM
After reading all the posts on this problem, I would like to add one more wrinkle. Yes, I too have the red "x" problem on the 10 Windows XP Pro SP3 PCs that I maintain for a local non-profit. And yes, I have gone through the chat tech support route. You would think that they would be aware of the generic issue.
A remove/reinstall/update today (7/29) on a test PC did not solve the problem.
I have a personal new PC running Vista Business, SP1 which has an intermittent red "x", running under the administrator account. About every 6 or 7 boots, the green check turns to a red "x" during startup. Clicking "fix" clears the problem. I have been on line with chat support and they have removed and reinstalled 360 V-2, and checked everthing, but the problem is still there. Since it is intermittent and can be fixed, I a going to live with it until Symantec issued a fix.
07-29-2008 05:29 PM
I have also had this problem since May. Since there was a report of a solution, I contacted Norton help and pointed them to this thread describing the problem. They had me uninstall and reinstall the software. I did this on July 27th. It appeared to go away and now is back.
I have uninstalled and reinstalled this software at least once a month since April because of various bugs.
Having the help desk give you a solution that does not work adds salt to the wound.
07-29-2008 09:49 PM
First of all, there is not one problem reported in this thread. Some users have an issue with "limited account users", whilst anothe has reported having a problem using administrative account user. So with respect, I do not know what problem you have, what operating system you are using or what version of Norotn 360.
I have posted in this thread a link to another thread where some issues have been raised, escalated and answered by Symantec.
I am not directing my reply here just to russeldj, but to everyone. You do need to follow links and read other threads. If you problem is as described then you have the current position and it has not changed. If you have a different problem, then you need to post the exact steps to recreate / reproduce your specific issue.
Finally, I would point out that some users have had their issue resolved, some not. It is possible that to determine which class you fall within, help desk felt it worth carrying out a reinstall. The solution may have worked for some but not all.
For those that it did not work for, you need to be patient. I refer you all again to either my post in the other thread or to Tony Weiss's post, message no 80 in this thread.