ESET NOD32 conflict with Malwarebyte's Anti Malware Real-Time protection?

I hope this is of help : at Malwarebytes forums they advise to put the files, mentioned in this thread, in exclusions :

http://forums.malwarebytes.org/index.php?showtopic=47704

Kindly regards,

Mona.

 

Hi, That was my first attempt. Excluding MBAM in Avast! Then it was suggested that I install Start up Delayer from r2 Studios. That worked sometimes. MBAM and Avast! put their heads together and made a fix in the end. But my previous post about heuristics is the deal breaker.

 

Tried that a while back, didn't work. So I just use MBAM to scan weekly and do not run it real time to avoid lock up conflicts.

 

I have never seen conflicts with NOD and MBAM. I know of several people who have both paid version of the software and are able to run along side eachother fine.

Out of curiousity - have you tried booting up in safemode with networking and seeing if updating works?

 

From what I've seen on my computers, the issue arises from the load sequence. On my primary XP machine, MBAM tends to load first and I would have occasional freezes as NOD32 attempts to load, check for updates and run the startup scan. On my Vista machine, the MBAM startup is considerably delayed (by default) and never a problem. I used Startup Delayer [Version 2.5.138] to delay MBAM's loading for 2 minutes on the XP machine and never a problem since. YMMV....