• All Community
    • All Community
    • Forums
    • Ideas
    • Blogs
Advanced

Not what you are looking for? Ask the experts!

This forum thread needs a solution.
Kudos0

antiphishing updates has stopped running (what is latest definition)?

I have NIS 2009 16.5 installed under Windows XP Pro SP3 and normally the "antiphishing updates" background task runs at least once a day.  I checked today and noticed that the last time it ran was May 16 at 8:17 PM.    The latest Web Definitions I have is 20090516.003 which was installed May 16 at 9:47 PM.  Since then no nwe Web Defintions have downloaded.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Running Live Update manually says there's no new updates.  I've tried rebooting my machine.

So is 20090516.003 the last update or is something wrong?

Also does the background "Antiphishing updates" task run regardless if there are updates or not?
Message Edited by Morac on 05-18-2009 11:40 AM[edit: Resized image.]Message Edited by shannons on 05-18-2009 09:05 AM

Replies

Kudos0

Re: antiphishing updates has stopped running (what is latest definition)?

My NIS 2009 History under identity shows that Antiphishing definitions were updated 4 times since 5/16/2009,tha last one being 10minutes ago. but all say the same thing.

Antiphishing Definitions version 20090516.003 downloaded. Today is 5/18/2009, why would I update a version from 5/16/2009?

Is that the latest version or is there a problem on my end? Usually I receive 2-4 updates every day.

Is anybody else still on version 20090516003?

Message Edited by TooStrong on 05-18-2009 08:39 AM
Kudos0

Re: antiphishing updates has stopped running (what is latest definition)?

I have NIS 2009 16.5 installed under Windows XP Pro SP3 and normally the "antiphishing updates" background task runs at least once a day.  I checked today and noticed that the last time it ran was May 16 at 8:17 PM.    The latest Web Definitions I have is 20090516.003 which was installed May 16 at 9:47 PM.  Since then no nwe Web Defintions have downloaded.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Running Live Update manually says there's no new updates.  I've tried rebooting my machine.

So is 20090516.003 the last update or is something wrong?

Also does the background "Antiphishing updates" task run regardless if there are updates or not?
Message Edited by Morac on 05-18-2009 11:40 AM[edit: Resized image.]Message Edited by shannons on 05-18-2009 09:05 AM
Kudos0

Re: antiphishing updates has stopped running (what is latest definition)?

Yes, I'm seeing the same thing.

[edit: Updated to reflect merged post.]

Message Edited by shannons on 05-18-2009 09:12 AM
Kudos0

Re: antiphishing updates has stopped running (what is latest definition)?

Hi Morac,

  I just asked the same question in another thread. I am also stuck on version 20090516.003 and my background task has not run since 5/16/2009 at 10:41 pm

Kudos0

Re: antiphishing updates has stopped running (what is latest definition)?

That is the latest update.  There is nothing wrong on your end.
Win10 x64; Proud graduate of GeeksToGo
Kudos0

Re: antiphishing updates has stopped running (what is latest definition)?


dbrisendine wrote:
That is the latest update.  There is nothing wrong on your end.

So the antiphishing updates background task only runs if there are new updates?

Kudos0

Re: antiphishing updates has stopped running (what is latest definition)?

No that is the Brackground task history (in the CPU usage screen).  I just ran a manual live update and recieved Web Protection update 20090516.004 .  So the updates are working, there is just not as many as virus definitions.

Just re-read your question: the history will be updated if there are any updates AND the task ran in the background AND it updated successfully.

Message Edited by dbrisendine on 05-18-2009 02:51 PM
Win10 x64; Proud graduate of GeeksToGo
Kudos0

Re: antiphishing updates has stopped running (what is latest definition)?

I ran LiveUpdate manually and it updated to 20090516.004. A few minutes after that, the "Antiphishing Updates" background job ran (the PC wasn't even idle). So it looks like that job only runs after a web protection update is successfully installed.

I guess I got confused because normally the "antiphishing updates" task ran daily, presumable because there were daily web protection updates.Message Edited by Morac on 05-18-2009 03:42 PM
Kudos0

Re: antiphishing updates has stopped running (what is latest definition)?

Web protection is Antiphishing; the CPU usage / background listing is kind of slow in updating. The update you saw was the manual one you ran; just takes a little while for the CPU Usage report to update.
Win10 x64; Proud graduate of GeeksToGo
Kudos0

Re: antiphishing updates has stopped running (what is latest definition)?

I'm pretty sure the background listing wasn't the manual update I did since I saw the background update start to run about 3 minute after the manual update finished. The background task ran for 10 seconds and then finished. I'm guessing that there is some kind of antiphishing processing that is done with the web protection updates kind of like how the idle quick scan kicks off after a virus definition update.
Kudos0

Re: antiphishing updates has stopped running (what is latest definition)?

Hi thread members-

Morac, you are pretty much correct.  The "Antiphishing updates" job is scheduled to run after a Live Update session (either interactive or Automatic LU) runs and obtains new definition data for the antiphishing feature.

The creation of the antiphishing configuration data from the definitions data takes some time/CPU and we didn't want it affecting the overall time of a LU session.  Because it is a background job and gets scheduled to run, it has some variance in when it actually ends up running.  It tries to run as an idle task.

Also, because Automatic Live Update is running in the background on its own schedule, that may cause some additional variance in the scheduling of the "Antiphishing updates" job.

Finally, security history has updates indicating both when the initial definitions are downloaded (completion of the LU session) and when the definitions are being used by a new antiphishing configuration  (completion of the "Antiphishing updates" job). 

We have recently determined a bug that can cause the "definitions downloaded" security history event to occur sometimes when new definitions haven't been really downloaded, but rather it's using the current definitions.  We should have that fixed in the next release.

Regards,

Matt Powers

Symantec Corp.

This thread is closed from further comment. Please visit the forum to start a new thread.