morgan26

Hi! I figured out what the issue was: even though I was whitelisting a whole directory and expecting .exe in there to be left alone, I didn't do it properly: I think that's because that directory was in a user's AppData folder and I had tried to use a regex to match it (something like C:/Users/*/AppData/...) I've moved the .exe to a folder that doesn't require a regex and now things are looking much better, my program isn't freaking out anymore. Thanks for the help!

Anti ransomware Version is 0.9.18.806 Managed client version: 1.9.0.3671 Anti malware version: 1.80.2.1012 Anti exploit version: 1.13.2.127

That would be the business version

Hi, thanks for the info, I really appreciate it! Unfortunately now that I'm digging into it a bit further, I just found out that I wasn't talking about the right product: we're actually using Malwarebytes Anti-Ransomware. Would you happen to have additional feedback on how to exclude a specific file for that one? Morgan

Hi, I'm a software engineer who recently updated my version of Malwarebytes AntiRansomware (Component Update Package: 1.1.258) and started noticing a weird behavior: as part of testing if a Windows directory is executable, I copy over an executable from C:Windows and run it there, then delete it. This process is repeated every time my program is started (multiple times a day). I found out that Malwarebyte seems to hold onto the .exe (I imagine to scan it?) much longer than previously: between 5 and 20 minutes, to a point that it makes my software crash. I was wondering if there was a way to get Malwarebytes to always trust what is happening in that specific folder, disregarding .exe files being copy pasted. Since I always use the same .exe, I wouldn't mind having a hardset rule that clears it if such a thing exists. Thanks for any help you may be able to provide! Morgan