system
1
Can I use both? Do I need to put avast on ignore list? Or do they work together? Thanks
CraigB
2
Yes you can run both together, exclusions ? being the suite i would probably add them but may not be needed, if you notice any problems then add the exclusions.
system
3
DavidR
4
Yes that is the MBAM line, but in reality it can be a different story.
I have MBAM Pro on XP Pro and win7 systems and the only exclusion I have set up is to stop MBAM scanning the folder where avast unpacks/scans files, c:\windows\temp_avast_. I make no other allowances in either MBAM or avast and I have not had a problem.
system
5
Thanks for the info, but is this for the old Mbam? Because I read in “Introducing \New Official Avast Program Update 6.0.1125” that - solved a compatibility problem with Malwarebytes Anti-Malware Pro. I was just wandering, and it seems to be running fine. I am a novice to computers, so any info will help.
Thanks again for your help.
DavidR
6
Other than the exclusion I mentioned on the avast working folder where it unpacks and scans content (c:\windows\temp_avast_), then I wouldn’t pre-empt any problem and set exclusions unless you do experience an issue.
I use AIS and MBAM(PRO) and have had no problems whatsoever. I have added the exclusions to both AIS & MBAM just to be sure. I am very happy with them both 
system
8
I don’t mean to annoy you, but could you tell me step by step on how to do that?
Thanks for your patience.
CraigB
9
Open up the MBAM GUI and click on the ignore list then the add button and navigate to the path DavidR supplied c drive / windows / temp / avast highlight and click ok.
system
10
Thank You, I did what you said, but i saw two Avast files one of them is c drive / windows / temp / avast and the other is c drive / windows / temp / avast 5 I did both. Should I be concerned or do you think it does not matter?
Thanks again
DavidR
11
If you did a clean install the avast5 folder related to the old installation (should be empty) and is redundant. The new c:\windows\temp_avast_ folder is for the new/clean installation of avast.
system
12
That is exactly what happened.
Thanks again