Jump to content

REGITDept

Honorary Members
  • Posts

    201
  • Joined

  • Last visited

Posts posted by REGITDept

  1. On 4/29/2020 at 5:35 PM, tetonbob said:

    @REGITDept thanks for your report. The site you link to is currently showing a 500 error

    Please provide:
    - the detection log from C:\ProgramData\Malwarebytes\MB3Service\ArwDetections
    - the MBAMService.log from C:\ProgramData\Malwarebytes\MB3Service\LOGS
    - a copy of the detected file once it's been restore from Quarantine

    Thanks.

     

    Dear tetonbob,

    The ArwDetections is empty (because the Quarantine was restored?).
    Attached you will find the LOGS and a copy of the detected file.

    Thanks.

    logs.zip MBatch.zip

  2. Dear Malwarebytes,

    There is a false positive between Anti-Ransomware and the software called "Multi-Batch".
    It was blocked and quarantined as "Malware.Ransom.Agent.Generic".

    The Multi-Batch website is:  multi-batch.com

    Please fix this ASAP.

    Thanks.

    FP.jpg

  3. 7 minutes ago, exile360 said:

    I'm not certain of the current development status, roadmap or priorities for the Product team, however I would encourage you to reach out to Malwarebytes Business Support if the product is failing to meet your requirements and/or expectations and hopefully they will be able to help you to get the product functioning the way that you desire.  If you haven't done so already, I would recommend contacting them by filling out the form located on this page and hopefully they will be able to provide you with solutions to the issues you are experiencing.

    I have done that exile360.

    They kept telling me they verified the bugs and are fixing it.

    Now it is more than a year and still no updates and fixes.

    Thanks.

  4. 42 minutes ago, scoutt said:

    Sad to say but I think the Management server portion is dead, they have focused 100% on the cloud management service. Which basically puts us organizations out of luck of any updates. Shame as it was starting to look like a good product. Might have to start looking for a different malware product.

    You are correct scoutt.

    They said they will fix this bug more than a year ago but still no fix yet. Looks like they are focusing on the Cloud side like you said.

    It is getting very ridiculous.

  5. On 2/5/2020 at 7:12 AM, LiquidTension said:

    Hi @PhilBurton,

    Thank you for the feedback.

    We've released a fix for this issue in the latest Malwarebytes Anti-Ransomware standalone: https://forums.malwarebytes.com/topic/211708-latest-version-mbarw-beta-v-0918807-build-277-released-feb-4-2020/

    We hope to make this available to other Malwarebytes products in upcoming releases.

    Can you please let me know when the business side is updated?

    Thanks.

  6. 20 minutes ago, tetonbob said:

    Hi all. We are still working towards a solution for this issue but can you try the following exclusions and confirm if it mitigates the issue for you? It does in our testing

    Folder exclusions for the following:
    C:\Program Files (x86)\Common Files\Apple
    C:\Program Files\Common Files\Apple

    Hi,

    We can try again, but we believed we have tried these in the past but not working.
    How about the Windows 10 Store version? What to exclude?
    Both the Windows 10 Store and Standalone versions are affected as well.

    Thanks.

  7. We just got an official email statement directly from Malwarebytes:

    "On December 11, 2019 it was identified that an internal update to our license management system resulted in Malwarebytes Management Console incorrectly indicating that licenses were expired for some customers."

    Thanks.

  8. 1 hour ago, tetonbob said:

    Hi @REGITDept - the screenshot provided in your initial post comes from our standalone Malwarebytes Anti-Ransomware.

    Malwarebytes Endpoint Security includes separate Malwarebytes products, Anti-Malware, Anti-Exploit, and Anti-Ransomware.

    Your Malwarebytes Anti-Ransomware clients should be a version number 0.9.18.806. Prior to the component update package we released last night, it should have been a -1.1.238 and after the latest update, it should be -1.1.242

    0.9.18.806-1.1.242 should no longer throw this False Positive detection.

     

    1.1_242.PNG.02d998dc09e3d5126d4299beec85b2c0.PNG

    Hi tetonbob,

    Our Malwarebytes Anti-Ransomware came from the Malwarebytes Endpoint Security, not standalone. Also what screenshot are you referring to?

    Currently I'm looking at my version which is 0.9.18.806-1.1.242 (See screenshot).

    Thanks.

    MBAR version.jpg

  9. 7 minutes ago, tetonbob said:

    @REGITDept - thanks for your report. I've personally tried reproducing the issue on a variety of Windows 10 hardware and VMs, using the Update Assistant, and Windows Update. On one machine where I ran the Update Assistant, I did get the FP. On others, I did not.

    We're aware of a code issue which is causing this type of false positive and are working on devising a solution. For now, the only workaround is to add an exclusion or temporarily disable the Ransomware Protection while you run the upgrade.

    May I ask, did your Windows 10 upgrade fail when you received this FP detection?

    Dear tetonbob,

    In our environment, the FP is 100% of the time on all of our machines.

    The installation failed 100% of the time.

    Our workaround is to temporarily disabled the protection before running the update.

    Waiting for your status update.

    Thanks.

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.