RESIDENT MBAM PROTECTION ALONG AVAST RESIDENT PROTECTION

[Avastfan1]

I've never had a problem with c:\windows\temp\_avast_ ??

[DavidR]

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 

I appreciate that, I too cant understand avira's thinking on this.

[DavidR]

I've never had a problem with c:\windows\temp\_avast_ ??

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.

[Avastfan1]

That is a really interesting point you make. Thanks for the heads up!

Avast can scan everything which MBAM does not flag in that folder. Hence there will always be a report if something suspicious turns up there.

Not known to MBAM: Avast can scan it
Known to MBAM: MBAM alerts the user.