Any time you add another layer of ‘real time’ security monitoring, there is likely to be some impact on the OS resources. Amount of RAM and CPU strength also come into play.
Conflicts can also come from other software installed.
Conflicts also will vary from one OS to another.
The one real way to know is go ahead and run what you want and monitor results/consequences.
You can always uninstall or disable “start up” settings in MBam. Always have a back up image before testing anything with uncertainty.
While schmidthouse is correct, in this particular case the odds of success are probably in your favor. Quite a few of us, including myself, happily run avast and MBAM Pro/Premium together. One thing you might want to do is add exclusions in each program to the other’s operating folder, so that definitions don’t trigger alerts.
Avast + MBAM + I also have MBAE (anti exploit free) as well…you can read my signature for how I stack my protection.
If you ask you will get many answers on “what” you need and “which” is best…I pretend to be no expert but my combo “for me” offer very good layered protection with min penalty.
To be honest…Avast is the one that takes the cycles from your PC…MBAM/MBAE are light in comparison…but all running work fine and I’ve been using for years.
A little dated but: https://blog.malwarebytes.org/news/2013/08/malwarebytes-av-compatibility-report/
Those exclusions are rather old now Bob, though they are still services there have been many more implemented into MBAM since version 2 came out and it’s easier just to exclude the Program file and Program Data file.
I always exclude my security software from one another, it’s not just for detection issues but helps with system performance ( not that it matters running the free version )
There’s also the two files in Windows\System32\drivers
“C:\Windows\System32\drivers\MBAMSwissArmy.sys” which has been known to be flagged now and again and “C:\Windows\System32\drivers\mbamchameleon.sys”
The only exception I set was to stop MBAM scanning the temp C:\Windows\Temp_avast_ so it doesn’t scan the folder that avast unpacks/sends data to be scanned.