The amount of prefetch files is also getting silly. Every new version of icarus generates a prefetch file, about 20 KB each. It’s just clutter.
I have an old Windows 7 Virtual Machine that has Avast installed and is set to manual update for both program and virus definitions.
It had Avast Free 24.6 installed. No trace of any icarus.exe on the whole machine. I just updated both program version and virus definitions. It now runs 24.11. And critically: no icarus.exe on the machine!
Can we assume that Avast has discontinued the use of icarus.exe? Or will this problematic piece of software come back in the future?
My guess would be a likely yes, presumably after they have resolved this cock-up (sorry for the use of a technical term).
A new copy of icarus.exe gets installed and then discarded by every instance of update. That behavior runs afoul of several firewalls.
Interim software is tolerable, when updates are infrequent. Anti-malware gets updated FREQUENTLY. Therefore, the interim method is completely unsatisfactory.
The VM I updated came from 24.6, which predates the use of icarus.exe
Maybe if I have some time I’ll spin up a VM and completely remove Avast and then freshly install 24.11 to see if icarus.exe is present. Current copies could be leftovers from previous implementations (although that would be sloppy)
Or as suggested it may be the case that this is a staggered roll-out and not everybody gets icarus.exe as part of an Avast update or install. Hard to tell without direct word from Avast devs.
This is due to the location of icarus.exe changing on every update into a directory with a completely unique GUID each time. In the past the updater didn’t change the location it ran from - the version of the file might change but “where” it ran from didn’t which is what the firewall is looking at.
A proper firewall looks at both. If the executable itself has changed even though the location hasn’t, it will still be regarded as new. Which it then is.
True - but I’m talking about the products that use the Windows Firewall and just present a GUI for it
In addition to icarus being in a new directory 6 times a day, it also occasionally shows up as unsigned. Why does your update program behave like malware? Are you sure your software has not been compromised by a supply chain attack?
1 Like
Is actually anybody from Avast following this forum? Otherwise, there’s really no point in reporting it…
1 Like
I have no doubt someone has ‘lukor: is Avast Team’ - but one thing for sure, if you don’t post then no one will see it.
2 semaines après mon passage ici je vois que j’ai bien fait d’adopter une solution “radicale” en changeant d’antivirus – alors que j’utilisais avast en même temps que comodo firewall sans problème depuis au moins 15 ans.
(2 weeks after my visit here I see that I did well to adopt a “radical” solution by changing antivirus – while I used avast at the same time as comodo firewall without problem for at least 15 years.)
As I said before, you can use wildcards for Comodo firewall rules if you prefer.
This is what I am getting on Windows 10 Firewall Control. Every time Icarus executes it creates a new iteration of itself in a temp folder. This triggers the firewall to ask for permission.
I have the same issue, I am considering removing Avast Antivirus after years of use, I can’t take it anymore, I’ve never had this problem before.
1 Like
You don’t say what firewall you are using ?
For some firewall you can use wildcards in the firewall exclusions.
I am using Simplewall, which is the same one used by ElpinE which I replied.
I am hating Icarus.exe
Which one have you chosen, please? I am thinking to change too… after a lot of years and I m sorry but I am tired for these continuous icarus.exe notifications.
1 Like
which one new AV have you chosen, please?