This is a real killer for me at present. It occurs on computers who use Norton Anti-Virus products.
I don't know if it also happens with other AV manufacturers - feedback would be appreciated from our members.
If you'd like to know why this is happening, take a BIG DEEP BREATH and read over this document.
http://www.symantec.com/theme.jsp?themeid=star&tabID=5Still with me? If you got lost in the blurb, here's a summary of the key points which will help you understand the plight of software developers (e.g. moi) who distributes software over the internet.
DI/DA intercepts every new executable file at the time of download from the Internet. Then it queries the Symantec reputation cloud for a rating. Based on ratings received from the cloud, DI/DA takes one of three different actions:
DI= Download Insight (DI) feature in Norton products
DA= Download Advisor (DA) feature of our Symantec Endpoint Protection product.
Its the 3rd action which is killing me at present
If a file is still developing its reputation and its safety is unknown, the user is warned that the file is unproven. The user can then decide, based on their tolerance for risk, whether or not they want to use the file.
The reason? I update the product downloads regularly, so my files are always relatively new, and are continually starting at butts to develop a good reputation.
The most embarrassing thing is that it happens to new customers, and Ive already lost potential customers because of it.
Fortunately, most customers are pleasant and understanding. Needless to say there are a few who are not, and Ive been on the receiving end of some rather angry comments.
I'm now having to apply to Symantec to get every one of the downloadable files which I create and publish whitelisted.
e.g. if a customer buys Bank Genie as a download, that file has to be whitelisted so the user isn't faced with that nasty and worrying "dire consequences" message.
If I provide an update to a program in Bank Genie or Ideas Genie, I have to apply to Symantec to have it whitelisted.
That is VERY time consuming. Worse still, it will take time for Symantec to add the new or updated file to their whitelist.
Perhaps you now know why Ive been rather quiet on the forum recently