In order to track down the problem I tried a boatload of things to try and isolate where the problem was coming from.
One installer platform apparently tagged. One third party library that had been flagged as malicious. How do I know this?Īs it turns out there were a number of factors at play here: In this case however, it turns out that it's definitely a case of false positives. Seeing AV warnings on software is something you generally want to take serious. Brave indeed - I'm not sure I'd do the same. A few were brave and installed anyway - saying they trusted me that there was no malice in these files since they are coming from me. Looks nasty doesn't it? I had to take a closer look.Īnti-Virus false positives are a pain because it's quite likely if you open the package and see a virus warning you're going to be very hesitant to go any further, my assurances aside :-) Several people contacted me in recent weeks and let me know that the installer was flagged by their Anti-Virus tool. But to my chagrin, using VirusTotal - which is used by Chocolatey and other distribution sources - I was coming away with 9 AV failures: After all I know what's in my code and there's nothing threatening in here. 
My first reaction was - "ah, just a fluke with a false positive".
#Iexpress unable to open the report file install#
I didn't realize anything was wrong at first, until a few occasional emails came rolling in from users telling me their anti-virus flagged the installer - in many cases completely blocking the install process. It's a standalone desktop application and in recent months I've been plagued with Anti-Virus false positives for the installation executable.
I've been working on Markdown Monster for a while now.
0 kommentar(er)
