My PC: Windows XP SP2, Pentium D processor at 3.0Ghz, 2GB of RAM, DSL connection. Avast Home Edition. For the past few days, I have been getting red pop-up windows from Avast, which is highly unusual for me. The last time I had problems with Avast, the system clock was incorrect. But that is not the issue this time. Here is what the system logs report:
An error has occured while attempting to update. Please check the logs. Function setifaceUpdatePackages() has failed. Return code is 0x00000002, dwRes is 00000002.
Basically, check the log files (or post the last 100 lines of the logs):
C:\Program Files\Alwil Software\Avast4\DATA\log\Setup.log
C:\Program Files\Alwil Software\Avast4\Setup\setup.log
Also check:
If your subscription allows the update right now (i.e., if it is not expired). Home (free) version need registering each 14 months.
I hope you haven’t bought a license from a site on this list: http://www.avast.com/eng/fraudulent-sales-of-avast-products.html
If your firewall settings and allow avast.setup to connect.
If you’re not sure, just turn off your firewall (to be sure the update failure is not due to it).
Maybe you should ‘remove’ avast.setup entry, try to update, receiving a new alert from the firewall, allowing it and checking it to remember.
Check your proxy settings into avast!:
Left click the avast icon > Settings
Update (Basic) > Details > Proxy
Make sure your browser is not set to “Work Offline” (this option is generally in the File menu).
If it doesn’t help, try switching from “Auto-detect” to “No proxy” (I’m assuming you’re not connecting to the Internet via proxy).
You can run proxycfg -d in a DOS window to make your computer connect direct, without proxy. You can run proxycfg -h for help.
Also you can try changing update service’s login account, follow this:
Open services control panel (e.g. Start->Run, and type: services.msc
Double-click on avast! iAVS4 Control Service to show properties. Switch to LogOn page.
Enter administrator account name and password.
Do the same for avast! Antivirus service.
Then start update again.
The last option, check if the servers.def file is corrupt or 0KB (C:\Program Files\Alwil Software\Avast4\Setup\servers.def).
You can try and download the servers.def file, http://files.avast.com/iavs4x/servers.def and replace the one in the avast setup folder.
Thanks for the response. I don’t believe any of your suggestions regarding the cause of these error messages are applicable to me. I’ve been using Avast for years, and 99.9% of the time, it runs just perfectly. My expiration does not expire until July of next year, and the Windows Firewall and Avast have always worked fine together. I did visit Add/Remove programs, and ran Avast’s ‘repair’ tool, just for the heck of it.
Here is the info from my C:\Program Files\Alwil Software\Avast4\DATA\log\Setup.log. Personal info has been edited out:
11.04.2007 15:38:16.000 1176320296 general Started: 11.04.2007, 15:38:16
11.04.2007 15:38:16.000 1176320296 general Running setup_av_pro-3ae (942)
11.04.2007 15:38:16.000 1176320296 system Operating system: WindowsXP ver 5.1, build 2600, sp 2.0 [Service Pack 2]
11.04.2007 15:38:16.000 1176320296 system Computer WinName: *******************
11.04.2007 15:38:16.000 1176320296 system Windows Net User: ****
11.04.2007 15:38:16.000 1176320296 general Cmdline: /sfx /sfxstorage "C:\DOCUME~1*~1\LOCALS~1\Temp_av_sfx.tm~a01152" /srcpath "C:\Documents and Settings*\Desktop"
11.04.2007 15:38:16.000 1176320296 general DldSrc set to sfx
11.04.2007 15:38:16.000 1176320296 general Old version: ffffffff (-1)
11.04.2007 15:38:16.000 1176320296 general Install check: SetupVersion does NOT exist
11.04.2007 15:38:16.000 1176320296 general SGW32P::CheckIfInstalled set m_bAlreadyInstalled to 0
11.04.2007 15:38:16.000 1176320296 registry Get registry: Software\Microsoft\Internet Explorer\Version=7.0.5730.11
11.04.2007 15:38:16.000 1176320296 general Operation set to INST_OP_INSTALL
11.04.2007 15:38:16.000 1176320296 general GUID: e78636c7-240b-4ffb-ad0c-ba29b56b6585
11.04.2007 15:38:16.000 1176320296 general SelectCurrent: selected server ‘tmp sfx storage’ from ‘sfx’
11.04.2007 15:38:16.000 1176320296 package GetPackages - set proxy for inet
11.04.2007 15:38:16.000 1176320296 internet SYNCER: Type: use IE settings
11.04.2007 15:38:16.000 1176320296 internet SYNCER: Auth: another authentication, use WinInet
11.04.2007 15:38:20.000 1176320300 package Load C:\DOCUME~1********~1\LOCALS~1\Temp_av_sfx.tm~a01152\prod-av_pro.vpu
11.04.2007 15:38:20.000 1176320300 package LatestPartInfo: news = news-4b
11.04.2007 15:38:20.000 1176320300 package LatestPartInfo: program = prg_av_pro-3ae
11.04.2007 15:38:20.000 1176320300 package LatestPartInfo: setup = setup_av_pro-3ae
11.04.2007 15:38:20.000 1176320300 package LatestPartInfo: vps = vps-70301
11.04.2007 15:38:20.000 1176320300 package Part prg_av_pro-3ae was set to be installed
11.04.2007 15:38:20.000 1176320300 package Part vps-70301 was set to be installed
11.04.2007 15:38:20.000 1176320300 package Part news-4b was set to be installed
11.04.2007 15:38:20.000 1176320300 package Part setup_av_pro-3ae was set to be installed
11.04.2007 15:38:20.000 1176320300 package FilterOutExistingFiles: 144 & 0 = 144
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: setif_av_pro-3ae.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: setif_av_pro-3ae.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: setup_av_pro-3ae.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: setup_av_pro-3ae.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_core-360.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_core-360.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_dll409-158.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_dll409-158.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_hlp409-28a.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_hlp409-28a.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_skins-13.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_skins-13.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: avscan-276.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: avscan-276.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: winsys-2.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: winsys-2.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: winsysgui-2.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: winsysgui-2.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: vps-70300.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: vps-70300.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: vpsm-70301.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: vpsm-70301.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: news409-32.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: news409-32.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package FilterOutExistingFiles: 144 & 0 = 144
11.04.2007 15:38:20.000 1176320300 package FilterOutExistingFiles: 143 & 0 = 143
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: setif_av_pro-3ae.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: setif_av_pro-3ae.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: setup_av_pro-3ae.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: setup_av_pro-3ae.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_core-360.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_core-360.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_dll409-158.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_dll409-158.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_hlp409-28a.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_hlp409-28a.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_skins-13.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_skins-13.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: avscan-276.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: avscan-276.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: winsys-2.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: winsys-2.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: winsysgui-2.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: winsysgui-2.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: vps-70300.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: vps-70300.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: vpsm-70301.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: vpsm-70301.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: news409-32.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: news409-32.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package FilterOutExistingFiles: 143 & 0 = 143
11.04.2007 15:38:20.000 1176320300 package FilterOutExistingFiles: 144 & 0 = 144
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: setif_av_pro-3ae.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: setif_av_pro-3ae.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: setup_av_pro-3ae.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: setup_av_pro-3ae.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_core-360.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_core-360.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_dll409-158.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_dll409-158.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_hlp409-28a.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_hlp409-28a.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_skins-13.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: av_pro_skins-13.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: avscan-276.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: avscan-276.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: winsys-2.vpu - not okay
11.04.2007 15:38:20.000 1176320300 package IsFullOkay: winsys-2.vpu - not okay
@ TacoSteve
When are there errors occurring, shortly after boot, when ?
Are you able to do a manual update ?
If so I suggest you do manual program update as it would appear you are running 4.7.942, which is two program updates behind. Improvements to 4.7.981 and 4.7.986 modified the priority of the update process, this is said to improve/eliminate these error shortly after boot.
I believe these pop-up error messages occur after a reboot. Yes, I have done a manual update, and am now using version 4.7.986. I can't help but think this is a glitch on Avast's end, but I could be wrong.
If you check the avast! Log Viewer (right click the avast icon), Warning or Errors section, or the log (you previously posted extracts from) is there anything there relating to it ?
You could reboot now you have the latest version and see if it resolves the problem ?
If not you could edit the avast4.ini file, [InetWD] section, add the following line if it isn’t present, AlwaysConnectedWaitSeconds=60 (for broadband connections) or RASWaitSeconds=120 (for sial-up connections). See example below, both these values wouldn’t be present at the same time obviously. The figure is in seconds and you can set your own duration to wait before checking for updates. This allows time for a connection to be fully established.
If you check the avast! Log Viewer (right click the avast icon), Warning or Errors section, or the log (you previously posted extracts from) is there anything there relating to it ?
In the ‘Warnings’ tab, just the same messages about being unable to update.
You could reboot now you have the latest version and see if it resolves the problem ?
I got the red pop-up warning from Avast again today. So I decided to uninstall Avast. I then rebooted, deleted some references to Alwil in the registry and Windows Explorer, did a Disk Defrag, rebooted, and re-installed Avast again.
So, we’ll see what happens now.
I have another computer in the other room, with almost the same configuration, also using Avast Home Edition. It only had a problem with updating once, on April 7th. So maybe this problem was with this PC.
At first I thought this happened only upon rebooting, but it seems to occur at other times too. I’m using Windows Firewall.
Per earlier instructions in this thread, I downloaded and inserted the jollyroger.vpu file and placed it in the Avast4/setup folder, replacing the earlier one. I’m skeptical, but maybe that can help.
Basically, check the log files (or post the last 100 lines of the logs):
C:\Program Files\Alwil Software\Avast4\DATA\log\Setup.log
C:\Program Files\Alwil Software\Avast4\Setup\setup.log
Also check:
If your subscription allows the update right now (i.e., if it is not expired). Home (free) version need registering each 14 months.
I hope you haven’t bought a license from a site on this list: http://www.avast.com/eng/fraudulent-sales-of-avast-products.html
If your firewall settings and allow avast.setup to connect.
If you’re not sure, just turn off your firewall (to be sure the update failure is not due to it).
Maybe you should ‘remove’ avast.setup entry, try to update, receiving a new alert from the firewall, allowing it and checking it to remember.
Check your proxy settings into avast!:
Left click the avast icon > Settings
Update (Basic) > Details > Proxy
Make sure your browser is not set to “Work Offline” (this option is generally in the File menu).
If it doesn’t help, try switching from “Auto-detect” to “No proxy” (I’m assuming you’re not connecting to the Internet via proxy).
You can run proxycfg -d in a DOS window to make your computer connect direct, without proxy. You can run proxycfg -h for help.
Also you can try changing update service’s login account, follow this:
Open services control panel (e.g. Start->Run, and type: services.msc
Double-click on avast! iAVS4 Control Service to show properties. Switch to LogOn page.
Enter administrator account name and password.
Do the same for avast! Antivirus service.
Then start update again.
The last option, check if the servers.def file is corrupt or 0KB (C:\Program Files\Alwil Software\Avast4\Setup\servers.def).
You can try and download the servers.def file, http://files.avast.com/iavs4x/servers.def and replace the one in the avast setup folder.
