Have used Avast for a good while on XP with no problems. Just bought new Vista (32 bit) machine, installed Avast ver 4.8.1335 only to find that auto updates don’t appear to happen. Have repaired and re-installed Avast but still the same. I’m able to manually update.
Only using Vista built in firewall (on which Avast is authorised)
Avast is configured to autoupdate out of the box, but mine does not. Auto update for both database and programme options are selected in options.
Any idea what’s going on here?? Where’s my auto updating gone?
Does the manual update work (right click the avast ‘a’ icon, select Updating, iAVS Update) ?
Are you getting any errors displayed ?
Check the avast! Log Viewer (right click the avast ‘a’ icon), Warning or Error sections. C:\Program Files\Alwil Software\Avast4\ashLogV.exe
Did this new system come pre-installed with any software ?
Typically a trial version of another anti-virus.
Thanks for the replies. proxy server settings are displayed as correct.
In the Avast event logger, I noticed the following entry, that might give some insight to the problem to the trained eye…
07/02/2009 14:26:37 SYSTEM 1872 Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.
07/02/2009 14:45:42 SYSTEM 1872 Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.
07/02/2009 18:41:14 SYSTEM 1916 Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.
What is in the avast log viewer ?
Check the avast! Log Viewer (right click the avast ‘a’ icon), Warning/Error sections.
C:\Program Files\Alwil Software\Avast4\ashLogV.exe
Here’s the contents of my avast log viewer…mean anything to anyone??
07/02/2009 14:26:37 SYSTEM 1872 Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.
07/02/2009 14:45:42 SYSTEM 1872 Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.
07/02/2009 18:41:14 SYSTEM 1916 Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.
07/02/2009 23:32:49 SYSTEM 1916 Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.
08/02/2009 07:41:49 SYSTEM 1924 Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.
08/02/2009 12:03:05 SYSTEM 1924 Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.
08/02/2009 16:24:18 SYSTEM 1924 Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.
08/02/2009 17:42:02 SYSTEM 1948 Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.
08/02/2009 22:02:57 SYSTEM 1948 Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.
09/02/2009 16:07:26 SYSTEM 1936 Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.
09/02/2009 16:58:28 SYSTEM 1936 Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.
09/02/2009 17:49:40 SYSTEM 1936 Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.
09/02/2009 18:41:02 SYSTEM 1936 Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.
09/02/2009 19:32:15 SYSTEM 1936 Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.
09/02/2009 20:23:22 SYSTEM 1936 Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.
09/02/2009 21:14:41 SYSTEM 1936 Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.
My question was directed to the other poster with this problem also.
@ dsmail
Since the manual update works, as Alan said it is unlikely to be firewall blocking.
In the avast program settings > Update (Connections) > Proxy, if you don’t use a proxy to connect, try setting it to 'Direct connection (no proxy) and see if that makes any difference.
Although, having said it is unlikely to be your firewall blocking what is your firewall ?
Some, comodo for one blocks all outbound connections until it is fully established, so this could have an effect depending on your firewall.
If that isn’t the case we could probably try delaying the auto update so it doesn’t happen too early.
If that doesn’t have any impact we can try delaying the update check, let us know how you get on.
The Vista firewall doesn’t have these complex options (as far as I’m aware), nor does it check outbound connections. By default the outbound checking is disabled - You could also enable the outbound protection of the Vista firewall, but it isn’t very friendly, is rule based and you have to create the rules. - Vista Firewall Control, check out this topic for some user friendly help for the Vista Firewall, Outbound protection, http://forum.avast.com/index.php?topic=30234.0
Still no auto update. Have reverted back to auto detect proxy settings. Have just manually updated virus database and that still works fine although I’d prefer the auto update of course. Any further ideas??
I still feel that you should leave it on Direct Connection as the auto detect checks IE for its proxy and if there is no proxy set this is just an additional step.
The problem is why you are getting these errors, which appear to be when the auto update is checking, yet the manual update works.
09/02/2009 21:14:41 SYSTEM 1936 Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004.
You can try the delay update check, but I don’t hold out that much hope it will work, but we will see.
You need to edit (using notepad) the [InetWD] section of the C:\Program Files\Alwil Software\Avast4\Data\avast4.ini file and add the following line (depending on your connection type enter one or other of the Bold lines below):
Dial-up connections, add this line: RASWaitSeconds=120
Broadband connections, add this line: AlwaysConnectedWaitSeconds=120
[InetWD]
AlwaysConnectedWaitSeconds=120
Or
RASWaitSeconds=120
When complete save the changes, avast’s self-defence module will ask for confirmation, etc. answer Yes.
The figure is seconds and the above equates to two minutes, you could try that and adjust upwards if required, 180, 240, etc.
Still no auto update. Have just done another manual one that worked fine as always. Looks like I’m stuck with this.
I’ll need to remember to manually update regularly.
I think that this is a problem with the latest Avast update.
I to have been using Avast for a while on vista 32. And since the last update (1335) I am now getting no visual or oral notification that Avast is updating. I have reinstalled Avast but still no joy.
Could this be an Avast problem?
Just to add to my previous post, I checked the log viewer, and there has been no Auto update since the last program update, I have just manually updated, but had to allow this through UAC on Vista.
Could UAC be blocking Automatic Updates? If so I think this is an issue Avast need to sort.