LiveUpdate can't fix it and the suggested fix (uninstall any non-Symantec programs) doesn't apply.
This has just started cropping up whenever I start the computer a few days ago. Norton internet Security seems to launch just fine, but after around 6 or 7 minutes throws up this error. Assuming it must therefore be somethign to do with an attempted update or search for updates.
Indicating SONAR protection is off and can't turn it on; computer 'at risk'.
Welcome to our community. Are you using Norton 360, or Norton Internet Security, as you state? This is the Norton 360 forum, so if you're using NIS, I'll ask the mods to move your thread to the NIS forum, where you'll get more focused assistance.
Fix will most likely be the same: uninstall; run the Removal Tool; reinstall (taking care to let it preserve your settings so you can reload them) but let's let an NIS specialist confirm that first.
Also, remember to "backup" (export) your Identity Safe cards & credentials first, if you set any up.
LiveUpdate can't fix it and the suggested fix (uninstall any non-Symantec programs) doesn't apply.
This has just started cropping up whenever I start the computer a few days ago. Norton internet Security seems to launch just fine, but after around 6 or 7 minutes throws up this error. Assuming it must therefore be somethign to do with an attempted update or search for updates.
Indicating SONAR protection is off and can't turn it on; computer 'at risk'.
Hi there - I haven't heard from anyone on this but really hoping to find some help here! Shoudl I repost in a different location?
Or simply follow the suggestion above? If so, what would be the actual process? Do I need to copy down my key or something?
any help greatly appreciated!
Thanks.
Hi,
You are in the right place. The recommendation is the best solution. Do safe your identity safe date BEFORE you start. Using the R&R tool it will verify your key that is stored on the Norton server.
Hi - followed instructions in this thread and uninstalled then reinstalled. Threw the problem again when I launched but this time the autofix worked and all appears to be good!