admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
False virus detections
A number of users report virus detection's on GSB beta install file, enhanced walk forward optimizer and portfolio analysts.
I get the same issues with my autoit scripts and nircmd.exe files. (not related to me)
Here are some fixes that I'm using.
Surprisingly gmail.exe is not flagged. I thought it might be because it sends emails.
The logic is simple. Files like autoit (a scripting language) could be used to do damage, therefore declare all autoit scripts as virus's.
GSB files (not the installer ) are obfuscated to protect them being DE-complied.
Virus are obfuscated, therefore GSB is a virus.
I could submit false detection reports but there are so many virus companies, and GSB currently is getting a few builds a week. The last false
positive report I sent was meet with no response by the Chinese vendor.
When we have a stable build, that would be more possible to fix the issue.
Please see a fix below. Basically you can exclude the GSB folder and or exe's.
 
|
|
|
mindesb
Junior Member
Posts: 2
Registered: 14-12-2017
Location: Vilnius
Member Is Offline
Mood: No Mood
|
|
Microsoft security
Microsoft security essentials reports as virus too. Attached screenshot.
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
My posting above was on MSE.
the next release gets 1 out of 66 virus programs showing it as a virus.
Should be uploaded in the next week.
You also ought to run the latest beta. Just note that the file path is wrong and it says file not found.
You need to make a shortcut to gsbstandalone...exe not gsb...b.exe
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Today microsoft security essentials is flagging and deleted gsb1.0.47, ewfo as have virus.
Nothing has changed in gsb or ewfo to generate this.
At the heart of the issue is GSB files are obfuscated. Virus are obfuscated. Therefore GSB = a virus.
Not good logic. Virustotal.com shows gsb 1.0.47 passing 65 of 67 virus detectors including microsoft!
See steps below to exclude c:\gsb
    
|
|
|
JasonT
Junior Member
Posts: 61
Registered: 6-6-2018
Member Is Offline
Mood: No Mood
|
|
I just had a repeat problem with that after installing the most current build and a BitDefender pattern update. I had trouble getting GSB to
reinstall so I had to uninstall, delete the GSB folder, then reboot. I then had to add the installer file to my BitDefender application whitelist to
get it to run. I then re-installed GSB selecting the 'launch GSB' check box at the end of the installation (mistake). BitDefender proceeded to
delete the GSB executables again. I repeated the process and did not select 'launch GSB' at the end of the install but instead whitelisted all the
newly installed GSB executables then ran GSB. Is working fine now.
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Quote: Originally posted by JasonT  | | I just had a repeat problem with that after installing the most current build and a BitDefender pattern update. I had trouble getting GSB to
reinstall so I had to uninstall, delete the GSB folder, then reboot. I then had to add the installer file to my BitDefender application whitelist to
get it to run. I then re-installed GSB selecting the 'launch GSB' check box at the end of the installation (mistake). BitDefender proceeded to
delete the GSB executables again. I repeated the process and did not select 'launch GSB' at the end of the install but instead whitelisted all the
newly installed GSB executables then ran GSB. Is working fine now. |
Thanks for the tip. GSB is using a temp folder for cloud information which is also giving issues. Fixed in the next beta version to be releasef.
|
|
|
![[*]](images/davis/default_icon.gif){kind=icon}
