Problems with the latest GD-77 Community CPS installer

posted in: GD-77 | 3

A number of people reported that the latest GD-77 Community CPS installer had a virus in it.

To cut a long story short, this is almost certainly a false positive, but I appreciate that its a big risk installing something which your antivirus has reported as a virus, so I’ve had to revert to the previous version on GitHub, which does not include the driver for the OpenGD77 comm port.

I’ve also copied my original files, that I use to build the installer exe, onto GitHub and also zipped up the Comm port installer exe and bat file

https://github.com/rogerclarkmelbourne/radioddity_gd-77_cps/tree/master/installer

At the moment, there’s not a lot more I can do about this, because the the antivirus companies would rather declare multiple false positives than one false negative.

To try to understand why the installer now seems to be reported as a virus, I did a complete virus scan on my PC using 2 different antivirus packages.Firstly the built in Microsoft Antivirus, and then using Avast Antivirus.

This scan took around 9 hours, multiplied by 2 programs, i.e 18 hours, and I had to leave it going overnight for 2 consecutive days.

None of the individual files which are installed by the are reported as viruses by either antivirus package

Bizarrely, Microsoft Antivirus does not think the installer a virus when InnoSetup initially exports the exe.

It’s only if I upload the exe to GitHub or my Google drive etc, and then download it again, does Microsoft Antivirus decide that not only the file that has just been downloaded is a virus, but also the original file I uploaded is now a virus, and any other copies of the file on my PC.

I’ve found that I don’t even really need to upload and download the file for the exe to be flagged as contain a virus.
All I need to do is to drag the exe into the Google Chrome browser, and it treats the file as if its been downloaded from the web and somehow seems to be either getting Microsoft antivirus to scan it, or possibly Chrome is doing something like sending the exe to Google central for scanning, because when I drag a local file onto google, it takes it at least 15 or 20 seconds before it decides its a virus, and the local virus scanners do not take that long to scan a file.

 

Doing some research, this seems a common problem for any exe’s which are not digitally signed. But the cost of a digital certificate from a reputable provider is around $500 USD per year, and there is no way I could afford a digital cert, especially as I do all of this for free.

 

So, at least for the time being, I’m not able to build any new installers for the CPS and people will need to manually install the comm driver.

3 Responses

  1. Marko YT5HOK
    |

    Windows 10 v1903 (Windows Defender) doesn’t recognize Community CPS installer as a virus. Installed it on two machines, personal laptop and work PC. Although, I did install drivers at first without installer, but I did it again with it. It does warn about unsigned exe, but it’s OK.

  2. Roger Clark
    |

    I reverted to the previous version which does not flagged as a virus, but does not contain the driver installer.

  3. Roger Clark
    |

    I reverted to the old version, which does not get reported as a virus

Leave a Reply