Jump to content

tetonbob

Staff
  • Content Count

    1,314
  • Joined

  • Last visited

4 Followers

About tetonbob

  • Rank
    Staff

Recent Profile Visitors

20,847 profile views
  1. Hi @TheQuickFox - while this FP had already been addressed by Djordje, we'd like to try to understand the cause of the detection. Can you please collect and upload the diagnostic data using our MBST? Download and run the Malwarebytes Support Tool Accept the EULA and click Advanced tab on the left (not Start Repair) Click the Gather Logs button, and once it completes, attach the zip file it creates on your desktop to your next reply Thanks!
  2. Hi Tracy. I'm glad that the issue is resolved for you now that you're on the latest version. As Porthos says, new releases are metered over time.
  3. @TD351 - according to the logs you provided, your Malwarebytes product is not current. Controllers Version: 1.0.835 For the fix for the iTunes issue, you need to be on Controllers version 1.0.854 See:
  4. I'm not sure this will work, but can you try adding this folder to your exclusions? C:\Program Files (x86)\Common Files\Microsoft Shared\Virtualization Handler
  5. Thanks for letting us know you see the same as we do! And thanks again for your report 🙂
  6. Hi guys. See part 3 of Becky's reply here:
  7. @LoWd0Wn - yes, you can remove those 2 folders from your Allow List.
  8. I'd meant to post this sooner. Components Update: 4.1.0.56 version 1.0.854 was released Wednesday March 18.
  9. I'd meant to post this sooner. Components Update: 4.1.0.56 version 1.0.854 was released Wednesday March 18.
  10. Hi @throkr - thanks for letting us know. That would certainly explain it. 🙂 We've filed a defect for the original issue you've reported in this topic.
  11. Hi @throkr - I see the reason for what you are now seeing but not the cause. While your Component package version does indicate the Beta version, the file versions are not. mbam.exe for example should be 4.0.0.594 but mb-check-results.txt shows 4.0.0.591 (version from our current release build), which would explain why the Dashboard text is showing as expected again. arwlib.dll should be 3.1.0.817 but mb-check-results.txt shows 3.1.0.803 I need to be away from the PC for some hours. We'll investigate.
  12. Hi @throkr - Can you please collect and upload the diagnostic data using our MBST? Download and run the Malwarebytes Support Tool Accept the EULA and click Advanced tab on the left (not Start Repair) Click the Gather Logs button, and once it completes, attach the zip file it creates on your desktop to your next reply
  13. Hello, @throkr - you should not be able to receive the Beta CU version 1.0.853 unless Beta updates is enabled. Please confirm the 'Component package version' you're on. I see the same as you do, with 1.0.853. The banner wording 'Awesome! Your computer is protected.' is not translated.
  14. Hi @jimsarles - that's great news! Thank you for confirming the fix we made for this issue is working for you as well as us! Thank you also for your patience. 🙂 Regarding staying in Beta long term, that is entirely up to you. As Maurice suggests, it would make sense to remain in Beta mode until we make the next release generally available. This is to ensure you get any Beta refreshes we might make ahead of that release. That being said, there are no further changes planned for the Ransomware Protection component in this next release. We truly appreciate all our customers, and our Beta participants. Thank you once again!
  15. Understood. Thanks for helping us understand your situation so quickly.
×
×
  • 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.