Malwarebytes

Malwarebytes found things esetNOD32 doesn't catch (malware ... spyware ... adware). I would like to purchase/run Malwarebytes but I understand
that I may have to add the following files to the exclusions list in your anti-virus software before starting the protection module:

C:\WINDOWS\system32\drivers\mbam.sys
C:\WINDOWS\system32\drivers\mbamswissarmy.sys
C:\Program Files\Malwarebytes' Anti-Malware\mbam.exe
C:\Program Files\Malwarebytes' Anti-Malware\mbamgui.exe
C:\Program Files\Malwarebytes' Anti-Malware\mbamservice.exe

I'm not computer savvy and don't want to start manually editing eset ...

Will Malwarebytes run harmoniously with esetNOD32 without those edits?

 

If you set up one another to exclude each other it should.. I'd recommend PrevX with NOD32 though.. I've not found anything else to play as nicely with ESET.. The free scanner with MBAM is enough..

 

Thanks so much. I'll look into PrevX. Will I need to edit anything? You would leave Malwarebytes (free version) for manual scans?

 

PrevX is a good choice and yes leave MBAM for manual scans.

 

Yes, I would use PrevX 3.0, and NOD32 to run together.. I would setup exclusion so NOD32 wouldn't scan PrevXs files, and vice versa.. PrevX specializes mainly in malware... If you notice that is what most of the AV companies have a hard time keeping up with..

 

i tried spyware doctor, super anti spyware pro, ad-aware pro and spy sweeper, all played very well along nod32. i had to make exclusions for spyware doctor i think.

 

MBAM and NOD32 play well together without any issues and not requiring any tweaks on either program.

 

Yes, the Mchdriver file that went inside of Threatfire was being picked up as malware for a while.. I would install NOD32 first, disable protection, and then install Spyware Doctor V6 with AV.. Then after it installed setup NOD32 to exclude Spyware Doctor V6, and threatfire to exclude Eset.. Turn them back on, and they played nice..

 

>>mch driver
--> https://www.wilderssecurity.com/showthread.php?t=249826

In the early days eset warn about mbam files - but now: nothing

i would recommend mbam before prevx - prevx (free is only scan - no fix)
(although - fixing aint really possible)

btw eset have no problem with a2 (free) and mamutu too.