Issues installing Canon DLR ASCOM drivers
Posted: Tue Feb 16, 2021 6:25 pm
I am trying to use my Canon 700D (Also known as the Rebel T5i) in sharpcap. As part of this pursuit I have been attempting to install the ASCOM drivers for the Canon DSLR. I found a post from Robin in cloudy nights from a few years ago saying that he successfully connected a Canon 700D with sharpcap using the ASCOM drivers. However, the key issue I am running into is that my antivirus software flags the install files as containing a virus.
My antivirus software is Bitdefender. Here is the error message it gave when blocking the virus install, with specific info on the which virus the ASCOM driver file contains:
The file C:\Program Files (x86)\Common Files\ASCOM\Camera\ASCOM.DSLR.Camera\is-GPBG1.tmp is infected with Gen:Variant.Bulz.186598. The threat has been successfully blocked, your device is safe.
Here is where I went to download the ASCOM DSLR driver files which were flagged as infected when I attempted to install:
https://github.com/FearL0rd/ASCOM.DSLR
Since this is open source development I'm sure it is quite possible that someone who has worked on the program at some point may have had a virus on their computer that became introduced within the driver files.
Has anyone else encountered this issue?
My antivirus software is Bitdefender. Here is the error message it gave when blocking the virus install, with specific info on the which virus the ASCOM driver file contains:
The file C:\Program Files (x86)\Common Files\ASCOM\Camera\ASCOM.DSLR.Camera\is-GPBG1.tmp is infected with Gen:Variant.Bulz.186598. The threat has been successfully blocked, your device is safe.
Here is where I went to download the ASCOM DSLR driver files which were flagged as infected when I attempted to install:
https://github.com/FearL0rd/ASCOM.DSLR
Since this is open source development I'm sure it is quite possible that someone who has worked on the program at some point may have had a virus on their computer that became introduced within the driver files.
Has anyone else encountered this issue?