I’m an old avast free user (over 3 years). I needed to clean my notebook so I’ve uninstalled avast, I’ve uninstalled several other programs and I wanted to reinstall avast free latest version. I’ve downloaded the offline installer (from softpedia.com) and tried to install it, but it remains in the installer’s start screen forever. I’ve tried with online installer and I have the same situation. No warning or error.
I’m on Windows 7 Home Premium 64 bit, with a SSD 850 Evo and the notebook is a sony vaio i3 with 8 GB ram.
I’ve checked with malware bytes and I have several PUPs I know about (advanced system care, etc), but as far as I know, nothing to worry about.
There is any way to log the installer to see exactly what is blocking it ?
It seems that the problem is windows7firewall control from sphinx software (now renamed as windows10firewall control, but I did not have such problems with previous avast versions).
Avast is “calling home” from the very beginning of the installation and if something is blocking it (that firewall in my case), it stays there waiting for an answer from his servers. Strangely enough, even after allowing avast to communicate outside LAN, it freezes in the start-up installer. Only at the second launch of the installer it goes further.
After upgrading the firewall from sphinx, I’ve succeeded to finalize the installation, but with several retries.
Now, avast freezes at checking the latest software versions on my notebook, and I’m suspecting it is the same conflict with the firewall. Normally, the firewall pops-up an alert and allows the user to decide if an app could go on internet or not, but there is no pop-up when avast is checking local software versions. Could be a “timing” issue, if the pop-up alert from firewall is too late, avast “forgets” to give back the control to the user…
I’ll make other tests but I’m not very comfortable to uninstall that firewall…
There is no need for a third party firewall if you have W7 (or higher).
If you still want to keep it, a decent firewall will have one (or more) log files.
Check it to see if you can get more information about the problem I would say.