Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Nikilet on December 05, 2010, 12:14:57 AM
-
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! :)
-
I really appreciate the answers I received, but no one answered the question about the things to exclude.
-
Hi Nikilet :)
As far as I know the exclusions are not realy needed, but they just speed up the MBAM scanning :)
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.
-
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.
Not needed. ;)
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.
-
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 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. ;)
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 :)
-
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 :)
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.
-
...i always exclude my security software from one another just in case, i dont want any lockup's :)
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... ;)
asyn
-
...i always exclude my security software from one another just in case, i dont want any lockup's :)
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... ;)
asyn
Im just doing what the power's that be suggest to do.
Asyn do you run MBAM PRO ?
-
Asyn do you run MBAM PRO ?
Not here.
But I have some machines where it's running.
asyn
-
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. :-\
-
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. ;)
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. ;)
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.
-
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. ;)
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. ;)
asyn
Will do.
-
Will do.
Thanks..!
-
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.
Not needed. ;)
asyn
Not true!
Quit offering advice on Vista and Windows 7 as you do not know it!
Plus you are not running Avast Internet Security 5 as you are running Comodo.
-
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 :)
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.
The biggest potential for conflicts is in the _avast5_ sub folder of Temp (C:\WINDOWS\Temp\_avast5_) as that is where avast unpacks/scans files and the last thing you want is another resident scanner locking files in this area. So that is an area I would exclude in MBAMs real-time scanning.
-
Quit offering advice on Vista and Windows 7 as you do not know it!
Plus you are not running Avast Internet Security 5 as you are running Comodo.
Well, Kenny - I administrate a lot of systems..!
Looking at my sig only tells you about this one... ;)
asyn
-
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 :)
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.
The biggest potential for conflicts is in the _avast5_ sub folder of Temp (C:\WINDOWS\Temp\_avast5_) as that is where avast unpacks/scans files and the last thing you want is another resident scanner locking files in this area. So that is an area I would exclude in MBAMs real-time scanning.
Is that the only area you would exclude DavidR for AVAST FREE and MBAM PRO, iv deleted all my exclusions as a bit of a test but at the same time im worried what might happen.
-
Personally if I had MBAM pro, yes that would be the only area I would exclude as there is a direct interaction there in relation to real-time scanning. Other than that I wouldn't exclude any MBAM files in avast unless it was proven it was necessary, e.g. a detection by avast.
-
Personally if I had MBAM pro, yes that would be the only area I would exclude as there is a direct interaction there in relation to real-time scanning. Other than that I wouldn't exclude any MBAM files in avast unless it was proven it was necessary, e.g. a detection by avast.
Thank's for that, i'll add that exclusion to MBAM now :)
-
You're welcome.
-
Quit offering advice on Vista and Windows 7 as you do not know it!
Plus you are not running Avast Internet Security 5 as you are running Comodo.
Well, Kenny - I administrate a lot of systems..!
Looking at my sig only tells you about this one... ;)
Then why do you not post about the Windows 7 system you are running. ???
I'm running 2 and others are running more than that.
-
Then why do you not post about the Windows 7 system you are running. ???
I'm running 2 and others are running more than that.
All these systems wouldn't fit in my sig. (40+ atm) ;D
asyn
-
Then why do you not post about the Windows 7 system you are running. ???
I'm running 2 and others are running more than that.
All these systems wouldn't fit in my sig. (40+ atm) ;D
asyn
So you pick the worst one. ;D
-
So you pick the worst one. ;D
I picked the one that fits best for this machine...!! ;)
asyn
-
So you pick the worst one. ;D
I picked the one that fits best for this machine...!! ;)
asyn
You do not show system specifications nor XP Home nor Pro.
So you support 40 systems.
I hope you are payed well.
You have a lot of poor un-aware system users that barly know where the Power On button is and you proffer advice. ::)
-
I hope you are payed well.
Don't worry, I am... ;D 8)
asyn
-
I thank you all for the input, but to be honest, it was almost too much info for me to filter through. At this point I'm not sure what to do so I'm going to start with DavidR's advice: The biggest potential for conflicts is in the _avast5_ sub folder of Temp (C:\WINDOWS\Temp\_avast5_) as that is where avast unpacks/scans files and the last thing you want is another resident scanner locking files in this area. So that is an area I would exclude in MBAMs real-time scanning.
DavidR, as I understand things then, I should make no exclusions in Avast, but make this exclusion in MBAM? Do I enter this just as you show it then? (C:\WINDOWS\Temp\_avast5_)
-
I thank you all for the input, but to be honest, it was almost too much info for me to filter through. At this point I'm not sure what to do so I'm going to start with DavidR's advice: The biggest potential for conflicts is in the _avast5_ sub folder of Temp (C:\WINDOWS\Temp\_avast5_) as that is where avast unpacks/scans files and the last thing you want is another resident scanner locking files in this area. So that is an area I would exclude in MBAMs real-time scanning.
DavidR, as I understand things then, I should make no exclusions in Avast, but make this exclusion in MBAM? Do I enter this just as you show it then? (C:\WINDOWS\Temp\_avast5_)
You navigate to that folder through the add button in MBAM ignore list then highlight it and click ok.
-
OK - thanks a lot!