3
Hello. I went through a similar problem with AVAST. I made a digital certificate to sign my code by Certsign:
https://www.certisign.com.br/certificado-digital/assinatura-codigo/authenticode
To use this certificate is very simple, when you enter the publishing part of your software, you will see a publication screen will have a tab:
SIGNING
On this screen you can put the digital certificate and sign your code.
After I did that, I never had problems with AVAST or Windows security again.
See http://www.hardware.com.br/comunidade/desativo-mensagem/754771/
– Dinei
Search for code Signing. In short, you need to purchase a specific certificate for this, from a recognized certifier, and sign the executable (either with signtool.exe or other similar methods). As for the specific warning of the image, part of the problem is the fact that it is wanting to run from mapped unit.
– Bacco
@Bacco please move your "comment" to a reply. :)
– Thiago Lunardi
@Thiagolunardi would have to elaborate more, just "brush over" the subject to make it easier for Thomas to research. I’m kind of tied up with other topics to elaborate, but if you or another user want to respond with more details, feel free (it is good to remember to elaborate on the Signing code, and also explain the criteria that windows uses to determine that a network file is unreliable in addition to those marked with stream NTFS as downloaded from the internet)
– Bacco