I started out with version 5.0.507.0 upgraded to Beta 5.0.542.0, and now I have upgraded to 5.0.545.0 (the latest).
Avast won´t update anything. It does not update automatic and it does not update when I´m setting it to manual and push the update button.
It says:
“Step 1/2
Initializing, please wait…”
…and nothing happens - nothing at all.
In the settings i´m set to “computer has a permanent connection”
The proxy is correct set to Direct (No Proxy).
I have disabled my firewall and I have shut down my firewall (comodo).
Cannot get the update to work.
My system is: Win XP, SP3.
And my date/time settings is correct.
Nope I just have one Firewall. I have Avast Antivirus and Comodo Firewall. I have set every instance of Avast as trusted. I have also disabled and totally shut down the firewall (comodo). But Avast wont update - so I don´t think it´s the firewall stopping Avast.
I don’t have CIS installed anymore but I had recently and the firewall never blocked Avast. Avast is first in the list of trusted vendors so no issue with Def+, all avast processes are allowed to connect (including avast.setup), either following an alert or automatically, depending on the firewall mode, so…the only (minor) issue that I know of is that avast.setup being generated temporarily, if you purge the firewall and def+ rules, its permissions will be removed.But it’s not blocked.You’re prompted again when needed.
I stand corrected. Here´s what I did (if someone else get the same problem);
I cleaned out all entries of Avast/Alwil in “Network Security Policy” in Comodos Advanced Firewall settings, rebooted - This did not change anything.
I then cleaned out all entries of Avast/Alwil in “Computer Security Policy” in Comodos Defence+ settings, restarted Avast - This did work.
The firewall automatically started to learn a lot of stuff again - and let it through. UPDATE worked =)
For the protocol - I stated out that I had disabled and also shut down the Comodo Firewall (I did - did not help), but I did not try to disable the Comodo Defence+ - kinda forgot :P.
So the blocking was in Def+, must have been manually blocked before, wouldn’t have happened otherwise (may be an alert that wasn’t answered, I think it’s set to “block” by default if it times out).