Avast installer creates new interation each time it checks for updates

Avast Free Antivirus / Premium Security
1

Every time Avast checks for updates it creates a new iteration of “Avast Installer”. I am up to Avast Installer (95) at this point. Whenever a new iteration is created, my firewall asks me to allow it through. As soon as I do Avast creates another iteration and I get asked again. It is very annoying. I’ve used Avast for many years and it has never behaved that way. I am using it on a desktop with Windows 10.

2

If this is what you are talking about there is already a large topic on this.

https://community.avast.com/t/for-a-week-or-so-the-firewall-asks-everytime-if-icarus-exe-can-connect-even-an-allowed-rule-is-set/850416

3

Thank you. I’ve reviewed the long list of comments. Icarus creates a new iteration in a temp file every time it is needed. This signals the Windows firewall control to notify the user. Is there a solution? I could not find one in the comment stream. Is Avast aware of the issue? Are you associated with Avast or just one of the more experienced member of the community?

4

I’m sure they are aware of it there are a couple of replies by lukor an avast team member.

I have just been an Avast Free user for a little more than 20 years. I have been a forum member since May 7, 2004. In that time I have gathered much information.

There isn’t a solution at present, as far as I’m aware, it doesn’t effect those that are using the Avast Firewall component. Only those that are using the Windows or other 3rd party firewall.

5

Thanks again for such a quick response. I am using only the free Avast anti-virus. I have been using it for more years than I can remember. For me, the current problem has only been around for the past few weeks. I’ll revisit some of the posts by “lukor”. Thanks for your help.

6

Glad I could help.

I use Windows 10 Home 64bit version fully up to date. I don’t use the Windows Firewall but the Avast Firewall Component and I don’t get any blocking of the icarus.exe when it is updating the Program, Virus definitions, etc. Whilst that isn’t a solution, it it an option, as You can’t use wildcards in the windows firewall to try and allow icarus.exe connections.

By all accounts this happened in or around the Avast 24.10 or 24.11 - personally this should have been found in Alpha or Beta testing. But if the tests didn’t use other 3rd party firewalls it wouldn’t have been detected.

A belated welcome to the forums.