(Fixed) Now I am at 160901-8!

Avast free on my Win 10 computer has updated its VPS to 160901-2 today to the current one without any action on my part (have not turned on the older Windows Vista computer yet but I am assuming that it will also update without any problems now). Thus, the suggestion that some local Avast servers are apparently not serving the latest VPS, at least over the last few days, seem to make sense. Thought I would post this to help those of you who had encountered this issue over the last few days.

One thought did occur to me: if the VPS is only the consolidation of all the streaming packages that had been received throughout the day, then does the failure of the VPS to update itself the last 2 days not suggest that not all streaming packages had been received (otherwise, why would the VPS not have updated to the latest date as it did today)? Perhaps someone who understands how this works could explain. :slight_smile:

Update: I just executed a Manual Update and I now have 160901-8!

One thing to keep in mind: There needs to be time and work to integrate AVG into Avast. Once this process begins, it will go on for quite some time. Avast resources are finite and thus will affect things of this sort from time to time.

If streaming updates are working, nothing to worry about IMO.