Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: TacoBellSteve on April 27, 2007, 03:06:38 AM
-
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:
1) 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
Also, bad jollyroger.vpu file could contain banned registration keys with error and then update fails because of an invalid key. See how to download a new jollyroger.vpu, http://forum.avast.com/index.php?topic=27185.msg222148#msg222148.
2) 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.
3) 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.
4) 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.
5) 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
-
I don't believe any of your suggestions regarding the cause of these error messages are applicable to me.
Do you use Spyware Doctor?
-
@ 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 don't believe any of your suggestions regarding the cause of these error messages are applicable to me.
Do you use Spyware Doctor?
No. I use Windows Defender as my real-time anti-spyware monitor, as well as Spybot S&D, Ad-Aware SE, and SpywareBlaster.
-
@ 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.
[InetWD]
RASWaitSeconds=120
AlwaysConnectedWaitSeconds=60
-
**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 ?**
We'll see.
-
I note that you decided to show us a part of your setup log from some time ago.
I have to wonder ... did this date in your log represented the first instance of the problem you are reporting?
I also note that date is the day immediately following Microsoft Tuesday for the month of April.
Has the error persisted every day at startup since then ... or did the problem just go away?
-
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.
-
Just got another red pop-up warning message from Avast. :'(
I would hate to have to use another AV. Avast has worked fine on my PC for years.
-
Just got another red pop-up warning message from Avast. :'(
When does this occur, just avast making login? Any time?
Which firewall are you using?
-
When does this occur, just avast making login? Any time?
Which firewall are you using?
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:
1) 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
Again, bad jollyroger.vpu file could contain banned registration keys with error and then update fails because of an invalid key. See how to download a new jollyroger.vpu, http://forum.avast.com/index.php?topic=27185.msg222148#msg222148.
2) 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.
3) 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.
4) 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.
5) 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.
-
Are you able to update when you request an update manually?
-
I can do a manual update with no error message.
-
Perhaps you might be willing to perform a test. It may not eliminate your problem ... but it might give a pointer to the problem.
To perform the test:
Control Panel > Services set the "Automatic Updates" service to "Disabled".
Restart your system. Do you still get the error flag from avast at startup?
Please remember after the test to:
Control Panel > Services set the "Automatic Updates" service to "Automatic".
-
Control Panel > Services set the "Automatic Updates" service to "Disabled".
Restart your system. Do you still get the error flag from avast at startup?
Please remember after the test to:
Control Panel > Services set the "Automatic Updates" service to "Automatic".
If this is the problem, won't be enough just to change (check) the Services option in the Troubleshooting tab of settings?
-
The test should be done as I have advised.
-
The test should be done as I have advised.
Why?
-
Because your suggestion is far from achieving the test I intend.
-
What you are suggesting Tech would be removing a symptom rather than find the true cause I beileve. Now as has been suspected by Alan that these issues have a relationship with the windows update checks hogging resources and effectively locking everything else out and that is what I believe he is trying to test.
If by disabling the windows update service avast has no issues then we have a candidate for the real cause, but by using the trouble shooting workaround we wouldn't find that out.
-
Tech & David,
I suspect that there are more potential causes than the Windows Automatic Update function. I just want to eliminate it, if possible, in this case.
The avast Settings option, starting avast a few milliseconds later than other Windows services, is of no use whatsoever if you want to prevent Automatic Update running in competition with the avast automatic update.
What I find puzzling about this case (and why it may not be WAU here) is that this is a higher end system
and I have only ever been able to reproduce WAU conflicting with avast on a very much lower spec machine.
-
Thanks for the responses. I disabled Automatic Updates, and will leave it disabled until tomorrow afternoon. I should know by then whether that has made any differences. I have rebooted the computer, and no error message from Avast. However, this doesn't happen after every reboot.
As mentioned earlier, I've been using Avast for years and it has been one of the most trouble-free programs I've ever installed. Now everything is going to hell. LOL.
-
What you are suggesting Tech would be removing a symptom rather than find the true cause I beileve.
No. Vlk stated this as a 'solution' for logon troubles. It's on avast Troubleshooting settings.
Removing the symptoms will be anything that looses protection and only 'apparently' solves the problem.
It's not the case, in my opinion.
Now as has been suspected by Alan that these issues have a relationship with the windows update checks hogging resources and effectively locking everything else out and that is what I believe he is trying to test.
I understood... but he must post a little bit more... with half words - at that time - I couldn't talk or guess...
If by disabling the windows update service avast has no issues then we have a candidate for the real cause, but by using the trouble shooting workaround we wouldn't find that out.
Maybe we don't need to find out anything... just solve user's problem... helping the fast (straight) way.
-
Are you using Windows Defender on your system?
Thanks for running the test for a couple of days - as long you don't forget to set it back to Automatic by the second Tuesday in May.
I look forward to your feedback.
-
Yes, I am running Windows Defender.
-
I waited until about 10am this morning, and didn't get any error messages. However, I decided to go ahead and format my computer's hard drive. I have everything already backed up, so it wasn't too difficult. I have reinstalled Avast, with the same providers. Only difference is that I did not install Windows Defender. Instead, I will use WinPatrol.
If I encounter another red pop-up error message in the next day or so, I'll post it here.
2:45pm ET update: I got the dreaded pop-up error message again. Sigh.
-
The reason I asked about Windows Defender is that it too use the Windows Automatic Update service to manage its updates. If I am right about WAU playing a role in compromising the ability of avast to get its update done then having that extra use of WAU would make the interference more likely.
-
I doubt Windows Defender is the culprit, for two reasons:
1) Windows Defender and Avast have co-existed on my computer quite peacefully for months with no trouble.
2) The last time I received the pop-up error message from Avast (this afternoon), I didn't have Windows Defender installed.
I have emailed Avast's tech department about this problem. If they have any ideas that solve this glitch, I'll post back here.
-
I did not say that Windows Defender was the problem at all.
I did say that Windows Defender causes Windows Automatic Update to run more than if you do not have Windows Defender installed and that increases any chance of a possible conflict between avast automatic update and Windows Automatic Update.
To be fair to the avast team. The vast majority of Windows users do have the Windows Automatic Update set to "automatic" and most avast users do not experience any problems with avast automatic updates.
Even those avast users who, like you, have the avast "red popup" problem at startup have mostly not experienced the problem with the red popup after their system has been up and running for a while and avast performs it later check for updates.
Quite a number of cases where the red popup has occurred have been diagnosed to issues that have been remedied by one or other of the "checks" that Tech has posted twice in this thread.
The net result is that this is a rather complex puzzle for the avast team and I doubt if they will be able to offer you an immediate, clear and satisfactory solution.
The test I asked you to perform does not prove that Windows Automatic Update is causing your avast automatic update problem - it would need a more controlled test - but it is indicative, I hope, to the avast team as they review this one.
-
To be fair to the avast team. The vast majority of Windows users do have the Windows Automatic Update set to "automatic" and most avast users do not experience any problems with avast automatic updates.
But a lot of users have delays caused by Windows Updates at any time...
Does anybody knows how to run them at low priority? How can we configure the specific svchost.exe of this service?
avast team? Vlk, Kubecj, any help for me?
-
****I did say that Windows Defender causes Windows Automatic Update to run more than if you do not have Windows Defender installed and that increases any chance of a possible conflict between avast automatic update and Windows Automatic Update.****
As I mentioned earlier, I did not have Windows Defender installed today, and yet the red-pop up error message from Avast appeared again. That would seem to rule out ANY role for Windows Defender in this mystery.
-
As I mentioned earlier, I did not have Windows Defender installed today, and yet the red-pop up error message from Avast appeared again. That would seem to rule out ANY role for Windows Defender in this mystery.
I've posted a lot of 'solutions' for update problems... including the delay of update on login...
Did you follow them?
-
Tech,
unfortunately, when there are updates to be downloaded and Microsoft is throttling the load to protect their servers I have seen cases where Windows Update which often runs for a long period, can run for 10-15 minutes at system startup. So any delay that can be incurred by the avast4.ini setting often does not help in this case. I do not know if there is a maximum value to the delay setting - do you? If TacoSteve could try it set to 300 or 600 seconds it would be interesting to see if it eliminates the "red popup" at startup. Clearly though, it would do nothing to help the the same problem he is seeing when his system has been up and running for a while.
Since TacoSteve's automatic updates worked just fine with Windows Update disabled then it is hard to see how any of the other items on your list apply.
-
TacoSteve,
the error popup you saw today, was that at a system startup or after your system had been running for some time?
-
TacoSteve,
the error popup you saw today, was that at a system startup or after your system had been running for some time?
I think it was after the computer had been running for about 10 minutes.
-
I think it was after the computer had been running for about 10 minutes.
I see a relationship between this popup and Windows Update after login...
-
I'm getting the same problem with my dad's computer, except that it wouldn't update even manually. I would click either AVS or program update and nothing would happen except a avast.setup file would be created in the Setup folder each time I tried....so I ended up with avast.setup, avast.setup1, avast.setup2, avast.setup3 etc etc.
So this afternoon I uninstalled the current version using the uninstall program because the link in add/rem progs was broken. I reinstalled with a freshly downloaded version, then did a manual update. It worked properly, and downloaded approx 2.3 or so megs of VPS updates. I left it unattended and either did not leave a confirm message when it finished or automatically rebooted the system. At any rate, after the update took place, the manual update would again not function. I did a reboot and as soon as I connected to the internet again I got another red popup.
Any ideas?
-
There was an engine upgrade to Avast recently released, version 4.7.1001. This was downloaded and installed on my system this morning. Then I got the infamous red pop-up error message saying unable to update. Despite this, I was prompted to restart my computer to complete the installation, which I did.
I haven't received a response from Avast yet regarding this issue.
-
Please, post the last 100-150 files of avast log files:
C:\Program Files\Alwil Software\Avast4\DATA\log\Setup.log
C:\Program Files\Alwil Software\Avast4\Setup\setup.log
-
From C:Program Files/Alwil Software/Avast4\DATA\log\Setup.log. Avast has a limit of 10000 characters, so I can't post too much. Personal info blocked out:
30.04.2007 13:09:31.000 1177952971 general Started: 30.04.2007, 13:09:31
30.04.2007 13:09:31.000 1177952971 general Running setup_av_pro-3da (986)
30.04.2007 13:09:31.000 1177952971 system Operating system: WindowsXP ver 5.1, build 2600, sp 2.0 [Service Pack 2]
30.04.2007 13:09:31.000 1177952971 system Computer WinName: E510MAIN
30.04.2007 13:09:31.000 1177952971 system Windows Net User: E510MAIN\*************
30.04.2007 13:09:31.000 1177952971 general Cmdline: /sfx /sfxstorage "C:\DOCUME~1\*********~1\LOCALS~1\Temp\_av_sfx.tm~a02968" /srcpath "C:\Documents and Settings\************\Desktop"
30.04.2007 13:09:31.000 1177952971 general DldSrc set to sfx
30.04.2007 13:09:31.000 1177952971 general Old version: ffffffff (-1)
30.04.2007 13:09:31.000 1177952971 general Install check: SetupVersion does NOT exist
30.04.2007 13:09:31.000 1177952971 general SGW32P::CheckIfInstalled set m_bAlreadyInstalled to 0
30.04.2007 13:09:31.000 1177952971 registry Get registry: Software\Microsoft\Internet Explorer\Version=7.0.5730.11
30.04.2007 13:09:31.000 1177952971 general Operation set to INST_OP_INSTALL
30.04.2007 13:09:31.000 1177952971 general GUID: 2b2b871b-88a8-4bfd-b823-0dbbe21534ca
30.04.2007 13:09:31.000 1177952971 general SelectCurrent: selected server 'tmp sfx storage' from 'sfx'
30.04.2007 13:09:31.000 1177952971 package GetPackages - set proxy for inet
30.04.2007 13:09:31.000 1177952971 internet SYNCER: Type: use IE settings
30.04.2007 13:09:31.000 1177952971 internet SYNCER: Auth: another authentication, use WinInet
30.04.2007 13:09:39.000 1177952979 package Load C:\DOCUME~1\**********~1\LOCALS~1\Temp\_av_sfx.tm~a02968\prod-av_pro.vpu
30.04.2007 13:09:39.000 1177952979 package LatestPartInfo: jrog = jrog-1
30.04.2007 13:09:39.000 1177952979 package LatestPartInfo: news = news-4b
30.04.2007 13:09:39.000 1177952979 package LatestPartInfo: program = prg_av_pro-3da
30.04.2007 13:09:39.000 1177952979 package LatestPartInfo: setup = setup_av_pro-3da
30.04.2007 13:09:39.000 1177952979 package LatestPartInfo: vps = vps-73402
30.04.2007 13:09:39.000 1177952979 package Part prg_av_pro-3da was set to be installed
30.04.2007 13:09:39.000 1177952979 package Part vps-73402 was set to be installed
30.04.2007 13:09:39.000 1177952979 package Part news-4b was set to be installed
30.04.2007 13:09:39.000 1177952979 package Part setup_av_pro-3da was set to be installed
30.04.2007 13:09:39.000 1177952979 package Part jrog-1 was set to be installed
30.04.2007 13:09:39.000 1177952979 package FilterOutExistingFiles: 144 & 0 = 144
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: setif_av_pro-3da.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: setif_av_pro-3da.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: setup_av_pro-3da.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: setup_av_pro-3da.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: av_pro_core-38a.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: av_pro_core-38a.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: av_pro_dll409-164.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: av_pro_dll409-164.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: av_pro_hlp409-2a9.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: av_pro_hlp409-2a9.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: av_pro_skins-13.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: av_pro_skins-13.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: avscan-299.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: avscan-299.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: winsys-2.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: winsys-2.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: winsysgui-2.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: winsysgui-2.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: vps-73400.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: vps-73400.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: vpsm-73402.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: vpsm-73402.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: news409-32.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: news409-32.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: jrog-1.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: jrog-1.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package FilterOutExistingFiles: 144 & 0 = 144
30.04.2007 13:09:39.000 1177952979 package FilterOutExistingFiles: 143 & 0 = 143
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: setif_av_pro-3da.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: setif_av_pro-3da.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: setup_av_pro-3da.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: setup_av_pro-3da.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: av_pro_core-38a.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: av_pro_core-38a.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: av_pro_dll409-164.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: av_pro_dll409-164.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: av_pro_hlp409-2a9.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: av_pro_hlp409-2a9.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: av_pro_skins-13.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: av_pro_skins-13.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: avscan-299.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: avscan-299.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: winsys-2.vpu - not okay
30.04.2007 13:09:39.000 1177952979 package IsFullOkay: winsys-2.vpu - not okay
-
From C:\Program Files\Alwil Software\Avast4\Setup\setup.log:
13:09:31 min/gen Started: 30.04.2007, 13:09:31
13:09:31 min/gen Running setup_av_pro-3da (986)
13:09:31 nrm/sys Operating system: WindowsXP ver 5.1, build 2600, sp 2.0 [Service Pack 2]
13:09:31 vrb/sys Computer WinName: E510MAIN
13:09:31 min/sys Windows Net User: E510MAIN\**************
13:09:31 min/gen Cmdline: /sfx /sfxstorage "C:\DOCUME~1\*************1\LOCALS~1\Temp\_av_sfx.tm~a02968" /srcpath "C:\Documents and Settings\*************\Desktop"
13:09:31 vrb/gen DldSrc set to sfx
13:09:31 min/gen Old version: ffffffff (-1)
13:09:31 vrb/gen Install check: SetupVersion does NOT exist
13:09:31 nrm/gen SGW32P::CheckIfInstalled set m_bAlreadyInstalled to 0
13:09:31 vrb/reg Get registry: Software\Microsoft\Internet Explorer\Version=7.0.5730.11
13:09:31 vrb/gen Operation set to INST_OP_INSTALL
13:09:31 min/gen GUID: 2b2b871b-88a8-4bfd-b823-0dbbe21534ca
13:09:31 nrm/gen SelectCurrent: selected server 'tmp sfx storage' from 'sfx'
13:09:31 min/pkg GetPackages - set proxy for inet
13:09:31 nrm/int SYNCER: Type: use IE settings
13:09:31 nrm/int SYNCER: Auth: another authentication, use WinInet
13:09:39 min/pkg Load C:\DOCUME~1\***********1\LOCALS~1\Temp\_av_sfx.tm~a02968\prod-av_pro.vpu
13:09:39 vrb/pkg LatestPartInfo: jrog = jrog-1
13:09:39 vrb/pkg LatestPartInfo: news = news-4b
13:09:39 vrb/pkg LatestPartInfo: program = prg_av_pro-3da
13:09:39 vrb/pkg LatestPartInfo: setup = setup_av_pro-3da
13:09:39 vrb/pkg LatestPartInfo: vps = vps-73402
13:09:39 vrb/pkg Part prg_av_pro-3da was set to be installed
13:09:39 vrb/pkg Part vps-73402 was set to be installed
13:09:39 vrb/pkg Part news-4b was set to be installed
13:09:39 vrb/pkg Part setup_av_pro-3da was set to be installed
13:09:39 vrb/pkg Part jrog-1 was set to be installed
13:09:39 vrb/pkg FilterOutExistingFiles: 144 & 0 = 144
13:09:39 vrb/pkg IsFullOkay: setif_av_pro-3da.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: setif_av_pro-3da.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: setup_av_pro-3da.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: setup_av_pro-3da.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_core-38a.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_core-38a.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_dll409-164.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_dll409-164.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_hlp409-2a9.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_hlp409-2a9.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_skins-13.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_skins-13.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: avscan-299.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: avscan-299.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: winsys-2.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: winsys-2.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: winsysgui-2.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: winsysgui-2.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: vps-73400.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: vps-73400.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: vpsm-73402.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: vpsm-73402.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: news409-32.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: news409-32.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: jrog-1.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: jrog-1.vpu - not okay
13:09:39 vrb/pkg FilterOutExistingFiles: 144 & 0 = 144
13:09:39 vrb/pkg FilterOutExistingFiles: 143 & 0 = 143
13:09:39 vrb/pkg IsFullOkay: setif_av_pro-3da.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: setif_av_pro-3da.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: setup_av_pro-3da.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: setup_av_pro-3da.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_core-38a.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_core-38a.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_dll409-164.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_dll409-164.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_hlp409-2a9.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_hlp409-2a9.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_skins-13.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_skins-13.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: avscan-299.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: avscan-299.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: winsys-2.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: winsys-2.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: winsysgui-2.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: winsysgui-2.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: vps-73400.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: vps-73400.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: vpsm-73402.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: vpsm-73402.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: news409-32.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: news409-32.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: jrog-1.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: jrog-1.vpu - not okay
13:09:39 vrb/pkg FilterOutExistingFiles: 143 & 0 = 143
13:09:39 vrb/pkg FilterOutExistingFiles: 144 & 0 = 144
13:09:39 vrb/pkg IsFullOkay: setif_av_pro-3da.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: setif_av_pro-3da.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: setup_av_pro-3da.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: setup_av_pro-3da.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_core-38a.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_core-38a.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_dll409-164.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_dll409-164.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_hlp409-2a9.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_hlp409-2a9.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_skins-13.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_skins-13.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: avscan-299.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: avscan-299.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: winsys-2.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: winsys-2.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: winsysgui-2.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: winsysgui-2.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: vps-73400.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: vps-73400.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: vpsm-73402.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: vpsm-73402.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: news409-32.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: news409-32.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: jrog-1.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: jrog-1.vpu - not okay
13:09:39 vrb/pkg FilterOutExistingFiles: 144 & 0 = 144
13:09:39 vrb/gen Operation set to INST_OP_INSTALL
13:09:39 vrb/pkg FilterOutExistingFiles: 144 & 0 = 144
13:09:39 vrb/pkg IsFullOkay: setif_av_pro-3da.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: setif_av_pro-3da.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: setup_av_pro-3da.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: setup_av_pro-3da.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_core-38a.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_core-38a.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_dll409-164.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_dll409-164.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_hlp409-2a9.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_hlp409-2a9.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_skins-13.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: av_pro_skins-13.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: avscan-299.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: avscan-299.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: winsys-2.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: winsys-2.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: winsysgui-2.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: winsysgui-2.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: vps-73400.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: vps-73400.vpu - not okay
13:09:39 vrb/pkg IsFullOkay: vpsm-73402.vpu - not okay
-
TacoSteve, I see no error message in your log...
It's beyond my knowledge. You'll need to ask for Alwil team help :-[
-
Thanks to all who tried to help. I am reluctantly going to uninstall Avast right now and try AVG free.
-
13:09:31 min/gen Cmdline: /sfx /sfxstorage "C:\DOCUME~1\*************1\LOCALS~1\Temp\_av_sfx.tm~a02968" /srcpath "C:\Documents and Settings\*************\Desktop"
Did you change this line to the asterisks content or it's like in setup log file?
Hope that Alwil team drop a word of help here...
-
I added the ************ because they had my name in them.
-
I added the ************ because they had my name in them.
Ok. Right now, does the problem is only on update or you can't use avast at all?
By the way, does this could help?
http://forum.avast.com/index.php?topic=28102.msg229764#msg229764
-
I do not want to try to speak for TacoSteve but the consistent problem he has reported is the "red popup" at system startup when avast fails its VPS update checks. This problem stopped for a while when he disabled the Windows Automatic Update service and returned after (I recall) he formatted his hard drive and performed a system restore. The problem continues with the latest version (1001). The logs he most recently posted are full of many "not okay" lines that do not show up in my log and I suspect not in yours.
The errors in TacoSteve's log are very different from the errors shown in the log for those experiencing the "short names" problem so I have to believe the TacoSteve is experiencing a different root cause.
A great pity that the avast team have not the time to make a comment.
-
I added the ************ because they had my name in them.
Ok. Right now, does the problem is only on update or you can't use avast at all?
The only problem was the update error message. Other than that, Avast seemed to work fine. I'm using AVG 7.5 right now. One nice thing about this program is that you can control when it checks for updates.