[Malwarebytes and Microsoft Security Essentials conflicts]

initial tests have been successful with 1.233.245.0 without any exclusions.

[Malwarebytes and Microsoft Security Essentials conflicts]

2 minutes ago, oreonutz said:

This was DEFINITELY DUE to a Microsoft Security Essentials definition update (and all Microsoft Anti Virus that uses the definition).  This has been admitted several time by Microsoft themselves, although they accepted no blame, they claim their AV is to only be used alone! 

good to know.  I know they stated several times to use their AV alone.  If only....

[Malwarebytes and Microsoft Security Essentials conflicts]

Was this in fact a Microsoft change that caused the issues?  We have a premier support case open with MS since Friday.  Their initial response was a change Malwarebytes made that conflicted with their existing AV solution.

[Malwarebytes and Microsoft Security Essentials conflicts]

4 minutes ago, Cleatus said:

thanks for the info on how you got it done-- two problems....these are Police laptops--half the people are asleep (night shift) and /or off for three days or on vacation.  Two, I don't have any remote access software-- I requested some, but they refused to spring for it.

 

As someone stated earlier have them rename MBAMService.exe to .old and restart.  Wait till the updated definitions fix the issue.

 

[Malwarebytes and Microsoft Security Essentials conflicts]

13 minutes ago, mchammer99923 said:

Can you just type in the .exe name to exclude in scep processes? i'm getting errors when typing in the full path for the managed client due to the ' in the name

yes.

 

 

[Malwarebytes and Microsoft Security Essentials conflicts]

10 minutes ago, msherwood said:

Yes, for those with x64. My message was a quick copy/paste to get it posted. I'll come back and edit here in a bit.

no problem.  Just wanted to make sure since the exclusions are not working for us. 

[Malwarebytes and Microsoft Security Essentials conflicts]

23 minutes ago, msherwood said:

If you're not having success with the exclusions, here's what worked for us within MBAM 1.80:

1 - Boot into safe mode with networking

2 - Open MSE – Go to Settings -> Excluded Processes and add the following:
C:\Program Files\Malwarebytes' Anti-Malware\mbam.exe
C:\Program Files\Malwarebytes' Anti-Malware\mbamgui.exe
C:\Program Files\Malwarebytes' Anti-Malware\mbamservice.exe
C:\Program Files\Malwarebytes Anti-Malware\mbamscheduler.exe
C:\Program Files\Malwarebytes Anti-Malware\mbamapi.exe
C:\Program Files\Malwarebytes Anti-Malware\mbamdor.exe
C:\Windows\System32\drivers\mbam.sys

3 - Save Changes

4 - Shutdown and Boot into Normal Mode

Also, we're working on MBAE and we'll have more to share on that shortly. 

Wouldn't it be ProgramsFiles (x86) 64bit installations?

[Malwarebytes and Microsoft Security Essentials conflicts]

neither fix has worked for us.  I added the exclusions to SCEP and MBAM.  SCEP locks the system up when running a quick scan.