Jump to content

Rix643

Members
  • Posts

    4
  • Joined

  • Last visited

Reputation

0 Neutral
  1. Hi @LiquidTension, Thanks for the explanation! No, I don't have the option to add partial filenames/use wildcards. The whitelisting is based on complete path/filename plus file characteristics like creation date et c. Switching real time malware protection off seems to do the trick, I haven't seen the whitelisting request for some time, and scans seem to work. I can live with this for now, but I hope in a future release there will be an option to turn this behavior off. I rather have a weak malware protection layer than none at all. Regards, Rick.
  2. Thanks for your reply. Unfortunately I cannot whitelist programs based on their location or vendor. For now I disabled automatic scan and see whether the whitelist request returns or not. If it does I'll keep disabling protecting options until notions stay away, so I'll know which part is responsible. Hopefully the developers will come with a solution for this, perhaps an option to turn this behavior off.
  3. I use Malwarebytes with a child-account, having set up Family Safety to only allow programs to run which are whitelisted. However, the latest version of Malwarebytes keeps creating new versions of ig.exe, like ig-0.exe, ig-1.exe, ig-2.exe, when starting an automated scan. These have to be whitelisted again and again. It is getting quite annoying. Can you stop creating new instances of ig.exe? Does it affect the scan when not allowing the new instances to run? I noticed the scan starts anyway. Anyone else having this issue?
  4. Same problems here. Uninstalled using mb-clean-3.1.0.1031.exe, re-installed mb3-setup-consumer-3.3.1.2183-1.0.262-1.0.3791.exe, immediately turned off 'automatically download and installing application component updates' and re-installed the license while ignoring the license server error (license gets installed anyway). It's still running without the RAM hogging, and real-time web protection stays on. Software version is now 3.3.1.2183, Component package version: 1.0.262, Update package version 1.0.3791. It seems the fault is in Malwarebytes' last update.
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.