Hello,
You can try to report your built EXE setups to the related antivirus support teams so they can remove the false positive detections.
Also, it will be very useful for us if you can replicate the false detection in a buildable sample (AIP + its referenced files) and send it ad download link for it so we can further investigate this on our side.
Recently we received a similar false detection from another user and we discovered that the false detection appears only in a very particular scenario:
1. the user added his installation files (i.e. DLLs) in "Files and Folders" page; when scanned separately outside of the setup the files were detected as clean, but when packaged into an EXE setup, the installation setup was falsely detected (we tried to replicate the detection by using our own sample DLLs but every time the sample setups were detected as CLEAN)
2. the
"Enhanced User Interface" feature is enabled for your setup package
3. you build a
"Single EXE setup (resources inside)" package type
So, it seems the false detection appears only when you try to package some of your specific installation files into an EXE setup package built with the "Enhanced User Interface" feature enabled.
As a workaround you can build your setup package as an
"EXE setup with resources next to it" (Builds page -> Configuration tab).
All the best,
Daniel
FOLLOW US
Get the latest news in Application Packaging