Jump to content

mbamswissarmy.sys


Recommended Posts

Hi, DougBar:

No need to exclude that file.

IIRC, with the latest version of MBAM, that file is created anew anew during a scan.

I'll see if I can find a recent post about this, but I'm pretty sure that's the case. I think these are the only 3 exe files that need to be excluded:

  • mbam.exe
  • mbamgui.exe
  • mbamservice.exe

In general, it is a good idea to set the reciprocal exclusions/permissions between one's AV and MBAM.

Many people experience no problems whatsoever without doing so.

However, it's usually recommended in order to optimize performance.

daledoc1

PS FYI There has been a known issue between ESET NOD32 and MBAM when using USB external HDDs -- AFAIK, both companies are working to resolve it. It may only apply to WinXP, but I'm not sure. I'm not sure of the status of the fix. Here is a link to a recent thread: http://forums.malwar...howtopic=107829 and: http://forums.malwar...ndpost&p=560797 and http://forums.malwar...ndpost&p=559998

Link to post
Share on other sites

Also, should I exclude all of the stuff in the pinned FAQ?

"In general, it is a good idea to set the reciprocal exclusions/permissions between one's AV and MBAM." what does that mean?

Hi, Dougbar:

You had asked if you should "exclude all of the stuff in the pinned FAQ" and your topic is about setting exclusions.

So, I had replied that, yes, it is generally a good idea to configure mutual trust settings ("exclusions") between MBAM and your AV.

That is what I meant (and what I thought what you were asking about in the first place). :)

It just means configuring both programs to "ignore" each other.

Sorry if I wasn't clear. :(

Doing so permits both programs to work fully with less chance of minor conflicts or performance degradation on the system.

So perhaps I misunderstood what you meant when you asked about "all of the stuff in the pinned FAQ"??? :(

If you are already running both MBAM and ESET and are not experiencing any issues, then you should be fine.

If you need additional help with the specific steps to "exclude" the programs from one another, then please let us know.

I don't personally know the exact steps for ESET (since I don't use it), but one of the MBAM staff or another member will be able to help.

To tell MBAM to ignore ESET:

  • Open Malwarebytes' Anti-Malware and click on the Ignore List tab
  • Click the Add button on the lower left
  • In the small browse window that opens, navigate to C:\Program Files and click once on ESET and click OK
  • Click the Add button on the lower left
  • In the small browse window that opens, navigate to C:\Program Files\Common Files and click once on ESET and click OK
  • Close Malwarebytes' Anti-Malware

HTH,

daledoc1

Link to post
Share on other sites

UPDATE:

Hi, again, Dougbar:

I just found your original topic >>HERE<<. :)

According to >>THIS POST<< by forum admin, AdvancedSetup, you ought NOT to need to set exclusions for MBAM in ESET.

So, you should be just fine, if everything is working OK. :)

(However, there is a link in >>THIS POST<< by Firefox for steps on how to do so, if you'd like. It's for ESET v4, but I expect the process would be similar.)

daledoc1

Link to post
Share on other sites

I had to revert back to 4.2.71.2 because I had some problems with v5. I just added mbam.exe, mbamgui.exe, and mbamservice.exe. I will try that and see what happens. Those were all the ones that I was originally talking about in my first thread. Didn't know if I had to exclude all of them or not.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.