Author Topic: (Fixed) Now I am at 160901-8! (Read 10812 times)

=Snake= · « **Reply #30 on:** August 31, 2016, 08:56:17 PM »

Just made a manually update of VPS and have now another version (see screenshots).
You should try the same way.

=Snake=

cruiser25 · « **Reply #31 on:** August 31, 2016, 08:58:44 PM »

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.

=Snake= · « **Reply #32 on:** August 31, 2016, 09:12:00 PM »

Quote from: cruiser25 on August 31, 2016, 08:58:44 PM

I to had version 160829-1 until five minuts ago but now it´s ok.

Thank you for your feedback.

=Snake=

mchain · « **Reply #33 on:** August 31, 2016, 10:14:34 PM »

Quote from: greenflow on August 31, 2016, 08:36:55 PM

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?

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.

bob3160 · « **Reply #34 on:** August 31, 2016, 10:24:15 PM »

Quote from: mchain on August 31, 2016, 10:14:34 PM

Quote from: greenflow on August 31, 2016, 08:36:55 PM
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?
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.

REDACTED · « **Reply #35 on:** August 31, 2016, 10:36:43 PM »

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.

lucD · « **Reply #36 on:** August 31, 2016, 10:56:37 PM »

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.

Gopher John · « **Reply #37 on:** August 31, 2016, 11:00:32 PM »

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.

REDACTED · « **Reply #38 on:** September 01, 2016, 01:37:22 AM »

Update: After 2 days of NO UPDATES I am now at 160831-3!

REDACTED · « **Reply #39 on:** September 01, 2016, 03:32:02 PM »

The Issue seems 2 have fixed itself as I am now at 160901-2!

REDACTED · « **Reply #40 on:** September 01, 2016, 03:34:18 PM »

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.

REDACTED · « **Reply #41 on:** September 01, 2016, 09:50:37 PM »

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

mchain · « **Reply #42 on:** September 01, 2016, 10:46:43 PM »

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.