Excluding items

[Asyn]

Asyn do you run MBAM PRO ?

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

[CraigB]

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.

[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

[CraigB]

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.

[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

[CraigB]

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.

[Asyn]

Will do.

Thanks..!

[YoKenny]

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.

[DavidR]

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.

[Asyn]

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

[CraigB]

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.

[DavidR]

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.

[CraigB]

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

[DavidR]

You're welcome.

[YoKenny]

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.