Windows 10: Defender & MBAM Coexsistence

Odd error on Insider (any build) with Defender and MBAM running at same time. MBAM is 3.0.6.1469. With Defender periodic scanning enabled, and all 4 MBAM protections enabled, I can't update definitions. WU won't find them either.

I get this error, and the code leads to practically nowhere. I do see MpCmdRun.exe fire up for just a second before the error is posted. It's trying to update, but can't. I have Defender and MpCmdRun.exe and all I could find related set as exclusions in MBAM. Also, the Defender setting of Periodic will not stick on a reboot. Used to be a setting somewhere to register/unregister Virus Protection, but I can't find it now. Maybe I'm just misinterpreting how Defender and MBAM should live with each other. I thought it would be MBAM as Real Time Protection and Defender as periodic and on demand scanning. Apparently not.

Is this the new normal until MS and MB sign a peace treaty? I'm not sure at all which side is being cranky.

Any thoughts and/or fixes? Thanks, TC.....





:)

 

Bad_Pool_Header started after a Windows 10 upgrade

When & why was MalwareBytes' Anti-Malware (MBAM) installed? Is it MBAM Premium or MBAM Free? Has MBAM ever detected & quarantined anything since it's been installed? ...before you upgraded to Win10? ...after you upgraded to Win10?

[Defender (not Defender Offline) will not be available as long as the Bitdefender application is installed.]

 

If I install Mbam *** Windows Premium (Malwarebytes), will it interfere with Defender? Win 10

Since MBAM is now sold as an anti virus replacement/program it might interfere with WD & it certainly requires a change of a setting within MBAM to not allow it to register in security centre so that it doesn’t disable it. The Pro version of MBAM especially
so.

Read about this here: Malwarebytes 3.0.5 and Windows Defender.

 

Interesting problem, from what I have read, there are basically 2 options:
Malwarebytes 3.0 - Frequently Asked Questions - Malwarebytes 3.0 - Malwarebytes Forums


1. Run both as a realtime protection, WD being primary and MBAM secondary (not registered as AV).
2. Run MBAM as a primary (registered as AV always in Action Center), WD disabled.

The third option would be like this:

3. Run MBAM as a primary, WD disabled, but run WD on-demand.

I guess, they have not expected running WD as on-demand, since its signatures are inferior.
Try to run this as admin via CMD and then update, but I do not think, it will do with MBAM on.

reg delete "HKLM\Software\Policies\Microsoft\Windows Defender" /f

You better report it on MBAM's forum. Version 3 is pretty new, especially as AV, so this is expected.

 

Thanks for quick reply! This doesn't seem to be an issue in 14393 AU, just Insider builds. They (MS) have been mucking around with compatibility of Defender and other AVs. I remember something from earlier installs of MBAM where there was a question of registering it, now it seems to be gone. And I can't find that in Action Center/Settings anywhere. This is on 15031 IP, so nothing would surprise me. Maybe I can't get there from here! *chuckle

Not a critical problem at all. Just wanted to know if there was a hammer I could use on either AV to get them to play nice together. Not sure if MB or MS anticipated this scenario.

Thanks for digging. If you have anything else, or can think of something, please post! TC