Excluding items

I am using Avast Internet Security 5. I’ve been debating now for some time about whether to purchase Malwarebytes and use the free SUPERAntiSpyware ---- or purchase SUPERAntiSpyware and use free Malwarebytes. I’ve decided to purchase Malwarebytes.

I went to their forum and they gave me a whole list of things to exclude in Avast, including one item to exclude under the firewall. If this is necessary, then do I need to exlude Avast items in Malwarebytes as well?

These are the items I was told to exclude in Avast:
* 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

As this item was included as well:
Note: If using a software firewall besides the built in Windows Firewall you’ll need to exclude MBAM.EXE from it as well

Thanks

I use the paid version of the software that you mention. I could possibly miss SAS but NEVER Malwarebytes antimalware.

I used to have both SAS and MBam together but found SAS much heavier on my OS. I too would not be without the power and reliability of MBam! :slight_smile:

I really appreciate the answers I received, but no one answered the question about the things to exclude.

Hi Nikilet :slight_smile:

As far as I know the exclusions are not realy needed, but they just speed up the MBAM scanning :slight_smile:

Greetz, Red.

According to the MBAM forum, this was posted by one of our Evang. in another thread:

If you decide to install the Pro version of MBAM, you will have to add the exclusions into the file system shield and to the exclusions in settings.

For Windows XP: CODE 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 and Windows 7: CODE 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 and Windows 7: CODE 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

These will need to be added one at a time.

This was written when MBAM was v.1.46, and the version has since changed to 1.50. So you may want to verify with the MBAM forum. In the meantime, it can’t hurt to add the exclusions to be on the safe side.

Not needed. :wink:
asyn

I needed to use it on a Vista using MBAM Pro but only added some of the exclusions listed above. Pro is resident protection. Someone’s update, not sure who…caused MBAM to become a FP and I did not have MBAM as an exclusion. Since then I’ve had no problems. This information came from the MBAM forum itself.

Well, there was an issue with swissarmy some time ago, but this has been corrected, I don’t know of any problems right now…
asyn

I do think the MBAM 1.50 is much better, so perhaps this has fixed things.

I don’t know, which issue(s) you had…???
But sure, we don’t need to discuss old problems with new versions. :wink:
asyn

The exclusion’s may or may not be needed but from the info and advice that was supplied to me by the MBAM moderator’s is that the exclusion’s should be placed into all av’s that are running alongside MBAM. Nikilet you can add the avast program file to the ignore list in MBAM, might not be necessary but i always exclude my security software from one another just in case, i dont want any lockup’s :slight_smile:

Good suggestion for now until we confirm with MBAM. I am very familiar with Nikilet’s machine nightmare history, and I am sure the OP does not need another problem.

No problem, but keep in mind, that if any of your security programs files should get infected somehow, the other program would be unable to find it, if you excluded it from scanning… :wink:
asyn

Im just doing what the power’s that be suggest to do.
Asyn do you run MBAM PRO ?

Not here.
But I have some machines where it’s running.
asyn

Going on what the MBAM MOD’S/TEAM has said to me previously is that xp and vista should definatly have the exclusion’s, there has only been a few issue’s with win 7 on some systems but the exclusion’s are still recommended as a preventitive. I might actually delet my exclusions just to see what happen’s for a test. :-\

When did they tell you…? Could be outdated information by now…
Anyway, if they tell you to add them as ‘preventive’, it’s up to you. :wink:
asyn

Was on version 1.46 when this was discussed but the basic scanning format has not really changed, if anything the scanning is even more through. My test will tell, only for win 7 though.

Well, it depends what you’re refering to, as also the problem with the swissarmy was already resolved in 1.46…
If you test it, post your feedback, as it would surprise me, if you should find any problems. :wink:
asyn