seit dem letzten update von free avast antivirus (version 24.10.6133 - build 24.10.9535.880)
bekomme ich mehrmals am tag meldungen von meiner firewall (keine avast firewall) das
icarus.exe und/oder avast installer um erlaubnis fragen.
ein oder zwei tage lang mag das noch aktzeptabel sein, langsam wird es aber eher nervig.
gibt es fuer das problem eine einfache und schnelle loesung?
since last free avast antivirus update (version 24.10.6133 - build 24.10.9535.880) i keep getting
messages from my firewall (not a avast firewall). the messages appear multiple times a day
and they are about that icarus.exe and/or avast installer want internet access.
one or two days of the messages might be ok, but with the time its getting on ones nerves.
is there a simple and fast solution to the problem?
ok, as i can see there is no help to get here concerning my problem.
is there a way to contact avast support directly to solve this issue?
been using avast antivirus for the past 16 years without any problems but this issue now
is absolutely inacceptable.
so, before i uninstall avast antivirus i would like to give the support a chance to solve the
problem.
@Puck@mambi which version of Windows are you running?
Have either of you tried doing Repair of Avast or installing the previous version (with avast program updates disabled)?
with me the problem happens on windows 10 home 22h2 and windows 11 pro 23h2.
yes, i tried the repair function with no result.
yes, i set the allowed rule too on my firewall, but still icarus.exe and avast installer keep asking
for allowence.
no, i haven’t tried installing the previous version of avast, couldn’t find it.
the whole thing is just very annoying.
all i can say is that with all the false positives lately and now this issue avast is getting to a
point where i’m getting very unhappy with avast and ask myself if i shouldn’t uninstall avast after
17 years of no problem use.
as i said earlier, a direct link to avast support would be great.
since Puck reports the same problem i assume lots of others have the same issue, just not
reporting it.
i think this is something support or the dev’s should be looking at.