gdiloren if you dont believe us that MBAM Pro works in unison with avast maybe you should checkout what Malwarebytes have to say, ( note revised rules for exclusions between Avast 6 and Malwarebytes Pro ) http://forums.malwarebytes.org/index.php?showtopic=10138 scroll to section K.
Having just read the revised list, I still think they are wrong. They are pretty much guessing how avast works in relation to MBAM.
I don’t know what they were thinking up when they though to have you exclude *.mbamupdates.com in the web shield; when presumably this is for mbam updates that wouldn’t be accessed via your browser and as such not scanned by the web shield.
They have as far as I’m concerned missed the most essential exclusion and that is one which should be applied in the MBAM Ignore List, c:\windows\temp_avast_ where avast unpacks/sends data to be scanned. We have seen in the forums many instances of MBAM Pro making detections in this folder, on the unpxxxxxxx.tmp files that avast is creating there so that they can be scanned. This is a direct conflict as MBAM would have hooked these files so it mbam can scan them, this means avast can’t actually scan them, it also stops avast clearing this folder after the scan.
I still maintain there is no need to exclude the MBAM folder and I have MBAM Pro on win7 and XP Pro and no issues at all with no MBAM exclusions in avast. I have always considered exclusions something they you should apply only if a) you have a problem and b) after full investigation.
So I don’t go pre-empting something which hasn’t happened, if there is a problem then I exclude the specific file and not a complete folder (unless it relates to multiple randomly named files in a folder as in the example above) as that introduces a hole your security.
I did the same thing when I was using SAS Pro's resident protection only having it exclude c:\windows\temp\_avast_.
I applied the same approach in Outpost Firewall Pro (OFP), I haven't excluded its program folders in avast or vice versa. I have one single file that I exclude for OFP in the file system shield and that is C:\Program Files\Agnitum\Outpost Firewall Pro\wl_hook.dll.
As I said I don't pre-empt problems that I haven't experienced or seen in these forums, etc.
Good spot David, i actually didnt read thoroughly there revised exclusions as im also only using the windows temp one like yourself but i mainly posted it for gdiloren as a piece of evidence from malwarebytes that avast and MBAM pro do run nicely together even if they have screwed up the exclusions ;D
I haven’t had a problem with it either, but I have seen numerous such instances in the viruses and worms forum, to make a decision it is something to avoid. If mbam hooks files in this folder as they are created then that would prevent avast from scanning them.
The other aspect is the c:\windows\temp_avast_ temp folder would otherwise be empty if it weren’t for avast unpacking/moving tmp files here to be scanned, since they are temporary and will be removed by avast after scanning any hooking/scan by mbam in this folder is redundant, duplication, which adds to system resource use.