Irregular Updates

Still 150725-1 version. Release date 25/07/2015.No Update on 26.07.2015 & 27.07.2015.What happend to avast!? It is a server problem or what? can anybody conform this. ???

That’ the same version I have but it shows release date 7/27.2015.

Just updated to 150727-1.

Hi guys,

Be Secure when you finally got the latest version? Do you please remember what was the delay between writing the post and actually got it?

The updates aren’t instant and it might happen that the website is updated faster than the update server you are connecting to.

Martin

I am just perfomed a update(Manually) on 27th july 4.30pm and it is then updated to 150727-1.On 26th july to 27th july(3pm) there are no update (VPS) at all,But the avast! update website listed 150726-1 and 150726-2 is released.Now everything seem to be fine.Latest version is 150728-0.

Same problem encounter:(.Avast! virus update history says it is 2.8.2015 - 150802-1.But my avast! got 1.8.2015 - 150801-1.I do a force update no success.Pls Avast! fix this issue.It is so frustrating.

Source of frustration really is about using software from a third party who controls when and if updates are issued; you, as the user, cannot make the updates happen when you wish or think they should happen.

Vps updates can only be gotten when they are available on the avast server in your area, you can’t get them if they are not yet deployed.

One thing avast always does is to strive to not release virus definitions which result in false-positive detections of clean files, so verifying that this is not the case can result in delayed vps releases. McAfee borked XP systems a few years ago when they released a definition update that caused their antivirus to detect a clean Windows svchost file as malicious: http://www.engadget.com/2010/04/21/mcafee-update--shutting-down-xp-machines/

Rather have it be the case that the newest avast vps updates are clean and without issues than have systems worldwide go down because of a major error in detection routines sent out.

Really, imo, streaming updates are more important than the daily vps updates as they patch the virus definitions in real-time as they happen. Whereas, as DavidR points out, the vps is a roll-up package of all previous streaming updates, including corrections of false positive detections and are issued up to five times per day. Normally one sees only two or three vps updates per day as a matter of course.

I’ve seen up to over 500+ streaming updates come in a 24-hour period, but normally only see around 150-200 per day. I think one reason for that is malware activity; likely higher on days more streaming updates come in.

Starting with version 8.0, avast has had streaming updates as their main protection, not the vps updates. The same page you attached will state that vps updates are made so to clean up any false-positive detections as they are discovered; that is the main reason, I think, the majority of vps updates are released now vs. avast versions earlier than 8.0. That is one difference you may not have seen yet.

IMO, it is the streaming updates that are more important to the average user rather than vps updates as they allow avast to offer up-to-date protection vs. waiting several hours for new virus definition updates to arrive at your desktop.

Hi,

yes the streaming updates are more important. If you have them turned on, you are fine.

Nothing has changed from the first time that you first created this topic.

Do I constantly monitor the avast.com/virus-update-history page, no, why because it is constantly changing and be the streaming updates are more current/crucial as the VPS essentially holds those streaming updates.

The latest according to the avast.com/virus-update-history page is now 150803-1 but my about avast shows 150302-1, am I concerned, certainly not. The auto update check depending on what avast version you have and what your update settings are. The default duration being 4 hours, so yes you could see differences in what is reported on the avast.com/virus-update-history page and your about avast.