locked Malwarebytes quarantines both 2.11.1 and 2.11.2


Mike N4LKB
 

Malwarebytes Premium (v3.4.5) automatically quarantines a file called "MachineLearning/Anomalous.100%" which effectively deletes JTAlert.exe for versions 2.11.1 (tried 3 times yesterday) or 2.11.2 (this morning)..

2.10.7 works fine, and has, from April thru yesterday morning..then tried 2.11.1 resulting in quarantine 3 times, reverted to 2.10.7 yesterday which then worked fine. Tried 2.11.2 this morning: quarantine.

Running Windows 10 (v1709), wsjtx-1.9.1-win32 , HRD Logbook (v6.4.0.840) (without CAT control) on IC-735.

N4LKB


m_scot_alex
 


HamApps Support (VK3AMA)
 

On 4/06/2018 9:40 PM, mjloucks@... wrote:
Malwarebytes Premium (v3.4.5) automatically quarantines a file called "MachineLearning/Anomalous.100%" which effectively deletes JTAlert.exe for versions 2.11.1 (tried 3 times yesterday) or 2.11.2 (this morning)..

2.10.7 works fine, and has, from April thru yesterday morning..then tried 2.11.1 resulting in quarantine 3 times, reverted to 2.10.7 yesterday which then worked fine. Tried 2.11.2 this morning: quarantine.

Running Windows 10 (v1709), wsjtx-1.9.1-win32 , HRD Logbook (v6.4.0.840) (without CAT control) on IC-735.

N4LKB
N4LKB,

Both JTAlert 2.11.1 & 2.11.2 utilise a more recent version of the compiler used to create JTAlert.exe. 2.10.17 used a much older compiler version. The compiler change would have altered many of the internal code signatures compared to all previous versions and it is likely these changes that have caused Malwarebytes to generate the False-Positive alerts.

JTAlert has always been and still is virus free.

de Laurie VK3AMA


KG4W
 

This morning, malwarebytes informed me of a new version. I downloaded it (ver 3.5.1) and all my problems with
installing the latest version of JTAlert vanished. All is good now. Using Win 7

Ed
KG4W

On 6/4/2018 4:48 PM, HamApps Support (VK3AMA) wrote:
On 4/06/2018 9:40 PM, mjloucks@... wrote:
Malwarebytes Premium (v3.4.5) automatically quarantines a file called "MachineLearning/Anomalous.100%" which effectively deletes JTAlert.exe for versions 2.11.1 (tried 3 times yesterday) or 2.11.2 (this morning)..

2.10.7 works fine, and has, from April thru yesterday morning..then tried 2.11.1 resulting in quarantine 3 times, reverted to 2.10.7 yesterday which then worked fine. Tried 2.11.2 this morning: quarantine.

Running Windows 10 (v1709), wsjtx-1.9.1-win32 , HRD Logbook (v6.4.0.840) (without CAT control) on IC-735.

N4LKB
N4LKB,

Both JTAlert 2.11.1 & 2.11.2 utilise a more recent version of the compiler used to create JTAlert.exe. 2.10.17 used a much older compiler version. The compiler change would have altered many of the internal code signatures compared to all previous versions and it is likely these changes that have caused Malwarebytes to generate the False-Positive alerts.

JTAlert has always been and still is virus free.

de Laurie VK3AMA



HamApps Support (VK3AMA)
 

On 5/06/2018 9:42 AM, KG4W wrote:
This morning, malwarebytes informed me of a new version. I downloaded it (ver 3.5.1) and all my problems with
installing the latest version of JTAlert vanished. All is good now. Using Win 7

Ed
KG4W
Tnx for the update Ed. Good to hear.

de Laurie VK3AMA