Launcher.exe detected by Avast, even after exclusion

[SK995]

This issue is fairly straightforward. Wehenever getting past the launcher, as I reach the login screen, Avast puts the Launcher.exe file in quarantaine, and sometimes makes it impossible to retrieve.

I have whitelisted the whole Battleforge file and specifically dealt with Launcher.exe. Avast removes it nonetheless.

The threat is listed as ''IDP.Generic''.

I am running Windows 10 on the Latest non-Insider update. The viral database version is 180914-O.

Thanks for reading.

[MephistoRoss]

Not sure what you expect us to do about this, seems more like this is a bug in Avast.

We are aware that most anti virus flags our software. I'm told this happens when one exe makes changes or opens other exe files, which happens with our updater. Nothing we can do about this right now.

[SK995]

I was not really expecting a solution on your end, to be fair. As you pointed out, Avast is at fault here.

However, I have found a workaround. After manually removing the file from the strange behaviour check list besides excluding the whole Battleforge folder from scans, it seems to no longer be detected and removed.

This is not a thing I have personnaly ever had to do, so hopefully this may help some people.