Include MBAM Exclusions.conf

[Xander / Prompt Care]

Nick, it seems like there's been some MBAM conflict of late between it and some of the AVs.  So I thought it might be beneficial to start pushing my exclusions onto systems, much in the same way you're already doing with offline definitions but applied more universally.

"C:\ProgramData\Malwarebytes\Malwarebytes' Anti-Malware\exclusions.dat"

I've confirmed this is the file by checking its timestamp after I'd just added an exception.

Side note:  I would absolutely love to be able to import/export my general settings for new installs (e.g. increasing the updates to 8hrs, adding a couple of scheduled scans, automatically check PUPs) but I have not yet been able to figure out where MBAM saves this info.

[Foolish Tech]

gonna require some thought.  more complicated than just copying the exclusions.conf after it is modified by you - don't want D7 automatically doing it just because it is there - on the off chance you are using MBAM already on the system and it has been compromised.  

another thought is, how does the exclusions work?  if you excluded something in \program files\ on a 32 bit system would it then mark that properly as \program files (x86)\ on a 64 bit system?

[Xander / Prompt Care]

I'm not sure if it carries over from x86 to x64 in that way.  It stores them as full paths so probably not.  You'd need to build up an entry for each variation.

My main thought was to build up a 'master' Exclusions file for the more common AVs (and ScreenConnect, for good measure).  I faked it out a bit by creating a "C:\Program Files (x86)/Avast Software" folder and adding that, even though I don't run Avast.  You just need a folder to point it at, though you could be more specific and point it to individual files.

(Might not hurt to add in paths for things like Quickbooks for its Connection Manager.)