Hi, one of my machines apparently updated the latest definitions as of 9/12/09 091212-1. Under “about Avast!” if I click VPS File it still shows 091212-0 and a date of 12/11/09. I ran the updater manually(right click Avast taskbar icon-updating tab) and it says i’m up to date with 091212-1 12/12/09. I even downloaded the manual installer and it said the same thing. I never had this issue before. Any Ideas? Thanks.
What VPS file (I assume 400.vps), and more crucially why would you do that anyway ?
Dates on files don’t reflect the second update of the day, as the VPS reported by avast, e.g. 091212-1 would show a return of 12/12/2009 as far as a file modified date.
You are looking at the creation date I would guess, which would reflect when you installed avast, mine shows 09/07/2008, when avast was first installed on this particular system. So you need to display the modified date in the folder view.
The manual update file only updates the existing 400.vps file so its ‘creation date’ would remain the same, but the ‘modified date’ would reflect the manual update date.
Why would I do what?
One machine(i’ll call it system A) updated automatically today with 091212-1, when I check “about avast!” VPS compilation date the date still says 01212-0 12/11/09. So I ran the updater manually(right click Avast taskbar icon-updating tab) and it says i’m up to date with 091212-1 12/12/09. So I ran the manual update downloaded from Avast, says i’m up to date 12/12/09. The VPS compilation date under “about Avast!” is off, still says 12/11/09.
On my other system(system B) that updated automatically today with the same update 091212-1 it says 12/12/09 01212-1 under “about Avast” VPS compilation date.
So something is wrong with system A. I don’t know how to reword it to make it simpler.
Try Avast repair
http://forum.avast.com/index.php?topic=38474.0
When you said this “if I click VPS File it still shows 091212-0 and a date of 12/11/09.” I thought you were looking at a physical file, the 400.vps file and not the VPS information in about avast.
The repair should resolved this out of sync issue between reported and actual VPS version, it has in the past.
The repair worked, never knew it had that feature. Thanks guys.
You’re welcome, sorry about the confusion.