I’ve been getting an error more than half the time when avast tries to update its virus data base after I turn on my PC. This problem started after the update two weeks ago to version 4.7.827. After the red pop-up error box, I click on details. In the red box I read, “Could not find file specified” (I DO NOT get a ‘server error’) I get ‘specified file not found’. After the error, I try to manually update and it updates perfectly. ???
The log viewer under warning shows:
“An error has occurred while attempting to update . Please check the logs”
Under that it says, "Function setifaceUpdatePackages() has failed. Return code is 0x00000002, …"
I’m thinking that avast is not waiting long enough in attempting to update after I boot up. Here’s why…
Today I carefully watched while booting up [I have a DSL - lite connection]. When the avast ball spun this morning, I never saw the light blink on my DSL modem (it did not access the internet). A couple of minutes later, I got the red pop-up error, “An error occurred while attempting to update. Plz check logs”. Avast seems to try to update Before ZoneAlarm is finished loading.
I have noticed on my system tray (after the latest update to 4.7.827) that avast is no longer the last thing to load - it’s now ZAP (Zone Alarm Pro). Maybe avast is trying to update before ZAP is ready to allow it? I think avast used to wait a full minute before updating with version 817. Maybe that’s no longer the default? Not sure.
What I’ve tried to correct this problem…
In my avast4.ini file under [InetWD] section I added “AlwaysConnectedWaitSeconds=60” (there was no entry there at all). Cleaned out all temp and temporary internet files (I do this regularly).
I have DSL Lite connection. Using Win98 SE; Zone Alarm Pro; IE-5.5 SP-2; OE-5.5 SP-2
Well “Could not find file specified” sounds like corruption or bad update previously.
The “Function setifaceUpdatePackages() has failed. Return code is 0x00000002, …” is a windows file system error - The system cannot find the file specified. Which basically reflects the above.
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.
If that doesn’t work try, uninstall, reboot, install, reboot.
It would probably be best to download the latest version of avast and save it to your HDD, somewhere you can find it again. Use that when you reinstall.
I failed to mention above that I already tried a ‘repair’ yesterday. I thought that maybe that did fix it too because I got a statement something to the effect, ‘repair was successful’.
It’s just strange that a manual update always works. It’s just the automatic update that fails sometimes. It’s not waiting the 60 seconds like I’ve put in the ini file. It’s like it ignores that value.
I guess I’ll have to try the ‘uninstall/reinstall’.
In conjunction with Tech’s question, you could also double-check what kind of connection you actually have.
My ISP and phone co. both offer what they call ‘DSL lite’ – they’re essentially just ordinary dialup but with server caching, data compression, and a few other tricks to speed downloads. Not DSL at all, despite the name.
Under update (connections) I have nothing ticked. This is the same setting I had with prior version of Avast (817). Maybe I should have ‘always connected’ selected? But - my settings for ZAP is to lock the internet connection when ever my screen saver comes up so I’m really not ‘always connected’.
To Mike…
My DSL lite is really DSL – but they slow it down for the $24 per month they charge. I get around 256K download speed at last test (a little faster than dialup). AND this connection requires filters to be installed on all my phones for non-interference. Also, my phone line is never busy.
Okay, I’ll give that a try. Neither ‘dial-up’ nor ‘always connected’ were ticked (selected). Not sure how it was working thus far. Must be a default thing.
Now that I think about it, the software was probably ignoring the ‘wait 60 seconds’ that I added to the ini file because ‘always connected’ wasn’t ticked!!
Thanks. I’ll change it… reboot… and let you all know how it goes.
After changing the choice to ‘always conncected’ and then rebooting, avast now waits 60 seconds before trying to update. After 60 seconds, ZAP is fully loaded and there shouldn’t be a problem. At least thus far there aren’t any errors.
My copy of avast updated this morning without any problem. The change in my “avast4.ini” file to wait 60 seconds and ‘always connected’ cured my intermittant error (red pop-up box).
That may not work as a default. I have a new problem…
As I said earlier, I have ZAP (ZoneAlarm Pro) as my firewall. I have it set to ‘Automatically engage internet lock’ when ever my screen saver comes up. If avast tries to update during this time, I get the red pop-up error, “Cannot connect to download12.avast.com (70.86.142.26:80) Total time 29:38”. I’ve given avast a ‘key’ to get past ZAP’s lock, but this doesn’t seem to work. Not only is there this error, but avast tries to connect for alomst 30 minutes. Since I leave my computer on most of the day, I’d hate to leave the internet ‘unlocked’ all of this time.
So the problem to me is this…
I need to have avast set to ‘always connected’ to allow avast to see the ‘wait 60 seconds’ command. BUT ‘always connected’ generates this new error when my firewall locks the internet.
I figured out what my problem was in not allowing avast to update through my firewall (ZAP) when the ‘Automatic internet lock’ engages (I have ZAP set to engage internet lock when screen saver come on). I had given a ‘pass key’ to ‘avast AV update module’ but failed to give a pass key also to ‘avast web scanner’. Using a proxy server so avast can do a webscan, it also needs an access key. DUH!
Sorry for any confusion. It updates just fine now when ZAP interlock is engaged. ;D
