possible conflict with Windows Defender

[retiree]

first noticed problem with one computer (Windows 7) extremely slow performance plus random system error messages. No issues identified from virus or other scans. Malwarebytes uninstalled from this computer. All issues resolved.

Problem also appeared on second computer (Windows 10) - extremely slow performance, slow launch of programs, windows edge failed to launch, etc. Disabled Malwarebytes and all performance issues were resolved. attached files are for this computer

There seems to have been a recent update of Windows Defender - Also Malwarebytes program was recently updated - I'm thinking there's a serious conflict between these programs. This may also explain problems other people are mentioning re real-time protection shutting off etc..

Addition.txt

FRST.txt

mbae-default.log

MBAMSERVICE.LOG

MB-CheckResult.txt

[retiree]

seems to be difficult to get anyone to have a look at this problem I posted 3 days ago. I think I've been experiencing many of the same problems that other people have been experiencing. Should I just try to get some assistance from support?

[Porthos]

Have you added mutual exclusions to BOTH Malwarebytes and Defender? Also update your MB to the new update package. You have  "controllers_version" : "1.0.50", New one is 1.0.75

Get the new version here.

 

I also suggest adding these to the exclusion list in Defender.

C:\Windows\System32\drivers\mbae64.sys
C:\Windows\System32\drivers\mbam.sys
C:\Windows\System32\drivers\MBAMChameleon.sys
C:\Windows\System32\drivers\MBAMSwissArmy.sys
C:\Windows\System32\drivers\mwac.sys
C:\Windows\system32\Drivers\farflt.sys

In addition to the current list here.

C:\Program Files\Malwarebytes\Anti-Malware\MbamPt.exe
C:\Program Files\Malwarebytes\Anti-Malware\mbam.exe
C:\Program Files\Malwarebytes\Anti-Malware\assistant.exe
C:\Program Files\Malwarebytes\Anti-Malware\MBAMWsc.exe
C:\Program Files\Malwarebytes\Anti-Malware\mbamtray.exe
C:\Program Files\Malwarebytes\Anti-Malware\MBAMService.exe

 

Edited March 10, 2017 by Porthos

[retiree]

Thank you Porthos. I updated MB to new package and added the mutual exclusions as suggested. Everything seems to be working much better now. Hope this keeps up!

[Porthos]

I use this combination on every computer I service in my shop and the only issues I have seen are minor and very very few. I am a proud user and reseller of the Malwarebytes product for many years now.

 

Please post again if you have any other issues.

[PALDK]

On 3/10/2017 at 5:57 PM, Porthos said:

Have you added mutual exclusions to BOTH Malwarebytes and Defender? Also update your MB to the new update package. You have  "controllers_version" : "1.0.50", New one is 1.0.75

Get the new version here.

 

I also suggest adding these to the exclusion list in Defender.

C:\Windows\System32\drivers\mbae64.sys
C:\Windows\System32\drivers\mbam.sys
C:\Windows\System32\drivers\MBAMChameleon.sys
C:\Windows\System32\drivers\MBAMSwissArmy.sys
C:\Windows\System32\drivers\mwac.sys
C:\Windows\system32\Drivers\farflt.sys

In addition to the current list here.

C:\Program Files\Malwarebytes\Anti-Malware\MbamPt.exe
C:\Program Files\Malwarebytes\Anti-Malware\mbam.exe
C:\Program Files\Malwarebytes\Anti-Malware\assistant.exe
C:\Program Files\Malwarebytes\Anti-Malware\MBAMWsc.exe
C:\Program Files\Malwarebytes\Anti-Malware\mbamtray.exe
C:\Program Files\Malwarebytes\Anti-Malware\MBAMService.exe

 

I add those, and so far I have not had a single issue since, if this was the solution I thank you from the bottom of my heart

[PALDK]

Sorry to post again, that was not the solution, V3 stopped working again, hang in scan/protection turning off and so on

I tried to stay positive, but I'm afraid I have to start wondering if this is worth all the trouble, I'v trusted in MBAM for many years, but now I do not trust it to protect me any more.

I will start looking for a new solution, it's a sad day.

To the MBAM team, Thank you for all the good years with previous versions and good luck with v3, I'll keep an eye on your product, but as it is now, I'm out.