Help base are not updated after day 4, a base 1 number. Streaming updates 4 ( 04.12.2016 14:07:11 )
Current version: 161201-0
Release date: 01.12.2016 12:01:34
In hand through anti-virus database Avast VPS Update can’t update says that uninstall windows defender. Himself defender disabled antivirus during installation
Windows 10 1607
There is no need to worry as long as you are receiving streaming updates.
All VPS updates are consolidated of streaming updates.
Well, there is something wrong as the VPS version in the GUI should show the latest which is 161203-0 according to https://www.avast.com/virus-update-history
Next to that I am getting the warning that the VPS is out of date for a couple of days in the Beta version and after updating (it shows downloading and installing) the version not changed.
Strange, although I am running the stable build, I haven’t got any warnings that the VPS is out of date.
Hope will be updated and change the version
Do you have streaming updates enabled ?
If so as has been said you are covered as the VPS updates contain a collation of all of the streaming updates since your last VPS update.
Mine is on 161201-0 but I have lots of streaming updates in the defs folder - see image - I’m not getting any warnings about the VPS being out of date either.
Yes, all the streaming update function. I poprobyval install updates manually using Avast VPS Update. Everything went perfectly and began installation at the end of the installation program appears incompatible detected: windows defender. After this change in the anti-virus database version upgrade window: 161204-0 and databases release date remains the same: 01/12/2016 12:01:34
I don’t know if part of the problem could be related to windows defender. In windows 10 I just wonder if your virus definitions are considered out of date, does it re-enable windows defender.
Thank zapus windows defender did not lead to a good result. Contact Technical Support avast waiting for an answer.
Surely the issue here is that the VPS has not updated from the 161201-0 version. That is what I am seeing on my system; that seems to be what DavidR is seeing; that is what Eddy is reporting; that is Destiny26’s report. It is a small sample but it suggests that an update is not happening automatically, nor if one triggers it manually. If so, that is a issue of general significance that Avast need to consider.
It may not matter as we are all probably protected by streaming but that is a separate question.
Well, it can be that the VPS did update but that it is only the version number that isn’t shown correctly.
Just some more input. The same on my system latest update 16.12.01-0. It says streaming updates are installed,hopefully it is so. I´m running windows 7 Home Premium SP 1. So it is not just on windows 10 this occurs. I remember this has happened before and it took quite a while before it was fixed. Maybe one of all avast users out there could make a post if you got a new update to a newer version for example 16.12.03-0. Should be interesting if this is something that affects all of us users or if it is some local server problem.
And hello again I tried to update and nothing I go I my.avast.com account and see that the update outdated
A good thought, but looking at the files on my disc they have a Windows timestamp of 1/12/16. I suppose that actually there may not have been any VPS updates released but that would be unusual and isn’t compatible with the information at https://www.avast.com/virus-update-history which shows updates on 2/12 and 3/12, but not 4/12.
Downloaded base with http://www.comss.ru/page.php?id=128 site. That’s where they write that all stopped database be updated and run manually and nothing happens. A site admins: Hello!
It is well-known, global problem. Hopefully it will be decided on Monday.
Support The answer came in the mail.
Hello, Please send a screenshot of the problem / message that appears when an error occurs.
We will try to understand.
Confirming what others have already noted here:
Database version internally listed as 2016-12-01-0, yet apparently considered “current”;
definition files on disk are time-stamped 12/1/2016 (plus a stream for each of the next 4 days);
but streaming updates current at 12/5/2016. Seems to be a bit strange.
Windows 7x64 Pro.
As has been said, as long as streaming updates work for you, there’s nothing to worry.
Strange that when another update manually change only the version and date of issue and the number remains the same definitions and the same.
avast team pls do something. :