Dear @HonzaZ,
Thank you for your answer.
My question was : is there a
permanent way to avoid the "File might be dangerous" message ?
As I'm making new builds of the .exe quite often, I don't have time to re-submit the .exe to Avast, Avira, and 10+ other antivirus software each week...
I already looked at "Avast Clean Guidelines" :
https://www.avast.com/faq.php?article=AVKB228but it didn't help me, because this is unclear:
1. Every executable file should contain a vendor identifier. No specific format is required, but Version Info is preferred. Other option could be a plaintext description in a custom section.
2. Digital signature is always beneficial.
3. If the file is packed, it should have a Taggant.
1. Can you give more infos about vendor identifier? I'm using
https://pastebin.com/PSxqv3rm, is it ok? Can you give more informations about vendor identifier?
2. What kind of digital signature? I did use Microsoft SDK "signtool" as detailed here:
https://stackoverflow.com/a/201277/1422096 but it didn't change anything. Any digital signature provider recommendation?
3. What is a Taggant in this context?
Thank you in advance @HonzaZ.