After having a super great experience with avast! 5, I am moving most of my friends and relatives over to this excellent software. I have never had any issues with avast! update functionality before. On 30th March 2010 I installed avast! Free Antivirus (build 5.0.462) on a brand new Dell Vostro 1520, Windows 7 Home Basic 32-bit. This machine did not come with any sort of trial or licensed antimalware/firewall solution. I disabled Windows Defender and proceeded with installation of avast!. The installation went smooth. I did a custom install and installed only File System, Web and Network shields. A few minutes after the install, avast! gave its ‘green’ update successful notification. For the following few days this machine was not connected to the internet. This machine was put online again on 7th April 2010, IN A DIFFERENT TIMEZONE. Its still in the same timezone and will remain so for a full year. Since then avast! has been unable to update. Here’s what I have done so far -
Triggered a manual update - nothing happens, i.e. no error messages, it just doesn’t update.
Downloaded the offline update file and launched it - got an error message with an error code (will report that if required).
Booted in safe-mode, ran the avast! uninstall utility, rebooted, installed avast!, rebooted, waited for an hour for the update, triggered a manual update - no update received.
I am at a loss now. I repeat that this machine never had any sort of antimalware or firewall utility. Any ideas?
If you don’t feel comfortable with the pre-release, just don’t install it - you can wait some time, as the stable version will be out soon.
why and what do you want to ping and check ???
asyn
I wanted to ping the avast! update servers from the machine in question to check connectivity issues. I remember the update server IPs being displayed in some thread, just not able to find that thread anymore.
same problem; stuck on virus definition 1000401-0 since installation of AVAST 5.0.462 on April, 11.
First, I made an install over AVAST 4 and windows screamed that the antivirus was obsolete. Thus I tried to update manually but AVAST states that it is the last up-to-date virus definition.
I made a complete uninstall and re-install but no way.
I am Vista Biz 64bits. Seems like I am the third person to report this problem on the forum; the other one having posted in French yesterday or the day before.
Thanks to help
sorry no change. I tried also with beta (5.0.499).
by the way, I got the following error message when trying to update the virus definition database from the manual donwload (vpsupd.exe):
It is a known and un-addressed issue that ANY change in computer time for ANY reason results in definitive impossibility to update version 5 properly.
I have tried any possible method (even cleaning manually every registry key I can identify) but I finally gave up and re-install 4.8.
Maybe one day somebody in Avast team will solve that. Maybe.
I agree, it is an issue that doesn’t go away, as I reported in this thread. @asyn
Humbly request that you stop telling people with this updating issue to run the beta, “and then we’ll talk”.
Some of us aren’t interested in betas, the changelog didn’t say anything about addressing this issue, and who has installed and ran the beta and it fixed their updating problem?
I don’t feel as though you are passing along valid advice, and I’d like to see someone respond besides you telling us to install the beta.
As a matter of fact, it is not a beta in the truest sense of the meaning. It is a pre-release of the next update version which includes bugfixes. And the curren 5.0.504 also adresses update problems: http://forum.avast.com/index.php?topic=58183.msg490305#msg490305
So, yes, I would recommend the beta as it is more an update than a beta.
Well, all semantics and “truest sense of the meaning” explanations aside, if the build is being made available for public testing, and the filename has the word “beta” in it, then that’s how I look upon it.
I fully understand your point there. Did not want to concince you to download and install, just to make my point about the “beta” here. Normally, “beta” marks a completely new development available for testing which in this case is not really true.
If there are problems that can not be solved by other means - why not try the beta. Things can’t get worse than a non-working application, or an they? :
Anyway it will be the officially released version soon, so there is no need to argue about anything, and I do see the point you are making as well. More or less a question of personal decision I should think.
The files are stored in the beta area area of avast!'s servers but it is a New pre-release build of avast [NOW 5.0.504] as indicated by Vlk’s post
Hi *,
we’ll soon be releasing a new build of avast 5 Free/Pro/IS. As usual, we’re making the build available for public testing before it’s officially released (so far the version number is 5.0.504).
Pro AV / IS: solved a compatibility issue with Acronis True Image
IS firewall: fixes for Internet Connection Sharing
IS firewall: Windows 2000 compatibility
IS firewall: solved a compatibility problem with Logitech Desktop Manager
various fixes in the Outlook antispam add-in
fixes in ashUpd.exe
no crashing of AvastUi.exe anymore
This is a New pre-release build and should be installed if you are having a problem with avast!
Go to PROFILE then Modify Profile then Forum Profile Information then then update your Signature: with information like my signature as this helps the helpers offer pertinent advice.
I upgraded to v5.0.507 on one machine and will get the other one shortly.
I will definitely report back to this thread as to whether or not this updating issue gets fixed.
To reiterate, the only real problem has been with trying to manually update when I know that an update is available.
In most cases, that has been impossible, and only a reboot (sometimes) fixes it, or a day change (always) will install the new day’s update.
