You may need to sign your executable. A lot of AV programs don't like those at all. 

My experience in this issue.

We use McAfee internally.  When we run (32 bit) compiled application, McAfee promptly quarantine that file.  When I sent the exe file to McAfee, they told me they will whitelist the exe, so no further blocking will happen.  It took 10-15 days for them to come out with a new update.   That update didn't delete the exe, that we sent to McAfee.  

In the meantime, we modified / re-compiled the exe many-a-times, which promptly got deleted by McAfee, as those were not white-listed.  So in my opinion whitelisting is not a permanent solution, to me atleast.  

The same issue is not there if we make 64 bit application.  McAfee didn't delete/quarantine those 64-bit of the same applications.

Now the question is

1.  Is it the problem of Appeon or McAfee?  As only 32-bit applications are affected.

2.  When every users of PB has the same issue, is it still the responsibility of individual users to contact the AV company? 

3.  Appeon (CEO) says their products are AV tested.  Does that mean the applications developed using PB are also tested.  Have Appeon developed any sample application (32 bit) and tested for virus warnings?

4.  Can Appeon suggest one / two good AV's that the PB applications can work without issues?

Happiness Always
BKR Sivaprakash

Hi.

While I'm not an expert, I would give more importance to the results shown in behavior... I say that because 5/72 is not so bad, given that most of those 5 AV vendors are small... Of course this can't be the answer to your client. You can always try to contact them.

Andreas.

Hi Maymone ;

  The problem is the AV software being used. We have seen this over and over again many times. Especially when non-mainstream AV's are used. However, this issue is really about the AV "trusting" your compiled App 's EXE. When Appeon Beat tests & releases any PB version we test the IDE and the Compiled App EXE signature with many mainstream AV software vendors. If it fails, we inform the AV vendor so that they can adjust their scanning process (aka definitions). You can get your AV software to trust your EXE signature via (as a few examples) ...

• Have the AV Software Vendor update their software AV definitions
• Have your AV team(s) add an exception for your App EXE(s)
• Add a "Manifest" file that allows the AV software to trust your App EXE.
• Digitally sign your App EXE(s) with a trusted certificate.

HTH

Regards .. Chris