Earlier today I was still @ 08/27/2016-0! Now I am @ 08/28/2016-1!
I prefer the Microsoft Edge Web Browser over other web browsers like Google Chrome and Mozilla Fire Fox.
The suggestion was to try and see if the issue lies with the Edge browser or not, it isn’t so much preferences but trying to find the problem.
It is your choice what you do on your system, but if you aren’t prepared to try suggestions then there isn’t much else that I can suggest.
There will no longer be any Security Updates 4 Windows XP (All Editions & All Service Packs) as it’s Life Cycle is over!
Do you think I don’t know that, this system will continue on winXP until I replace it. But we are here trying to resolve your problem.
I take many proactive measures to protect my system, including full system backups weekly (keeping the last 6 backups) and daily backups of data files that are more volatile.
Seems like you are having more problems with win10 than I am with XP 
Well for one thing perhaps you missed the fact that I mentioned that this is Windows 10 Home Edition Red Stone Beta Build 14905 from the Windows Insider Preview Program. This Build is far from Stable as it’s tied to the Fast Ring of Updates rather than the Slow Ring of Updates. It’s designed to be on the Bleeding Edge of Windows 10 Red Stone Beta Builds!
But a good av can block the threads that are trying to abuse the holes.
Both my computers have been stuck on definition 160829-1 for 2 days now. Have even tried to manually update through “Update”, “engine & virus definition” within Avast. Told that I already have the latest definition (just checked that the latest definition on Avast Update history is 160831-0). The first system is running Avast free 12.2.2276 (build 12.2.3126.2), Windows 10 Pro. The second is running Avast free 12.1.2272 (build 12.1.3076), Win Vista. Is anyone else having the same issue other than original post above?
Hi!
I jst updated my xp machine and have the same version of VPS: 160829-1! I don’t see it as a prob!
Sorry.
=Snake=
Just made a manually update of VPS and have now another version (see screenshots).
You should try the same way.
=Snake=
I to had version 160829-1 until five minuts ago when it updated itself to version 160831-3. I was just going to update by downloading the latest version myself when it happened. So now it is up to date. server problem maybe ? I did several tries to update within the program but it said that I had the latest version 160829-1 despite the today date 16.08.31. but now it´s ok.
Thank you for your feedback.
=Snake=
The definitions version date is dependent on what the local avast servers provide, so I, too went without for more than 48 hours. Not much to be done from here except to know the updating issue is not with your system.
Since the streaming updates are working, you are still fully protected. The VPS updates only consolidate the streaming updates.
I would worry if the streaming updates stop.
Thanks to all those who responded. My streaming updates seem to be working still (just checked: latest update received only 2 mins. ago). My VPS, however, is still showing the same, 160829-1. The suggestion that it is probably related to the local Avast server, and not my systems, makes sense. Guess I will wait a while to see if Avast resolves this itself, otherwise I will update to the latest versions of Avast for both systems (which I was planning to do soon anyway).
Snake: the VPS is usually updated daily, sometimes even several times a day, although there are some days when this does not happen. Thus if your system was originally showing the VPS for Aug. 29 today (when we already knew that the VPS had gone to 160831-0), chances are you were having the same problem we were having although you might not have realized it.
My very casual observation is that vps updates have recently been fewer in number and my assumption is that Avast is shifting the load on to the streaming updates. If VPS and streaming updates both stopped for two days then I might be concerned but, as others have remarked, there’s nothing really to worry about when there isn’t a new vps for a day or two.
I am aware that streaming updates contain all that the VPS updates contain plus some additional current detections. However, that doesn’t excuse the fact that repeatedly the Avast VPS servers aren’t serving the latest current VPS to ALL users across the world. There needs to be more effort put into making sure that the current VPS is going out and being served. As it was, apparently no one at Avast was aware that the served VPS was not current for almost 3 days. There is no excuse.
Update: After 2 days of NO UPDATES I am now at 160831-3!
The Issue seems 2 have fixed itself as I am now at 160901-2!