exe file created using Visual Studio is quarantined when run

[perfesd]

I have produced a C++ file using Visual Studio 2017 Version 15.9.26.

The *.exe file that is subsequently created is quarantined whenever I attempt to run it.  If I attempt to use the Visual Studio debugger, the same issue occurs.

I would be grateful for any assistance.

[Atribune]

This happens from time to time with our Machine Learning engines. As a developer your best option is to add an exclusion for your working directory in Malwarebytes. 

Please also read below why this happens.

 

[madusmacus2]

Even files that worked 4 hours ago (i archived in a zip) when broat back they get quarentined

also the same files tested on my 2nd machine are also getting quarentined

this means i cant work :¬(

 

Malwarebytes
www.malwarebytes.com

-Log Details-
Protection Event Date: 17/08/2020
Protection Event Time: 17:32
Log File: 4b24f378-e0a7-11ea-b41b-004e01a9606c.json

-Software Information-
Version: 4.1.2.73
Components Version: 1.0.1003
Update Package Version: 1.0.28623
Licence: Premium

-System Information-
OS: Windows 10 (Build 19041.450)
CPU: x64
File System: NTFS
User: System

-Blocked Malware Details-
File: 1
Malware.Heuristic.106, C:\Users\madus\Desktop\Link.exe, Quarantined, 1000001, 0, 1.0.28623, 00000000000000000000006A, dds, 00856278, 6E322E571BE9DD48434E4EA1CF86C87E, 7077FA735A154F14EEB14DE41A559108FF2157DB2D36183ED150DB46DA7B0325

(end)

[madusmacus2]

@Atribune 

In my case we develop large suites of progrms for end users that potentialy use malwarebytes

We cant have this FP of our executables on our test sites let alone customers using malwarebytes

BTW my problem 
"-Blocked Malware Details-
File: 1
Malware.Heuristic.106, C:\Users\madus\Desktop\Link.exe, Quarantined, 1000001, 0, 1.0.28623, 00000000000000000000006A, dds, 00856278, 6E322E571BE9DD48434E4EA1CF86C87E, 7077FA735A154F14EEB14DE41A559108FF2157DB2D36183ED150DB46DA7B0325"

Started happening 5 hours ago

[okiedev]

I am experiencing this same issue.  I develop applications for my customers (many that use MBAM).  Is there anything that can be done from within Visual Studio (2019 in my case) that would make it the resulting executables recognized as acceptable by MBAM? If not, this will be a significant headache for developers and their customers.

 

Thanks,

 

okiedev