12-19-2008 08:10 AM
My NIS 2005 is set so Live Update works automatically. I'm running Windows XP, SP3. For a long time, more often than not, I get the pop-up screen, five times in a row, every five minutes: "Rules automatically created for the program: Symantec Live Update".
I've Googled this issue countless times but found nothing that applies to me. Another user had the same issue with his NIS 2006 and was told to get the free upgrade to 2008 - I tired but the upgrade isn't available to NIS 2005 users.
Can anyone shed some light on these annoying notifications? The pop up notification window pushes itself on top of other windows so it interupts typing and makes for a very frustrating experience.
Solved! Go to Solution.
12-19-2008 09:05 AM - edited 12-19-2008 09:05 AM
This problem may happen if some of the program rules for LiveUpdate got corrupted. Try removing all the program rules in firewall and then run a program scan. For more instructions, refer to this Symantec Support Article. Let me know the results.
12-19-2008 01:19 PM - edited 12-19-2008 01:21 PM
1. Open Norton program.
2. Click Personal Firewall.
3. Click Configure.
4. Click the Programs tab.
5. On the Programs tab, select the entry for Symantec LiveUpdate(Luall).
6. Do one of the following according to your situation:
7. Click Ok, and again click Ok.
8. Run LiveUpdate. If you get the prompt for LiveUpdate from firewall, click Permit.
If the problem persists after this, you may need to restore the default firewall rules in your NIS 2005 program. Refer to the instructions in the section "how to restore firewall rules" in this Symantec Support Article.
12-19-2008 01:40 PM
Upgrade to NIS 2009 for free not 2008.
12-19-2008 01:52 PM - edited 12-19-2008 01:54 PM
joeyjoejoejr is using NIS 2005.
My NIS 2005 is set so Live Update works automatically.
12-19-2008 04:19 PM
12-19-2008 10:26 PM - edited 12-19-2008 10:31 PM
12-21-2008 08:29 PM - edited 12-21-2008 08:34 PM
12-22-2008 03:55 AM
My best advice would be is to contact their support.
However, you can try uninstalling and reinstalling the product once to see if this reoccurs. More often than not, it works.
Ignore this if you have already tried it out and no luck with it.