Jump to content

Jekko

Staff
  • Posts

    365
  • Joined

  • Last visited

Posts posted by Jekko

  1. Zero response from Malwarebytes sales or support so far. We were able to find the license email, it was emailed to an ex-employee's inbox. I don't know why they had to change their license code structure and break it, it should have just renewed as it has in previous years. I can't believe they'd release an update that would false positive on an important OS file, you'd think they would do a simple QA scan against a folder full of known good OS files before releasing to the wild and causing OS damage and systems not to boot. Very poor support from an otherwise good product. :(

     

    We are currently analyzing the situation and we are sorry for any inconvenience this may have caused.

     

    To answer a few of your questions/concerns:

    • you'd think they would do a simple QA scan against a folder full of known good OS files before releasing to the wild
      • We do have False Positive tests in regards to new databases being pushed out.  This had fallen through the cracks and we are currently analyzing exactly why this happened in the first place.
    • Zero response from Malwarebytes sales or support so far
      • ​We are doing our best to address each issue as they come up and if you still do not get a response, Marcin had responded in another thread that you can also respond directly to him as well.

    Please bear with us as we try to analyze and find the best solution that we can for anyone that this has inconvenienced.

  2. Hello There!

     

    I'd like to get more information if you don't mind.

     

    So there was an update to malwarebytes a few days ago. I'm now running 2.1.8.1057 and if I close the malwarebytes window so its just in my task bar the window pops up again about every 5 minutes and seizes control of my screen away from my current program.

     

     

    • What window pops up? (main UI or a notification of some sort?)
    • What does the message you can see say? (Something on the dashboard, something in a pop-up window?)
    • Could you also attach the logs daledoc (Hi Daledoc!) requested. :)
  3.  

    OK, thanks!

     

    Sorry for the redundant reporting.

     

    FURTHER UPDATE:

     

    I just noticed that "Show Notification after Successful Update" settings are NOT sticking after the on-top upgrade from 2.1.4 to 2.1.6.

    I just cold-booted my main desktop to find that the setting was once again disabled, even though I had set it to enabled a few days ago when I upgraded.

    So, in addition to reverting to "disabled", it appears that enabling it is not honored after a system reboot.

    It reverts to "disabled" again, at least in the GUI (I haven't run mbam-check to see what the log shows and I haven't seen a db update, yet, during this Windows user session).

     

    I guess I will either live without the notifications or I will try a clean reinstall of 2.1.6.

     

    Thanks,

     

    Hi daledoc,

     

    I don't think you need to go so far as to do an mbam-clean.  Try removing the existing scheduled update, and add a new one.

  4. Hi:

     

    I usually do a clean upgrade.

    I just now updated to 2.1.6 on top of 2.1.4 on "DT1" (see specs in my sig block).

    (SP was not enabled before the upgrade.)

     

    The following 2 settings were not retained/honored after the required reboot:

    • General -- "Close notifications after X seconds" -- it reverted back to the 3-second default (I had it set at 7 seconds before the upgrade)
    • Scheduler -- "Show notifications after successful update" reverted to disabled (I had it enabled before the upgrade)

    I'm not sure if this is expected behavior, and/or if these behaviors have been previously reported as bugs??

     

    Easy enough to fix.

     

    So this is largely "FYI".

     

    Cheers,

     

    Daledoc,

     

    Hey there!  We are aware of these issues and will do what we can to pull them into the next release.  Thanks for reporting :)

     

    The reason this still exists is because the default value of Close Notification used to be 7 seconds, but now the default value is 3 seconds.  If you install over the top and it sees 7 seconds, it will think "I need to set this from the old default value to the new default value".

  5. I have the SDKDatabaseLoadDefaults problem and have found recent threads where users with the problem have been asked to perform many lengthy and rigourous operations in order to find and solve the cause for the problem.... but I have not found a thread where the process they were required to go through ended in success. Maybe it was successful, maybe it wasn't. The thread doesn't tell us. Obviously, users with the problem don't want to go through a long and difficult process that doesn't fix the problem.

     

    Please let us know what process  has actually achieved SUCCESS in finding and fixing the cause of the SDKDatabaseLoadDefaults problem.

     

    If no solution for the problem has been found, but MWB is working to find it, it would be nice to know that as well.

     

    Thanks.

     

    Hi there gallilaw,

     

    We are currently researching this issue and trying to find a fix for it.  So far the popular workarounds have been posted by Maurice above me, but if you would like to help us try to track down why this is happening, I'm looking for:

    If you could get us those items, that would greatly help us :)

  6. Let's try a few more things.

     

    1. Please uninstall one of your AVs.  Having too much security software on the same machine can cause issues so it's usually recommended to only have one AV.
    2. Please try running a scan in safe mode to see if the same detections are found.
    3. Please try running a scan with MBAR and see if the same detections are found.
  7. SHA42,

     

    Thank you for your logs!

     

    Next, I'd like you to do the following:

     

    1. Download Process Monitor.
    2. Run procmon.exe.  It will open and start capturing events.
      post-119961-0-33882200-1412872175_thumb.
    3. Open MBAM and start a scan.
    4. Wait until you see the error prompt you reported "Scanner Failed with Error Code: 6".
    5. Go back to procmon, click File in the top left, and click on "Capture Events" to stop it from capturing events.
      post-119961-0-18726800-1412872458_thumb.
    6. When it is finished, click file in the top left, and click on "Save..."
    7. Keep note of the location the log is saved:
      post-119961-0-70689600-1412872729_thumb.
    8. Attach the saved procmon log back to us.  (If it's too big, we can provide you a link for uploading.  Just let us know  ;))
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.