Although I an receiving streaming updates regularly, my last full VPS update is 171204-02. I realize that my computer is still protected with the latest definitions, but the VPS updates should be updated regularly.
The issue may be server r-253-42-234-77.ff.avast.com or r-54-42-234-77.ff.avast.com.
The last VPS received on this XP system was 17120402, so two days. I don’t think it is a single server issue.
I also have a more serious issue on my win10 laptop, avast isn’t doing its housekeeping in removing old VPS sub-folders, I have 7 in all at 130MB a pop.
Since you have the same VPS as I and across the big water, you are right that it isnt’ just the servers I connect to. The server farm is not working correctly or Avast hasn’t released anything newer. There have been newer updates for Avast Mobile Security.
I believe that you restart Windows at least daily. On Windows 7, usually the old VPS folders are deleted on reboot.
They must be releasing new signatures or the frequency and quantity of streaming updates would also be impacted.
Only my XP desktop system gets shutdown at night, the win10 laptop just goes to sleep. However as you can see from my last images there are problems in both, XP not getting them and win10 not getting rid of the old ones.
I am relieved to read this. I noticed it last night and checked again today and mine are 171204-2 also. Came here to see if there was a problem. Glad I am not alone.
Hi guys, I’m on 171206-6, just checked.
I just tried a manual definition update. Says I am up to date with 171204-2. Got the same response from the attempt last night.
Strange, see screenshot…
Check out these attached images.
Image 1 shows current VPS update state as 171204-2, note that the latest update received time, when I first brought the win10 laptop out of sleep.
Image 2 shows the state after a manual update, indicating that I’m up to date.
Given the other issue of old VPS sub-folders not being subject to housekeeping, someone needs to pull their finger out and resolve this.
It may be worth while trying an Avast Repair, that has in the past resolved out of sync issues with what is reported and what is installed.
According to the screenshot, you need to reboot your system.
My AVAST has not updated since Dec 4. It is still on 171204-2.
I have tried repair and nothing changed. I also went as far as to uninstall and reinstall AVAST and it is still at 171204-2.
Even trying a manual request for update still gets 171204-2 and the message that it is up to date.
Same problem for me on Win 10 with Avast IS.
Don’t know what happens 
Manual update or reboot didn’t change anything :-[
As stream updates are running, nothing to worry about.
Having the same issue - was using manual updates to update, and now haven’t been able to update since update 171204-2.
Tried a repair, but that didn’t resolve this issue - every time I try to update, it says the definitions are up to date.
As said, if stream updates are running, nothing to worry about.
Interesting, I thought I already had 2318, I must be getting into bad habits, hanging back on program updates 
Interesting, the program update after restart has got rid of the old VPS sub-folders but the latest VPS is still 171204-2. A manual VPS update still reports I have the latest version.
After the in UI program update I got the slew of popups, confirm your protection level (well I still have 172 days left on this registration). After confirming my protection level as avast free, I get another in your face popup ‘Your loyalty pays off’ with no nice ‘No Thank you’ option.
Used the big X to kill the window and bang up comes another one ‘Not ready to commit’ try a 60 day free trial (and we all know where that leads. Again no nice ‘No Thank you’ option only start free trial, once more it is the ugly exit the big X.
I can understand marketing push when you first install, but when you have 172 days remaining on existing registration. But why are we still getting this mess when registration is a thing of the past.
Just a few minutes ago mine AUTO updated from 171204-2 to 171207-0.
I was having the same problem, but few moments ago I manually updated the definitions and now I’m using 171207-0
Same for me, update to 171207-0 runs fine 
I did know what happened with VPS update…