For over a week now, database is stuck with 161219-1. However, I can see that files are downloaded/updated. See picture.
This sort of out of sync issue (program says up to date but the display was wrong) used to be seen on occasion in avast. An avast repair usually sorted out this out of sync condition where the reported data didn’t match the displayed data.
I don’t know if the AVG beta has the avast repair function merged into the AVG settings.
It shows in the folder as 16121901, but the last modification date is 26th December. How is it on your PCs?
Your imgur.com image is AWOL.
On any count mine shows 16122800 (today’s current VPS and its associated stream 16122800_stream version both updates today.
Oops, attaching it here… ;D
Just finished clean reinstall (haven’t tried this beta on this particular PC yet)
https://snag.gy/VPNk7A.jpg
This is certainly looking like a VPS update issue with this new AVG beta, my image was on this win10 notebook and the latest avast version. So no issues on the avast program VPS updates.
That said I still think you should try a Repair of your AVG beta installation if the AVG beta has the avast repair function ?
There is a repair option. I’ll repair it if i find free time today. 
I’ve tried the repair and it still stays at 161219-1. When check for updates it shows as downloading some files and then says: “Already up to date 161219-1”. Let’s hope for 170101-1. 
Today the VPS was updated to 170105-0, but there is no number of the virus definitions in the About page, don’t know if it’s a bug or intended.
Today the VPS was updated to 170105-0, but there is no number of the virus definitions in the About page, don't know if it's a bug or intended.
You don’t say what avast version you are using, latest regular release is 12.3.2280.
On my about avast shows the number of definitions as 6,033,664.
Personally I’m not concerned with the numbers more on the protection. Avast is regularly optimising the virus signatures to capture more than just a single malware variant, so it is pretty hard to say how many variants would be caught.
Hmm, this is the… AVG beta forum here. 
Oops
Then I think that you have to expect some niggles like this when trying to implement avast style updates and info into the AVG beta. But it is certainly right to report it.
My second point is still valid I think, that number is meaningless (even when displayed) other than our database is bigger than yours database.
Especially when they are working on the unification of the definitions. What i as thinking is that this period of not receiving new definitions only streaming ones was because of a “good work behind the scene”.
It really depends on how generic and complex the definitions are. Norton has around 25 million and Comodo some millions more, but you can’t really say that the signatures are Comodo’s strength. ;D However i would like to see what will be the change after the integration of the AVG’s definitions and now i don’t know if this has happened or not. :