Error on pc startup.

[hellraiser]

On booting my pc I get a red box in right hand corner informing me an error occured whilst trying to update.
this is the log.

5/7/2007 07:11:32   SYSTEM   560   Function setifaceUpdatePackages() has failed. Return code is 0x00000002, dwRes is 00000002. 
5/7/2007 07:11:33   SYSTEM   560   An error has occured while attempting to update. Please check the logs. 
5/7/2007 09:52:57   SYSTEM   484   Function setifaceUpdatePackages() has failed. Return code is 0x00000002, dwRes is 00000002. 
5/7/2007 09:52:59   SYSTEM   484   An error has occured while attempting to update. Please check the logs. 
5/8/2007 07:27:49   SYSTEM   444   Function setifaceUpdatePackages() has failed. Return code is 0x00000002, dwRes is 00000002. 
5/8/2007 07:27:49   SYSTEM   444   An error has occured while attempting to update. Please check the logs. 
5/8/2007 08:09:14   SYSTEM   432   Function setifaceUpdatePackages() has failed. Return code is 0x00000002, dwRes is 00000002. 
5/8/2007 08:09:15   SYSTEM   432   An error has occured while attempting to update. Please check the logs. 
5/8/2007 12:34:14   SYSTEM   464   Function setifaceUpdatePackages() has failed. Return code is 0x00000002, dwRes is 00000002. 
5/8/2007 12:34:15   SYSTEM   464   An error has occured while attempting to update. Please check the logs. 
5/8/2007 13:26:05   SYSTEM   452   Function setifaceUpdatePackages() has failed. Return code is 0x00000002, dwRes is 00000002. 
5/8/2007 13:26:06   SYSTEM   452   An error has occured while attempting to update. Please check the logs. 
5/9/2007 16:30:30   SYSTEM   308   Function setifaceUpdatePackages() has failed. Return code is 0x00000002, dwRes is 00000002. 
5/9/2007 16:30:31   SYSTEM   308   An error has occured while attempting to update. Please check the logs. 
5/9/2007 16:36:53   SYSTEM   520   Function setifaceUpdatePackages() has failed. Return code is 0x00000002, dwRes is 00000002. 
5/9/2007 16:36:53   SYSTEM   520   An error has occured while attempting to update. Please check the logs. 
5/11/2007 16:00:25   SYSTEM   336   Function setifaceUpdatePackages() has failed. Return code is 0x00000002, dwRes is 00000002. 
5/11/2007 16:00:26   SYSTEM   336   An error has occured while attempting to update. Please check the logs. 
5/12/2007 12:38:50   SYSTEM   360   Function setifaceUpdatePackages() has failed. Return code is 0x00000002, dwRes is 00000002. 
5/12/2007 12:38:51   SYSTEM   360   An error has occured while attempting to update. Please check the logs. 
5/12/2007 13:31:36   SYSTEM   388   Function setifaceUpdatePackages() has failed. Return code is 0x00000002, dwRes is 00000002. 
5/12/2007 13:31:37   SYSTEM   388   An error has occured while attempting to update. Please check the logs. 
5/13/2007 06:37:51   SYSTEM   420   Function setifaceUpdatePackages() has failed. Return code is 0x00000002, dwRes is 00000002. 
5/13/2007 06:37:52   SYSTEM   420   An error has occured while attempting to update. Please check the logs. 
5/14/2007 15:10:00   SYSTEM   388   Function setifaceUpdatePackages() has failed. Return code is 0x00000002, dwRes is 00000002. 
5/14/2007 15:10:01   SYSTEM   388   An error has occured while attempting to update. Please check the logs. 
5/17/2007 12:43:23   SYSTEM   360   Function setifaceUpdatePackages() has failed. Return code is 0x00000002, dwRes is 00000002. 
5/17/2007 12:43:24   SYSTEM   360   An error has occured while attempting to update. Please check the logs. 
5/17/2007 16:38:52   SYSTEM   356   Function setifaceUpdatePackages() has failed. Return code is 0x00000002, dwRes is 00000002. 
5/17/2007 16:38:52   SYSTEM   356   An error has occured while attempting to update. Please check the logs. 
5/19/2007 10:31:46   SYSTEM   1112   Function setifaceUpdatePackages() has failed. Return code is 0x00000002, dwRes is 00000002. 
5/19/2007 10:31:47   SYSTEM   1112   An error has occured while attempting to update. Please check the logs. 
5/20/2007 08:07:29   SYSTEM   1092   Function setifaceUpdatePackages() has failed. Return code is 0x00000002, dwRes is 00000002. 
5/20/2007 08:07:30   SYSTEM   1092   An error has occured while attempting to update. Please check the logs. 

How may I resolve this problem.

[DavidR]

Well the windows error 2 = "The system cannot find the file specified. "

So it would appear there is a problem with a missing file, try a repair of avast. Add Remove programs, select 'avast! Anti-Virus,' click the Change/Remove button and scroll down to Repair, click next and follow. You need to be on-line to do this.

However, this could also be firewall blocking as this is a common reason for the Red Update error.

What is your firewall ?
Does it allow avast.setup internet access ?
- If it does delete the entries for them and do a manual update and reconnect to the internet, this will force the firewall to ask permission again.

[Lisandro]

Did you install avast in the default path? If not, which one did you choose?
When you installed avast, does the folder was there (not empty) or, on contrary, it was created by the installation package? In other words, did you install avast from the scratch?

[222fbj]

I have the same problem on a XPhome PC I maintain.   The software is installed on the default path...and has been working fine for about a month.

Is there a solution/advice?  What should I try to fix this error?
I looked in the knowledgebase - did not see anything.

thanks

[Lisandro]

What should I try to fix this error?

1. Uninstall avast from Control Panel first.
2. Boot.
3. Use Avast Uninstall for complete uninstallation.
4. Boot.
5. Install again the last 4.7.1001 version.
6. Boot.

[222fbj]

thanks for that uberfast reply.... I'll do it.

[Lisandro]

thanks for that uberfast reply.... I'll do it.

You're welcome. I've forgot step 7: post the results

[222fbj]

Step 7 - Results so Far....  still get an error at startup.  Log show the following errorsavastWedwarning.txt
5/20/2007 6:53:06 PM   SYSTEM   1940   Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004. 
5/20/2007 6:53:07 PM   SYSTEM   1940   An error has occured while attempting to update. Please check the logs. 
5/21/2007 4:32:55 AM   SYSTEM   1940   Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004. 
5/21/2007 4:32:56 AM   SYSTEM   1940   An error has occured while attempting to update. Please check the logs. 
5/21/2007 9:57:11 PM   SYSTEM   1940   Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004. 
5/21/2007 9:57:11 PM   SYSTEM   1940   An error has occured while attempting to update. Please check the logs. 
5/22/2007 4:33:03 AM   SYSTEM   1940   Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004. 
5/22/2007 4:33:04 AM   SYSTEM   1940   An error has occured while attempting to update. Please check the logs. 
5/22/2007 5:51:16 PM   SYSTEM   1940   Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004. 
5/22/2007 5:51:17 PM   SYSTEM   1940   An error has occured while attempting to update. Please check the logs.

[Lisandro]

still get an error at startup

Try changing (or adding) AlwaysConnectedWaitSeconds value into the [InetWD] section of avast4.ini file.
You could set the number of seconds to wait before attempting to update. The default is 30 but it may not be enough in some DSL systems. In this case, you can try increasing this e.g. to 60 (1 minute). That should be enough.
More details here: http://forum.avast.com/index.php?board=2;action=display;threadid=1647

[222fbj]

Thanks..I'll change the ini file and report back.

I'm curious...In program setup/troubleshooting there is an option to "Delay loading of avast! servcies..."   Should that only be used for troubleshooting - and left off at all other times?
Until I read your post, I was thinking of trying that.

thanks

[Lisandro]

I'm curious...In program setup/troubleshooting there is an option to "Delay loading of avast! servcies..."   Should that only be used for troubleshooting - and left off at all other times?

Yes, it's a troubleshooting option. You can test it as well.
They're there because the startup order of the services could block avast update and vice versa, could mess other updates like Windows Updates.

Alan's experience: This is especially true during Windows update week.  Windows automatic updates seem to hog resources even to just determine that updates do exist but you are just not allowed to download them yet (to prevent overload of Microsoft's servers).  So this is happening at every startup during the Windows update period until you have been permitted to download the updates.  Although I do not have "smoking gun" logs to prove it (a bit hard to get on an overloaded system at startup) I am reasonably certain that the Windows automatic update process, at this time, can prevent the avast automatic VPS update from getting timely access to it servers and causing avast to report an automatic update error - especially on older, less powerful systems.    This past week was Windows update week, some folks this week waited 4 or 5 days before being permitted to download the Windows updates through the automatic update process.

I suggest you first try my suggestion and then, if you have troubles, let the avast4.ini changed, it won't harm, and check that troubleshooting option. Boot and good luck

[alanrf]

I note with considerable interest that today I received an update from Microsoft that is designed to address some of the issues of the overhead (or resource hogging) of the windows update process.  It is reported that this is the first of two updates.

From the Microsoft site:

Today we are announcing the availability of an update that does not address a security vulnerability, but is a high priority for customers in keeping their systems updated. The update addresses the following issue:

Your system may appear to become unresponsive when Windows Update or Microsoft Update is scanning for updates that use Windows installer, and you may notice that the CPU usage for the svchost process is showing 100%.

When you try to install an update from Windows Update or from Microsoft Update, you experience the following symptoms:
•   

Your system may appear to become unresponsive when Windows Update or Microsoft Update is scanning for updates that use Windows Installer.
•   

You receive an access violation error in svchost.exe. This access violation stops the Server service and the Workstation service.
•   

A memory leak occurs when Windows Update or Microsoft Update is scanning for updates that use Windows Installer.
•   

Windows Update or Microsoft Update scans take a very long time, sometimes hours, to complete.

We encourage Windows customers to review and install this update. This update will be offered automatically through Automatic Updates. For more information about this issue, including download links for the available non-security update, please review Microsoft Knowledge Base Article 927891.

Please note that this update is the first part of a two-part fix that is the comprehensive solution to the problem. In June, another update will involve the Windows Update client. The update for the Windows Update client will also be automatically offered through Automatic Updates.

[Lisandro]

From the Microsoft site:
CPU usage for the svchost process is showing 100%.
Become unresponsive when Windows Update or Microsoft Update is scanning for updates that use Windows Installer.
Windows Update or Microsoft Update scans take a very long time

Thanks Alanrf, let's take an eye on this... seems promising...

[Lisandro]

Strange, the update mentioned in Microsoft Knowledge Base Article 927891 in Brazilian Portuguese (WindowsXP-KB927891-v3-x86-PTB.exe) was not offered to me automatically. It's not into my Update History...
I've downloaded the file and manually installed... I'll test if I could restore Windows Update to automatic mode.

[alanrf]

This was offered on automatically on another of my WinXP SP2 machines (my backup machine) yesterday.  It was installed.  On this machine I have the Windows automatic update service set to Automatic status and Windows Update to automatically download and await my OK to install.   

Today I brought the machine up and monitored the task manager as soon as possible after startup. It did appear to me, with just visual scanning that that the Windows update activity was less stressful.  The only services that exceed 60% CPU (on the non-Ferrari Intel P3 1Ghz processor) were avast services.

But this is early days, and, as you say Tech, something we should keep an eye on.  I think that the real test comes after part II next month.