After creating my exe file from my jar using Launch4j, I noticed this message:

WARNING: Sign the executable to minimize antivirus false positives or use launching instead of wrapping.

So I started digging into how to sign it, and finally got that to work as well. But now I was wondering, do I now not have any false positives?

I uploaded the signed exe file to VirusTotal and got a score of 2/64 (Cylance marked it as Unsafe, and SecureAge APEX marked it as Malicious) Granted I have never heard of either of them, so I wasn't making a big deal out of it.

But I wondered what the score would be of the original (unsigned) exe at this point, so I uploaded that and got a score of 0/66 (including Cylance and SecureAge APEX)

Is there any other reason you would like to sign your jar file? At this point I am more tempted to distribute the non-signed one as it provided a greater/perfect score on VirusTotal opposed to the signed one, incase one of the users actually wanted to check it out at some point this would reflect much better on my program, even if it was only a 2/64 from a relatively unknown provider.