I am using C ++ Builder RAD10.2 Tokyo. If I compile with dynamic RTL everything is fine. But if I include it inside the Exe, Avast says: Win32: MalOb-CA [Cryp]. I already reported it as a false positive. It is absolutely necessary that my application be standalone. Not only does my application have this. Any Win32 with static RTL is detected as a threat by Avast. What to do ?
Symantec Endpoint Protection's heuristic scanner recently triggered as Heur.AdvML.B on one of my 10.2 programs (a TCP comms Windows service). I reported it and had it whitelisted, but I have a feeling it will trigger again on the next release.
I ended up getting Avast to ignore scanning anything in that project folder. Which is okay for development but not for release. Other projects work fine. (By the way, checked with other virus/malware software and the executable is indeed fine).