re you seriously suggesting that "trying the latest" version might fix the problem?
Since the AV vendors change their heuristics daily, sometimes this helps, just as you can see in the initial messages from this thread.
We do not guarantee that an upgrade to the latest version will fix your version, thus we do not recommend this as a main solution, but sometimes it can be the easiest solution.
The algorithms defined by AV providers do not support whitelisting a certain vendor (e.g. our company for example) as that would be a serious security breach for them. They do whitelist us our binaries everytime we upload them, but this sometimes it is not enough as these binaries get changed with your package settings. (in EXEs we include your MSI, for other stubs we inject settings from the project and so on).
Basically, all these files are now new files in what the AV providers are concerned, and their false-positive detections start to appear.
God, so frustrating to have customers calling us up complaining we're shipping virus laden software.
We strongly recommend that you scan each official release (not your daily builds) on virustotal.com for false positives and submit your official release setup package
to any of the AV vendors that incorrectly detect it.
We do this for the setup package of Advanced Installer itself, each time we release a new build, as it is commonly detected because it contains all the EXE/DLL stubs used in the packages you generate.