24.02.2005 13:22:43 general: Started: 24.02.2005, 13:22:43
24.02.2005 13:22:43 general: Running setup_av_pro-225 (549)
24.02.2005 13:22:43 system: Operating system: Windows2000 ver 5.0, build 2195, sp 4.0 [Service Pack 4]
24.02.2005 13:22:43 system: Computer WinName: WQOMAIN
24.02.2005 13:22:43 system: Windows Net User: WQOMAIN\wqo
24.02.2005 13:22:43 general: Cmdline: /setproxy
24.02.2005 13:22:43 general: Operation set to INST_OP_PROXYDLG
24.02.2005 13:22:43 general: Old version: 225 (549)
24.02.2005 13:22:43 general: SGW32P::CheckIfInstalled set m_bAlreadyInstalled to 1
24.02.2005 13:22:43 internet: SYNCER: Type: 0
24.02.2005 13:22:43 internet: SYNCER: Auth: 0
24.02.2005 13:22:44 package: Part prg_av_pro-225 is installed
24.02.2005 13:22:44 package: Part vps-50601 is installed
24.02.2005 13:22:44 package: Part news-42 is installed
24.02.2005 13:22:44 package: Part setup_av_pro-225 is installed
24.02.2005 13:22:44 general: Old version: 225 (549)
24.02.2005 13:22:46 general: Connection test
24.02.2005 13:22:46 internet: SYNCER: Type: 0
24.02.2005 13:22:46 internet: SYNCER: Auth: 0
24.02.2005 13:22:46 general: progress thread start
24.02.2005 13:22:46 general: progress start - 1
24.02.2005 13:22:46 general: Server definition file for 'main' (d:\Program\Avast4\Setup\servers.def) is invalid.
24.02.2005 13:22:46 general: progress end - 0
24.02.2005 13:22:46 general: progress thread end
And to everyone asking questions:
I have the new servers.def downloaded from website.
This is NOT an issue around firewalls/proxy, don’t even suggest my firewall is blocking anything.
The file looks fine to me. When my connection died in the great thunderstorm, Avast Updater invalidated all servers itself and now refuses to get them back.
Probably clutching at straws here, but if you renamed servers.dat to serversdat.old say and try a repair of avast. Add Remove programs, avast! Anti-Virus, Change/Remove button and scroll down to Repair, click next and follow. You need to be on-line to do this.
This may or may not recognise the missing servers.dat file and may or may not replace/restore it.
I’m sure that one of the Alwil team will have the definitive answer.
Download proper servers.def e.g. from here: http://www.avast.com/iavs4x/servers.def (right-click the link and select Save As, otherwise it will open in your browser as a text file) and place it to the \setup directory.
Did that, checked everything else, took out regedit to wipe registry clean and reinstalled everything. The uninstaller was broken too but Avast is not to blame for that.
It is working but it is a little bit drastic and probably too hard for Joe User in average.
What is needed is a kind of integrity check for the installation, a kind of selftest to make sure all files are on the right place and the registry is not tampered with. With growing popularity, we can just wait to find viruses trying to delete Avast as is done with NAV and other older software.
Such a check is indeed present (and I believe it’s even more extensive than in other antiviruses)
(though I’m not completely sure if servers.def isn’t excluded from the check (for a reason)). However, if even the module responsible for the self-check/repair gets corrupted (which is the “setup” part in this case), there’s hardly anything to do.
Just a note: if a virus is activated and runs with administrator privileges, there is nothing that could prevent it from deactivating the antivirus (if the virus is targetted to deactivate this particular AV).