Page 1 of 1

v1.1.32.00 and Avast

Posted: 26 Nov 2019, 20:29
by avant-guvnor
Unable to install Autohotkey v.1.1.32.00 on a Windows 10 Pro v.1909 (build 18363.476) pc with Avast anti-virus v.19.8.2393.

Avast reports the following:

Image

Re: v1.1.32.00 and Avast

Posted: 26 Nov 2019, 21:50
by gregster
Well, on virustotal (without Avast) I get 3 hits (but twice McAfee) out of 69 engines for our installer:https://www.virustotal.com/gui/file/ce505d272f8d36c5599ac81f005e1d2d586eeaaa778c779ad858e44fdadfdb0d/detection
Not much for a new AHK version. Traditionally, there are a lot of false-positives for AHK.


Avast has been well-known in the past for creating false-positives for AutoHotkey, especially for new versions.

You can submit the suspected false-positive to Avast for a closer review:
https://www.autohotkey.com/boards/viewtopic.php?f=17&t=62266

That should help updating their database.

Re: v1.1.32.00 and Avast

Posted: 26 Nov 2019, 23:50
by SOTE
Also, v1.1.32.00 is a newer version of AutoHotkey, so various Anti-Virus companies may not have updated their database yet. The AutoHotkey community can help, by submitting false-positive reports and push companies to verify and then update their software. Some Anti-Virus companies are kind of lazy, so unless users contact them, they may not update their database on their own.

Re: v1.1.32.00 and Avast

Posted: 27 Nov 2019, 07:40
by avant-guvnor
I suspected a false positive, have submitted file to Avast, but also wanted to report my findings in these forums.

Re: v1.1.32.00 and Avast

Posted: 27 Nov 2019, 08:26
by swagfag
more often than not this is going to be the case. as long as u download from lexikos's page 99% of the time ure probably fine(1% him having gone rogue/hacked)

if ure mega paranoid(not necessarily a bad thing) u can always look at the commits since the last release and compile an .exe urself