SteveMac555

Could you please explain what the problem is between the two products? Is it not possible to fix this issue with a software update? My worry is if we add those 78 exceptions to SCEP/MSE what's stopping people renaming ransomware.exe to mbam.exe on PCs without MB and placing it in that path which is excluded from the AV? Thanks,

Hello, We have around 200 licenses and installed on roughly 151 machines (Managed Client & Anti-Exploit). We have roughly 5 (that we know of) that lock up every single day, multiple times. We have the Microsoft Security client paths in the "Ignore List" in the management console, as well as the listed paths in the first post for SCEP. I can confirm the machines both have these exclusions when locking up. We have also tried the delayed start and unticking random "Scan etc. etc." boxes in the policy to try and fix it. I discovered by accident that "Ending Process" on the MBAM executable in task manager instantly locks the machine and becomes unusable. None of the machines we have recover from the lock-up. They need to be hard-reset and they then seem to work for a while. We have had reports of people 'Switching User' in windows and having the lockup but we haven't seen this ourselves. On the most affected PCs we have had to remove MalwareBytes Managed Client as they were becoming unusable. I understand it's a wide spread problem and no one is really to blame; but people are not impressed here as we're a new MB customer and have just started rolling it out to all employee PCs. Thanks,