acr

Member
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About acr

  • Rank
    Member
  1. I did as you instructed but Mamutu needed restarted again today.
  2. Automatic updates are enabled with Mamutu. I don't log off Windows every night. Normally I leave my computer running all the time (reboot maybe once every week or so) and only have to use my password to sign back into my admin account. I run admin all the time, if that makes any difference.
  3. I followed the instructions you provided, rebooted, etc. This morning I noticed Mamutu needed restarted again. So no fix as of yet.
  4. I already had those programs' whole folders excluded but I will also add that those individual processes. BTW- how did you know I had Malwarebytes installed?
  5. Why do I need to restart Mamutu every night? It seems like these restarts are needed after every update. Other people I know who use Mamutu claim they do not have to restart. It is starting to be a pain. I have Windows 7 Ultimate, 32 bit.
  6. Thanks for the info. I will book mark so I have it for future reference. For now I decided to disable Eset HIPS and install Mamutu instead of the entire Emsi program. It seems to be working together fine for the last 3-4 days. I'll try Eset with Emsi and exclusions soon to see how that goes.
  7. I realize Emsi has nice protection but I desire to run Emsi anti-malware along side Nod32 version 5 if possible. I wish to disable the Nod32 HIPS and have Mamutu handle the behavior monitoring. I would like to know what settings I would need to make to ensure each product is not scanning the other. Would I need to disable the Emsi on access scanning if I plan to keep Nod32's on access scanning active? thanks