tetonbob

Moderators
  • Content count

    809
  • Joined

  • Last visited

1 Follower

About tetonbob

  • Rank
    Staff
  • Birthday

Recent Profile Visitors

15,427 profile views
  1. Hi @miguelgrado - thanks for your report. I've been able to reproduce this issue and reported it to the team.
  2. Hi @randykates - I'm not seeing any issues when attempting to use the Add File button to add a batch file (.bat) to Exclusions.
  3. Hi @cchilderhose - It appears you've received a reply to your support request. Since you do have an open ticket with Support, I'll close this forum topic. Thank you!
  4. Hi Paul. Thanks for letting us know that the issue is resolved. Typically when this inability to delete the mbar folder takes place, the mbamchameleon self-protection driver that is part of MBAR is still running for some reason. It is supposed to unload when MBAR exits. Sometimes a reboot or two will resolve that.
  5. Hi PaulAllen. Do you also have Malwarebytes Anti-Malware or Malwarebytes 3.0 installed? If so, is self-protection enabled?
  6. Hi @ceez - thanks for confirming that the Component Update 1.1.19 fixed this issue for you!
  7. Hi @bluenotemk- I'm glad to hear that the solution in Component Update 1.1.19 worked for you as well. Thanks for posting!
  8. @ron_hk - thanks for the logs. I can see in the MBAMService.log that indeed this detection was discarded as whitelisted. We'll forward this information to our Developers for review. We would consider this a false positive in that there was a detection, but no quarantine attempt took place. There should be nothing further for you to do.
  9. @royaljackv - If you see in the Report "No action by user" like in ron_hk's image, with the Anti-Ransomware component this means the detection was discarded. It's most likely been internally whitelisted. That being said, we'd like to know more about why there was a detection at all of this particular csrss.exe since that is a legit location for this file.. For that, we'd like the MBAMService.log which Dave mentioned in his previous post. Additionally, we'd like the .arw files located here: C:\ProgramData\Malwarebytes\MBAMService\ARW < copy this folder to desktop and zip it if there are multiple .arw files. Thank you.
  10. Hi @DFLO. Thank you for confirming!
  11. Great, thanks for letting us know that part of your report is resolved.
  12. Hi ingber. Currently, a file in a 64bit directory such as system32 on a 64bit system cannot be added to exclusions. However, you should be able to add the \lxss folder to exclusions. To do so, you'll need to ensure you have unchecked the 'Hide protected operating system files (Recommended)' option in your Explorer > View > Options > Change folder and search options > View See my attached image.
  13. Hi Jim_Lafleur. Our Anti-Ransomware technology is in fact already integrated in our next flagship program, Malwarebytes 3.0 which is now in Beta testing: Thanks for your interest.
  14. Hello moo4x, and thank you for your interest. Malwarebytes Anti-Ransomare technology is for Windows 7 and newer operating systems only. It will not run on XP or Vista. Thank you.
  15. Hi baskon. We apologize for the inconvenience and thank you for Beta testing. The uninstall and reinstall should resolve the issue of repeat notification of an impending program update.