devnulllore Posted August 26, 2012 Share Posted August 26, 2012 Hello friends, I use Norton 360 v.6.0 Final mainly because of working for Symantec I get it for free, but I get no answers from my colleagues on this question as they frown upon using anything besides Norton running at once ALL THE TIME, even when try to explain my situation it falls on deaf ears. I am in the "test" for the next version which I can't talk about further but I use that on my beta test machine. I leave Norton at full blast with all its bells and whistles running all the time. I also purchased Malwarebytes Anti-Malware which I can run all the time or set it as a secondary scanner. This also then turns off Windows Defender. Is it safe, no conflicts, or recommended in any way to run these two together all the time. I do not really see a difference in speed and Malwarebytes does block many "questionable" web sites. Which of those sites are actually bad is a mystery to me but they are in fact blocked. What is the verdict on this and what do YOU do? Thanks, Link to comment Share on other sites More sharing options...
goretsky Supervisor Posted August 27, 2012 Supervisor Share Posted August 27, 2012 Hello, If someone who was using my employer's anti-malware software in conjunction with Malwarebytes' Anti-Malware PRO (the paid-for version of MBAM) asked me this question, I would probably reply along the following lines: The programs may work together, however, we cannot specifically guarantee compatibility with their software. The reason for this is both our software and theirs are updated frequently, and it could be that an update to either program introduces an incompatibility. That said, the programs seem to work together without any major issues right now. I would suggest you exclude the following files from being monitored by our software: for Microsoft Windows XP: %AppData%\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref %ProgramFiles%\Malwarebytes' Anti-Malware\mbam.dll %ProgramFiles%\Malwarebytes' Anti-Malware\mbam.exe %ProgramFiles%\Malwarebytes' Anti-Malware\mbamext.dll %ProgramFiles%\Malwarebytes' Anti-Malware\mbamgui.exe %ProgramFiles%\Malwarebytes' Anti-Malware\mbamservice.exe %ProgramFiles%\Malwarebytes' Anti-Malware\zlib.dll %WinDir%\System32\drivers\mbam.sys %WinDir%\System32\drivers\mbamswissarmy.sys for Windows Vista/Windows 7 (x86) %ProgramData%\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref %ProgramFiles%\Malwarebytes' Anti-Malware\mbam.dll %ProgramFiles%\Malwarebytes' Anti-Malware\mbam.exe %ProgramFiles%\Malwarebytes' Anti-Malware\mbamext.dll %ProgramFiles%\Malwarebytes' Anti-Malware\mbamgui.exe %ProgramFiles%\Malwarebytes' Anti-Malware\mbamservice.exe %ProgramFiles%\Malwarebytes' Anti-Malware\zlib.dll %WinDir%\System32\drivers\mbam.sys %WinDir%\System32\drivers\mbamswissarmy.sys for Windows Vista/Windows 7 (x64) %ProgramData%\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref %ProgramFiles(x86)%\Malwarebytes' Anti-Malware\mbam.dll %ProgramFiles (x86) %\Malwarebytes' Anti-Malware\mbam.exe %ProgramFiles (x86) %\Malwarebytes' Anti-Malware\mbamext.dll %ProgramFiles (x86) %\Malwarebytes' Anti-Malware\mbamgui.exe %ProgramFiles (x86) %\Malwarebytes' Anti-Malware\mbamservice.exe %ProgramFiles (x86) %\Malwarebytes' Anti-Malware\zlib.dll %WinDir%\System32\drivers\mbam.sys %WinDir%\SysWoW64\drivers\mbamswissarmy.sys Likewise, I would suggest excluding our user interface, service(s) and device driver(s) from being scanned by MalwareBytes Pro. If a conflict does occur in the future, it could involve the MBAMProtect driver (filename: mbam.sys ), so disabling this should be the first troubleshooting step. Hope that helps. Regards, Aryeh Goretsky Link to comment Share on other sites More sharing options...
devnulllore Posted August 27, 2012 Author Share Posted August 27, 2012 Hello, If someone who was using my employer's anti-malware software in conjunction with Malwarebytes' Anti-Malware PRO (the paid-for version of MBAM) asked me this question, I would probably reply along the following lines: The programs may work together, however, we cannot specifically guarantee compatibility with their software. The reason for this is both our software and theirs are updated frequently, and it could be that an update to either program introduces an incompatibility. That said, the programs seem to work together without any major issues right now. I would suggest you exclude the following files from being monitored by our software: for Microsoft Windows XP: %AppData%\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref %ProgramFiles%\Malwarebytes' Anti-Malware\mbam.dll %ProgramFiles%\Malwarebytes' Anti-Malware\mbam.exe %ProgramFiles%\Malwarebytes' Anti-Malware\mbamext.dll %ProgramFiles%\Malwarebytes' Anti-Malware\mbamgui.exe %ProgramFiles%\Malwarebytes' Anti-Malware\mbamservice.exe %ProgramFiles%\Malwarebytes' Anti-Malware\zlib.dll %WinDir%\System32\drivers\mbam.sys %WinDir%\System32\drivers\mbamswissarmy.sys for Windows Vista/Windows 7 (x86) %ProgramData%\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref %ProgramFiles%\Malwarebytes' Anti-Malware\mbam.dll %ProgramFiles%\Malwarebytes' Anti-Malware\mbam.exe %ProgramFiles%\Malwarebytes' Anti-Malware\mbamext.dll %ProgramFiles%\Malwarebytes' Anti-Malware\mbamgui.exe %ProgramFiles%\Malwarebytes' Anti-Malware\mbamservice.exe %ProgramFiles%\Malwarebytes' Anti-Malware\zlib.dll %WinDir%\System32\drivers\mbam.sys %WinDir%\System32\drivers\mbamswissarmy.sys for Windows Vista/Windows 7 (x64) %ProgramData%\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref %ProgramFiles(x86)%\Malwarebytes' Anti-Malware\mbam.dll %ProgramFiles (x86) %\Malwarebytes' Anti-Malware\mbam.exe %ProgramFiles (x86) %\Malwarebytes' Anti-Malware\mbamext.dll %ProgramFiles (x86) %\Malwarebytes' Anti-Malware\mbamgui.exe %ProgramFiles (x86) %\Malwarebytes' Anti-Malware\mbamservice.exe %ProgramFiles (x86) %\Malwarebytes' Anti-Malware\zlib.dll %WinDir%\System32\drivers\mbam.sys %WinDir%\SysWoW64\drivers\mbamswissarmy.sys Likewise, I would suggest excluding our user interface, service(s) and device driver(s) from being scanned by MalwareBytes Pro. If a conflict does occur in the future, it could involve the MBAMProtect driver (filename: mbam.sys ), so disabling this should be the first troubleshooting step. Hope that helps. Regards, Aryeh Goretsky Thank You! Link to comment Share on other sites More sharing options...
Recommended Posts