This is really frustrating because I don't remember agreeing to the upgrade to begin with. In any case, NIS is reminding me that my is at risk but when I attempt to use the "Fix Now" option or enable anti-virus protection nothing happens. I simply get a prompt looking like this:
The lack of explanation is frustrating. I'm not given any hint as to what to do next except try again. I pressed "support" in the upper right, but that told me that nothing was wrong.
This is really frustrating because I don't remember agreeing to the upgrade to begin with. In any case, NIS is reminding me that my is at risk but when I attempt to use the "Fix Now" option or enable anti-virus protection nothing happens. I simply get a prompt looking like this:
The lack of explanation is frustrating. I'm not given any hint as to what to do next except try again. I pressed "support" in the upper right, but that told me that nothing was wrong.
Didn't work, unfortunately. The system date and time are correct. Ran LiveUpdate until there was nothing left to download. Still can't get NIS to stop telling me my computer is at risk.
I also tried manually turning on Antispyware, Auto-Protect and SONAR Protection from the settings window, but when I press "Apply" nothing happens. If I press "OK" then come back to settings, all three are returned to off.
I'm having the same issue. I turn on all Antivirus, Sonar and Antispyware settings, select Apply, and Back. When I go back into the Settings, everything is turned off.
I too have tried the Norton fixes with no luck. I then started a Chat session and repeatedly was told a reprentative would be with me shortly. After seeing that message 10 times over the course of 35 minutes, I gave up.
I'm having the same issue. I turn on all Antivirus, Sonar and Antispyware settings, select Apply, and Back. When I go back into the Settings, everything is turned off.
I too have tried the Norton fixes with no luck. I then started a Chat session and repeatedly was told a reprentative would be with me shortly. After seeing that message 10 times over the course of 35 minutes, I gave up.
Not sure where to go from here.
Sorry to hear you had to wait that long for chat.
If you have tried the suggestions in this thread, I would suggest trying chat again. Sometimes it does take a while to get a representative, but we hear the service is worth the wait.
Please let us know if you get the help you need, and what the solution was.
I have an Intel Core 2 Duo processor. Also, the link you sent me says the issue was "solved", but there is no actual solution in thread. Do you have any more suggestions, or should I go about trying to get a refund for software that doesn't work?
I have an Intel Core 2 Duo processor. Also, the link you sent me says the issue was "solved", but there is no actual solution in thread. Do you have any more suggestions, or should I go about trying to get a refund for software that doesn't work?
I don't know a solution to this issue. I gave the link because, I think, it is the same issue that you have, and if it is, then it was submitted to the Product Team so Symantec is aware of the problem. This is why it's marked as solved.
I have an Intel Core 2 Duo processor. Also, the link you sent me says the issue was "solved", but there is no actual solution in thread. Do you have any more suggestions, or should I go about trying to get a refund for software that doesn't work?
I don't know a solution to this issue. I gave the link because, I think, it is the same issue that you have, and if it is, then it was submitted to the Product Team so Symantec is aware of the problem. This is why it's marked as solved.
A practice done by the forum moderators BTW, not by those reporting the "issues", and one that (I believe) never made much sense because it heightens the likelihood for "issues" to get lost in the shuffle and thereby end up "falling through the cracks", just as this one obviously did...
A practice done by the forum moderators BTW, not by those reporting the "issues", and one that (I believe) never made much sense because it heightens the likelihood for "issues" to get lost in the shuffle and thereby end up "falling through the cracks", just as this one obviously did...
Regards,
John
I know, I also never marked my beta bug report threads as solved in the Beta forum board. I think it was Tim or another Admins.