Mix of dates

Today is March 29 and I can’t understand the dates of Avast’s updates. If you look at the home page of avast.com, you’ll see that the latest update was on March 27:


http://s45.radikal.ru/i110/0903/bd/7cb2cb3e66c4.jpg

But on the update page it is said the last update was on March 26:


http://i038.radikal.ru/0903/52/b16b9edaa074.jpg

And my Avast already has a manual (not automatic!) update from March 28:


http://s60.radikal.ru/i168/0903/c2/1dc0121be1b0.jpg

What’s happened? Are automatic updates still possible?

The homepage don’t always update as fast as we want.

And automatic updates work just fine, latest update is VPS 90328-0

The home page is more likely to be up to date (English home page shows VPS 090327-0 27.3.2009) than the VPS History page which shows 25/03/2009 as the last update, it obviously has to be edited to include all signatures added in each update and there are times when it is out of sync to the home page.

Since the manual download for the complete VPS Update is everything it may not be updated as frequently, the English page shows a more recent one also (The latest iAVS update was published on: 26.3.2009 version: 090326-0 ).

Personally I never worry about this if my version confirms I have the latest.

I got accustomed to everyday automatic updates and if I have none, I start to suspect that there is something wrong with my antivirus.

Yes, they are almost every day and sometimes more than once a day, but there is no set schedule. So that is the beauty of the auto update, it will check when you first connect and every 4 hours if you remain connected or when you next connect.

Edit there has just been an update, now 090329-0 ;D

Thanks. I’ve just got it through autoupdate. :slight_smile:

why its not updating in the site ?? why they are late? i think that is a something bad to a company like avast … !! they have to solve it soon as possible even its daily updated but the site should be updated automaticly…i hope to resolve this problem ass soon as possible…

I find that he update package ‘vpsupd.exe’ is up-to-date even if the web-page info isn’t.

Because I guess it is a lower priority than getting the signature updates out.

It is meant to happen automatically at the same time and for most occasions it is, sometimes it is out of sync and has to catch up.

It really isn’t a problem as the auto update process keeps the users VPS signatures up to date with the latest signatures even if the web site information is not in sync.

If you check today the home page and the VPS History page reports the correct version: 090330-0, it really isn’t an issue, I rarely check the web site for the version number, but just do a manual update check and it normally tells me I’m up to date.