As a software developer with a small business (a couple hundred customers using our software), we have made the effort to get a security certificate so we can digitally sign our software executables and installation files, assuring our customers (and potential customers who get a trial version) that our software is not malicious and that we are a legitimate company. Internet Explorer, for instance, recognizes the digital signature and bases its reputation calculation (to determine whether to warn a user that a file is "not commonly downloaded") on all uses of the certificate, even if the specific file changes, so that when we release an update to the software, the new version is treated as recognized and doesn't trigger extra security layers.
Avast's Cybercapture does not seem to recognize such certificates, and so I'm constantly running into the "Hang on; this file may contain something bad" popup. The only solution I've found is to completely disable Cybercapture. It would be nice to have it operating for other executables that might find their way onto my system, but it's a major nuisance both for me and for my customers to have the popup occurring every time I build a new version. The security certificate is specifically intended to eliminate the need for these extra security steps; it's disappointing that Avast doesn't recognize it.