Jump to content

Strenalis

Honorary Members
  • Posts

    100
  • Joined

  • Last visited

Posts posted by Strenalis

  1. Thanks for coming!

     

    We could use some additional information, if you don't mind.

    • Does this happen every time, or just the once?
    • Was self-protection enabled? This is disabled by default.
    • Was scan for rootkits enabled? This is disabled by default.
    • If you're able to replicate the crash, I'd like you to enable complete memory dumps and have it crash again. Instructions for generating full dumps here. If you can get a complete memory dump, please upload it to wetransfer and attach here.
    • Download and run dds.com or dds.scr. This tool gathers information about your system but does not make any alterations. This will gather two logs (DDS.txt and Attach.txt), save both of these and attach here.
    • Download and run mbam-check. This tool gathers information about your Malwarebytes Anti-Malware installation. Attach "CheckResults.txt" here as well.
    If you'd rather not attach these files to this thread, feel free to send me a private message with the attachments instead.

     

    Cheers, :)

  2. Hi again Weyoun,

     

    Nice finds. Fortunately I'm easily able to replicate the BSOD issue upon Webroot's detection and have forwarded information to the devs for them to get this fixed as soon as possible. As for the shutdown issue, I've not been able to replicate it, so I'd like to ask a few questions:

    1. Did the shutdown issue present itself after the BSOD issue was found on the same system? If so, it's possible that it's a side effect of the detection BSOD.
    2. If Webroot is temporarily uninstalled, does the shutdown issue still persist?
    3. If Beta 3 is uninstalled, does the shutdown issue still persist?

    Thanks in advance for your reply. :)

  3. I'm not exactly sure why the device is listed there. It should reside in the Non-Plug and Play Drivers section and also be a hidden device. Since we now have a new beta, I'd ask for you to completely uninstall 503 and then see if the device is still listed as disabled. Then install 504 and see if it's in the proper place and running normally.

     

    Thanks. :)

  4. Hi Weyoun,

     

    There's actually not a need for us to stop users from adding web exclusions for all antiviruses with web filtering components. We've done this with Kaspersky and avast! specifically because there's a compatibility issue with the way their respective web filtering components work. Most all antiviruses we've performed compatibility testing with do not exhibit the same problem, so there's no need to stop them from being added to Web Exclusions.

     

    Thanks for your concern. :)

  5. Hi Wide Glide,

     

    Sorry, but I'm actually a little confused as to what the issue is here. Can you please provide more information? MBAMWebAccessControl is the service used by the new and improved Malicious Website Protection in 2.0. In 1.75 and before, this was handled by MBAMService.

     

    Are you unable to start the service manually? Is it always disabled or only under certain scenarios?

  6. That's correct! As I stated originally, I am definitely seeing this buggy behavior, even without browser extensions. The reason I asked if you had any browser extensions was so that when the developers do fix the issue, we can test it against this Print Edit add-on in addition to the default method.

     

    Thanks MCFatTongue for reporting this, and thank you daledoc1 for stepping in. :)

  7. Hi MC and thanks for helping to test MBAM 2.0 Beta :)

     

    I am able to replicate the issue you've reported. When self-protection is enabled, I'm unable to have Firefox 27.0 generate a print preview. I'm attempting to do this by clicking on the Firefox button, then navigating to Print->Print Preview (see attached screenshot).

    post-111281-0-49853200-1392753441_thumb.

     

    After clicking this option, a small pop-up appears displaying that it is generating the preview, but after that goes away, no preview is displayed. Is this also what you are seeing?

     

    You also mention in your original post that you're unable to create a print preview using the right click menu. Are you using a browser extension to accomplish this? I don't see any options to generate a print preview from a right click context menu. Please let me know in your next reply.

     

    Once I have this information, I'll forward all of it to our developers so that the issue can be fixed in the near future.

     

    Thanks again!

  8. Unfortunately we do not offer such a feature at this time. This particular website (http://iptest.malwarebytes.org) is hosted by a specific IP address that we have defined as "malicious" in our database so that MBAM will block access to it if Malicious Website Protection is enabled. Note that this site is not actually malicious in any way and is only used for testing purposes.

     

    However, this webpage should be blocked and redirected to http://block.mbamupdates.com, but it appears that that is not the case on your system. Are you sure you don't have any other Web Exclusions setup? Adding your browsers as web exclusions (which is not recommended) would also cause iptest to be unblocked, as it is in your screenshot.

     

    I'm going to private message you with a batch file called log_gen.bat. It will analyze the Malwarebytes related Windows services on your system and generate a log file called "mbam-servicelog.txt" on your Desktop. Please attach this file either here in this forum topic or as a reply to the private message.

     

    (To attach a file to your post, click the "More Reply Options" button to open the full editor. From there, you'll be able to browse for files to attach.)

  9. Hi Brendtw,

     

    1. Does this freeze behavior happen consistently? If you run another scan and cancel it again, will it continue to freeze as you described?
    2. What operating system is this on?
    3. Do you have any other security software running on this system?

    Thanks in advance! The more information we have about the issue, the easier it will be for the development team to fix. :)

  10. Hi SpinDoctor, thanks for your feedback. See below for some short explanations as to why they were changed to what they are now:

     

    Quick Scan --> Threat Scan

    We want this to be the primary scan that users choose because in almost all cases in catches all malware that a "Full Scan" would in less time. It scans for threats in all of the locations that malware likes to hide on your system, and ignoring places that it doesn't.

     

    Flash Scan --> Hyper Scan

    This was renamed because with the word "flash", it can be implied that this scan will search flash memory devices such as flash drives/thumbsticks, which it does not. This type of scan primarily searches for malicious processes that are currently running in memory. Because it takes less time to perform than a Threat Scan, we decided that "Hyper Scan" would be appropriate.

     

    Full Scan --> Custom Scan

    A custom scan can be used to perform a full scan, that is, scanning every file and folder on every drive connected to the system. However, that's not its only function. The user can also simply select a few specific directories that s/he's concerned about instead of simply scanning everything. We've redefined this type of scan to account for this use.

     

    I hope that clears things up a little for you. Feel free to let me know if you have any additional concerns.

     

    Thanks! :)

  11. Thanks.

     

    1. After a system reboot, how long do you wait before deciding to turn Action Center on manually
    2. If you disable the option "Start Malwarebytes Anti-Malware with Windows" and reboot, does the Action Center icon appear normally?
    3. Are you sure you have Action Center configured to "Show icon and notifications"? You may have it set instead to "Only show notifications", which could also be responsible for the behavior you're seeing. See attached.


      post-111281-0-35588200-1391195529_thumb.
  12. Hi chappieray, and thanks for your interest.

     

    If you have MBAM Pro 1.75, then you already have a lifetime license. This means that you don't ever need to re-subscribe to keep your license active. In short, it's valid forever for one machine!

     

    With the release of 2.0, we'll be changing that so that a license is only valid for a year for three different machines, after which the user will have to re-subscribe. However, if you already have a lifetime license for 1.75 (which you do), that will continue to be valid as a lifetime license for 2.0, if you choose to upgrade.

     

    The beta for Malwarebytes Anti-Malware 2.0 uses a special temporary key that can be found on this thread.

     

    LICENSE KEY:

    id: MBAM2BETA

    key: 4XZHE-6ANRN-TKWCV-EV6HZ-G79PH

     

    You cannot use your 1.75 license key for the 2.0 beta.

  13. Wilpower and craigb,

     

    Thanks! It turns out this is an issue that was once present in our older test builds that has apparently resurfaced. Try the following to see if one or both fixes the issue of duplicate entries:

     

    1. Exit Malwarebytes Anti-Malware completely (right click the Malwarebytes icon in the system tray and select Exit), and then re-open the scanner.
    2. Try running a Threat Scan and see if the duplicates still remain afterwards.
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.