As an update here, I uploaded the installer for whitelisting. Within 24 hours, I received a message that it was unblocked. Following a virus definition update, I confirmed that the installer worked without the problem behavior.
However, that will require us to submit every installer (there are several) for every release of the application, individually. | AVG (https://support.avg.com/SupportArticleView?l=en&urlName=AVG-Threat-Lab-file-whitelist&q=Threat+lab+file+whitelist&supportType=home) mentions whitelisting via digital signature, which I assume is a code-signing certificate. The emails I have received do not mention a process to do that - how do I register a signing cert, so all signed installers are unblocked?
As an update here, I uploaded the installer for whitelisting. Within 24 hours, I received a message that it was unblocked. Following a virus definition update, I confirmed that the installer worked without the problem behavior.
However, that will require us to submit every installer (there are several) for every release of the application, individually. | AVG (https://support.avg.com/SupportArticleView?l=en&urlName=AVG-Threat-Lab-file-whitelist&q=Threat+lab+file+whitelist&supportType=home) mentions whitelisting via digital signature, which I assume is a code-signing certificate. The emails I have received do not mention a process to do that - how do I register a signing cert, so all signed installers are unblocked?
For a customer's product we have created an installer using Inno Setup. On computers with AVG installed, we get the following behavior when running the installer:
- AVG pops up saying, "Hang on, this file may contain something bad..."
- This comes up for the installer, the installer's decompressed payload, and for the program executable itself
- The error "ShellExecuteEx failed; code 255. The extended attributes are inconsistent." appears once or twice.
- Once AVG's scans complete, the installer disappears, then restarts and completes normally.
I understand there is a whitelist process, but I have a few questions about it:
- As we do further development on the product and release new versions, do we have to keep submitting the new installers for whitelisting?
- Is there another way, like code signing the installer and executable, to avoid this behavior altogether?
- Perhaps Inno Setup is just problematic for some reason? Is there another installer platform "recommended"?
Hi Matt,
You need to upload your software for whitelisting. AVG shouldn't detect the program again as threat.
After uploading for whitelisting, you will receive an email with further details. If AVG detect your program again for future updates, please revert back to that email for further assistance.
Click the below link to show steps to upload the files for whitelisting.
https://support.avg.com/SupportArticleView?urlname=AVG-FTP-file-upload
Hi Avinash/Matt
Is there any possibility that others of us can also get the answer to Matt's last question about the problem of having to submit every release of the application individually, and code-signing certificates.
Thanks!
Hi Matt,
You need to upload your software for whitelisting. AVG shouldn't detect the program again as threat.
After uploading for whitelisting, you will receive an email with further details. If AVG detect your program again for future updates, please revert back to that email for further assistance.
Click the below link to show steps to upload the files for whitelisting.
https://support.avg.com/SupportArticleView?urlname=AVG-FTP-file-upload
Matt, I could see that you have submitted the same query to our senior technical team who have resolved this matter.
They will respond to your email at the earliest possible, please keep checking your inbox and spam box as well.
Hi Avinash/Matt
Is there any possibility that others of us can also get the answer to Matt's last question about the problem of having to submit every release of the application individually, and code-signing certificates.
Thanks!