Cannot update program files: Error during D/L & Install

[CitizenOfTheWorld]

OK, I have auto updates off.  Here are the text cues I receive when attempting to manually update:

"Current Version:  5.1.864"

"A new version of the program is available! Latest program version: 5.1.889"

Then once i click the "Update Program" button I receive:

"Last encountered error: The system cannot find the file specified."
"Total time 2s"

The info is much like saying "I need to find a particular human." and then nothing else...

Obviously, My question is: "Which file?"

OS: Windows XP Pro 32bit

TIA

[Silk0]

Hmmm... Remove the actual version and install by this links of the 1st post. http://forum.avast.com/index.php?topic=69305.0
Didn't find such problem on my update procedure [avast! 5.1.884 Pr => avast 5.1.889]..

[CraigB]

It took me a couple of attempt's to get it to work but it did eventually, first attempt i got the error then staight away i tried again and it worked
If you do decide to download the new copy there is no need to delet your existing, just install over the top.

[Gopher John]

I had the same error trying to update 5.1.884 to 5.1.889, trying several times for about an hour.  Finally, I downloaded the 5.1.889 installer from http://download833.avast.com/iavs5x/setup_av_free_eng.exe and did an overinstall in a Administrator account.  I now have Avast Free 5.1.889 installed, all shields are working(except Mail Shield which I've disabled some while ago).  Did a Quick Scan, and then a Boot Scan.

Before all this, the definitions updated to 110113-0.  Now with 5.1.889, I get the same "Last encountered error: The system cannot find the file specified." when I manually check for VPS updates.

I'm wondering if some of the Avast servers are misconfigured.

[Vlk]

Please send me the setup.log file from the <avast>\setup directory.

Thanks
Vlk

PS I think it's related to the update from a beta build (or is anyone here experiencing the same problem when upgrading from a release build? - i.e. 5.1.864 or 5.0.677). There are some files that have same names in both beta and release builds, and this may cause some confusion to the updater. If my hypothesis is correct, it will correct itself with the next virus defs update, due in a few hours.

[Gopher John]

Vlk,

I've sent my setup.log to your email address.  Hopefully, it will help.  Also, I did attempt a repair via Add/Remove Programs, to no avail.

[darkwolf]

I just tried again with my current version, 5.1.864, it came up at 2s as server.def. Cannot find the file. I am downloading 5.1.889 and will install over 5.1.864. Installing worked well, but could not update, or say up to date.
Error message as follows:

Last encountered error: The system Cannot find the file specified.
Total time: 7s

servers.def.vpx    was found
servers.def        was not found

Looks like this is at the server end of the connection

[jwall]

With a clean install, I get this if Direction Connection is checked.
Auto connect works ok.

[pcguy]

I have 5.1.884 yet Avast is showing that there is a new version of the software 5.1.864. Also have defn a318mp.avast.com

[DavidR]

@ pcguy
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. This has in the past resolved this out of sync issue between reported and actual VPS version. You may need to reboot after the repair.

[pcguy]

Made no difference here on XP. Same problems

[Gopher John]

With a clean install, I get this if Direction Connection is checked.
Auto connect works ok.

Jwall, you hit the nail on the head.  Even after two repairs of avast 5.1.889, I got the same error.  When VPS 110113-1 became available, Avast was aware of the update, but wouldn't update.

In Avast Settings | Updates under Proxy Settings, I had Direct Connection checkmarked.  On changing it to Auto detect (use Internet Explorer settings), avast updated the VPS.  With Auto Detect Proxy, avast now tells me that I am running the latest program and VPS version.  There are no proxy settings in Internet Explorer at all, and direct connection (no proxy) has worked in all previous versions of Avast, including v4.x.

[jwall]

With a clean install, I get this if Direction Connection is checked.
Auto connect works ok.

Jwall, you hit the nail on the head.  Even after two repairs of avast 5.1.889, I got the same error.  When VPS 110113-1 became available, Avast was aware of the update, but wouldn't update.

In Avast Settings | Updates under Proxy Settings, I had Direct Connection checkmarked.  On changing it to Auto detect (use Internet Explorer settings), avast updated the VPS.  With Auto Detect Proxy, avast now tells me that I am running the latest program and VPS version.  There are no proxy settings in Internet Explorer at all, and direct connection (no proxy) has worked in all previous versions of Avast, including v4.x.

Thanks,
I know, go figure.

[DavidR]

If at any time you had a proxy determined in the Internet Explorer settings, then direct connection may well fail, usually it is the reverse where the Auto detect fails and changing to Direct connection (no proxy) is the solution

[Gopher John]

If at any time you had a proxy determined in the Internet Explorer settings, then direct connection may well fail, usually it is the reverse where the Auto detect fails and changing to Direct connection (no proxy) is the solution

I've never had a proxy in Internet Explorer settings.  Only with this 5.1.889 update did Direct Connection setting cause problems with Avast, and it started occurring during the GUI update from 5.1.884 PR.