MBAM keeps locking Visual Studio compiled executable preventing subsequent rebuild and debug

[pal1000]

This doesn't seem to be an issue anymore. Tested with v3.2.2.2029 CU 1.0.212.

I compiled a few small projects and 2 very large ones with no issues.

Validated everything with Process Explorer.

Edited October 24, 2017 by pal1000

[dcollins]

Yes, sorry, I forgot to update this thread but the issue should be resolved as of Component Package  Version 207 which was released on September 28

[Phoenix84]

I'm still seeing this issue.

I built an executable in VS, then copied it to a different location (both on the same, non C: drive), however when I went to delete it from that location, the delete failed (it deleted, but came right back).

Once I disabled ransomware protection, the file immediately went away (no further action was necessary).

 

I'm on MBAM: Version 3.2.2.2018

Component: 1.0.212

Update: 1.0.3114

 

https://www.dropbox.com/s/ghj3tiezkekn15p/mb-check-results-2017-10-27.zip?dl=1

Edited October 28, 2017 by Phoenix84

[raerae1616]

I'm having this issue also.  I didn't encounter it for the first 2-3 days after installing and purchasing real time protection with  Malwarebytes Premium, but suddenly late this evening it started blocking my build. 

At first I didn't know the cause, but 10minutes on Google lead me to this possibility and once I disabled Malwarebytes the problem was immediately resolved!

Malwarebytes version: 3.3.1.2183

Component package version: 1.0.236

Update package version: 1.0.3389