Avast scanning files when MBAM scans them

[fish_hook]

Hello everyone,

I've seen some threads regarding the Avast-MBAM harmony. Mine is a little different. I have Avast 5 installed and the free version of MBAM

Once I got MBAM to do a quick scan on my computer and left it to finish the job. About 30 minutes after that, I returned to an Avast warning (asking me what action to take for badfile.dll) and the MBAM scan halted at badfile.dll.

Hmm... I don;t know how these engines work but is this a conflict? Is it normal to shut down real time AV protection when scanning with MBAM?

Say if I decide to get the Pro version of MBAM with real time protection, can it be activated together with Avast? Both are of different types (so to speak) so I think there won't be any issues?

Hope to hear again. Thanks!

[Firefox]

Hello and

It will not hurt to exclude the files from your Avast, please excluded them and try the scan again....

Please exclude the following files from your Antivirus (not sure what version of you are using):

Note: If using a software firewall besides the built in Windows Firewall you'll need to exclude them from it as well

For Windows XP:

• C:\Program Files\Malwarebytes' Anti-Malware\mbam.exe
  
• C:\Program Files\Malwarebytes' Anti-Malware\mbamgui.exe
  
• C:\Program Files\Malwarebytes' Anti-Malware\mbamservice.exe
  
• C:\Program Files\Malwarebytes' Anti-Malware\mbam.dll
  
• C:\Program Files\Malwarebytes' Anti-Malware\mbamext.dll
  
• C:\Documents and Settings\All Users\Application Data\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref
  
• C:\Windows\System32\drivers\mbam.sys
  
• C:\Windows\System32\drivers\mbamswissarmy.sys
  

For Windows Vista or Windows 7:

• C:\Program Files\Malwarebytes' Anti-Malware\mbam.exe
  
• C:\Program Files\Malwarebytes' Anti-Malware\mbamgui.exe
  
• C:\Program Files\Malwarebytes' Anti-Malware\mbamservice.exe
  
• C:\Program Files\Malwarebytes' Anti-Malware\mbam.dll
  
• C:\Program Files\Malwarebytes' Anti-Malware\mbamext.dll
  
• C:\ProgramData\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref
  
• C:\Windows\System32\drivers\mbam.sys
  
• C:\Windows\System32\drivers\mbamswissarmy.sys
  

For 64 bit versions of Windows Vista or Windows 7:

• C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbam.exe
  
• C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbamgui.exe
  
• C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbamservice.exe
  
• C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbam.dll
  
• C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbamext.dll
  
• C:\ProgramData\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref
  
• C:\Windows\System32\drivers\mbam.sys
  
• C:\Windows\SysWoW64\drivers\mbamswissarmy.sys
  

Note: If using a software firewall besides the built in Windows Firewall you'll need to exclude MBAM.EXE and MBAMSERVICE.EXE from it as well

Note: Once that's done, please make sure that if either of those programs has any sort of web filter, that you add the following as a trusted site:

data-cdn.mbamupdates.com

The FAQ contains examples of setting file exclusions for some known AV products

Please post back and let us know how it went.

[fish_hook]

Hi Firefox,

Thanks for the reply. I did that already. Not sure if it'll appear anytime soon (I think my computer's clean now).

Avast didn't flag MBAM's files as bad. Rather, each time MBAM detects a bad file, Avast will pick it up too. And in the process, halting MBAM. I thought on-demand scanners and a real time protection can live in harmony.

But then again, Firefox, it's no big deal I guess. I'd just stop Avast when scanning on MBAM and then turn on the real time when MBAM's done.

B)

[ThexDarksider]

It happens with other realtime antimalware programs too. MBAM (or any other on-demand scanner, for that matter) accesses the file like any other normal program and the realtime protection is triggered. Either disable Avast and scan with MBAM, or scan with Avast first, and then with MBAM. The latter is probably better because if you have one piece of malware, more may be waiting to activate.

[fish_hook]

It happens with other realtime antimalware programs too. MBAM (or any other on-demand scanner, for that matter) accesses the file like any other normal program and the realtime protection is triggered. Either disable Avast and scan with MBAM, or scan with Avast first, and then with MBAM. The latter is probably better because if you have one piece of malware, more may be waiting to activate.

Thanks ThexDarksider. Something new to me...

[Firefox]

It happens with other realtime antimalware programs too. MBAM (or any other on-demand scanner, for that matter) accesses the file like any other normal program and the realtime protection is triggered. Either disable Avast and scan with MBAM, or scan with Avast first, and then with MBAM. The latter is probably better because if you have one piece of malware, more may be waiting to activate.

Agreed...