Hi Dexter,

I recommend to do the following things:

1. Sign your application .EXE with a trusted certificate.

2. Sign all external DLLs with at trusted certificate.

3. Include built-in manifest file.

4. Report the false positive to the A/V vendor.

5. If problem keeps happening switch to different A/V vendor.

Best regards,
Armeen

Ok Armeen, I will try your advice. thanks a lot.

We are having sometimes problems and sometimes not (with the same application). The other day, once again I got Avast telling me there was a virus after pausing on the login window (no virus detected sofar !), since the database was down and had to login on the server to start the oracle instance. When typing in my password again in the app, I got this:

So this happens like "random". I could complain with Avast, but it seems I'm going to have to keep complaining for every release of Appeon and every release of our executables. For development, I just exclude the folders, but yes ... if this starts to happen on customers we'll have to sign the apps and cross our fingers they don't use Avast.

WHY does this not happen with pb12.6 executables? I still feel that Appeon could / should do something about this.

best regards.