Avast 9 not updating virus definitions - dallas3super

Avast 9 (Free) version 2014.9.0.2008 is not updating the virus definitions.
As of 2:45pm cst 11/17/13 it still shows latest definitions file as 131116-1.
The settings are for automatic update, with streaming updates enabled.
I tried manually several times, to no avail.
My pc is Win Vista.
My wife’s pc is still running last Free version 8.
Her definitions file is 131117-1.
Her pc is Win 7.
(I tried updating manually several times using 2014.9.0.2007, before updating to the .2008 prog update.
As noted, still will not update definitions file to 13117-1 (or greater).

I think it’s a sync issue. Try an avast repair…

Control Panel>Programs and Features>Uninstall a Program>Uninstall/Change>Avast>Repair.

Make sure to Reboot after repair.

No need to repair, Avast just haven’t released any vps updates for v9 so far today. Streaming updates are coming through fine.

Or…GUI>Settings>Update>check manually. :slight_smile:

But “been” is correct no vps update so far today.

Check vps update history here.

If you check that link, it has them for v8. I’m back to v8 too so yeah.

i am still stuck on the 16 version as well i have tired multiple times updateing to 17 definition and it dosent update

The V9 stream has not updated today … But there have been 217 streaming updates

I’m still a little fuzzy on the whole streaming updates and the update we get with a version number. Are the streaming updates rolled in to the version update?

Are things like FP’s in streaming updates, or only in the version update? Why even have a version update sig file if everything is coming in as a streaming update. ← This one is the one I’m trying to really figure out.

if you have been offline…and when going online again, you get the VPS that containe all previous released stream updates

search avast blog http://blog.avast.com/ and FAQ section for info http://www.avast.com/en-eu/faq.php

today no vps updates…version 131116-1 avast 9

Maybe we should all try a repair, because it is happening here too.
The update history shows the latest issue as 17.11.2013 - 131117-1
It’s 18.11.2013 here, my Avast shows 131116-1, and remains at that after a manual update - it say 131116-1 is the latest.

No need to do a repair!
v8.0 and v2014 are on different servers thus don’t get the vps updates on the same cycle.
I have received well over 200 streaming updates so far today.
I’m not concerned at all. Mainly because there is nothing to worry about. :slight_smile:

The reason I suggested it was because I’m using v8 and THOUGHT that the defs should be around the same. For v8, 131117-1 is the latest.

Sorry, my “Maybe we should all try a repair” was said tongue in cheek.

I agree that if the local definition is not overly outdated there is unlikely to be any significant risk, particularly if streaming updates are being received, but it isn’t a confidence builder when Avast put the cart before the horse and show an update as the current latest, when it isn’t at that time available on the servers for those who do a manual update.

It would be better if there was no reference to it until it was actually available on the servers.

This thing happens every Sunday. Not sure why, it is specific to Sundays relative to the other six days.

terrible

No, sorry, it’s (really) not. Streaming updates are the most current, up-to-date definitions one can get, and these are done in real time. Why wait for a consolidated vps update maybe once or twice a day when one can have this more beneficial feature? I feel protection is enhanced here, not lessened, even tho a vps was not released for 2014 today.

Imagine the uproar here if there were no streaming updates and no vps for that day.

Sometimes it gets a little slow on the malware fighting front. Could be a good thing going here.

[EDIT:] Just fired up the XP system, and vps is 131116-1 but got a total of 380 new streaming updates in five minutes.

still vps 131116-1… :frowning:

Hello all,

My VPS is 131116-1 but here it is 11-18-2013,18 November!!!.
Repair; done.
manually; done.
it must be 131117-1.what to do now ?

Gercla.

nothing…no repair…vps 131116-1 fo me also…perhaps have some problem with the servants of the version 9