New Version of Avast has impacted mbam

[Russell C]

A couple of days ago I attempted installing Avast's new version 5. This was not successful and I have reverted to version 4.8.

After the unsuccessful installation my Comodo firewall started going off every few seconds, warning about what mbam was trying to do. After repeatedly being told mbam is a trusted application it had a nice cup of tea and a lie down.

However one hangover of this event is that mbam is now denied access to notepad. I can run a scan and get a result, but it can't generate a log.

Why an AV app can have this effect on an antimalware app is a mystery to me, and suggestions would be welcome. B)

[exile360]

Greetings and welcome B)

It's possible that you need to exclude/trust Avast! 5's files/processes from Comodo as well for it to work. Aside from that, please make sure that you're running the latest version of Avast! 5 as one of the earlier versions did have issues with Malwarebytes' Anti-Malware and please be sure to exclude/trust these for both your antivirus and your firewall:

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\zlib.dll
  
• 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\zlib.dll
  
• 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\zlib.dll
  
• 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
  

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

[Francois_Blais]

I suggest you browse the AVAST forum.

There have been several threads about the problems between AVAST 5 and MBAM real-time.

I started a thread myself here about that earlier this year.