Jump to content

throkr

Honorary Members
 View Profile  See their activity

  • Posts

    407

  • Joined

  • Last visited

 Content Type 

Posts posted by throkr

    Various issues with MBAM 2.2.0.1024 on Win 10 Pro x64

    in Malwarebytes for Windows Support Forum

    Posted · Edited by throkr

    Hi daledoc1,

     

    Well, the clean install and the fact that I followed exactly the uninstall procedure seems to have done the trick : no systray icon issue anymore and self-protection remains enabled.

    If the scheduled scans issue is fixed in a not to far future, I'll be happy again using MBAM without any trouble ...    ;)

     

    BTW, a question concerning the updates of the program himself : I noticed that keeping self-protection enabled requires a reboot to finish the update whilst disabling it doesn't require a reboot; both ways work (for inside upgrades as well as for updates "over the top"), but is there a recommendation from Malwarebytes for this (I mean disabling / not self-protection before updating the program) ?

     

     

    Again, thanks for your time !    :)

    Various issues with MBAM 2.2.0.1024 on Win 10 Pro x64

    in Malwarebytes for Windows Support Forum

    Posted

    If I understand everything correctly, the proper clean reinstall seems to have resolved the important issues?

    (Yes, our own special removal tool (mbam-clean), rather than Revo, is the recommended method to cleanly uninstall.)

     

    The CheckResults.txt log now correctly shows PREMIUM, as does your scan log. :)

     

    Just curious: Why do you have what appears to be your entire documents folder and other data folders excluded from scanning?

    That pretty much defeats the purpose of using MBAM, as anything in those folders would NOT be scanned.

    If files in those folders were infected, they would not be detected.

     

    The "only" files/folders that **might** need to be excluded -- for some users -- would be their anti-virus and other security applications.

    (And even those are not generally needed, though some users prefer to set them.)

    It is not recommended to exclude one's data folders.

     

    Anyway, yes, we will keep this thread open. :)

     

    Please post back and let us know how it goes.

     

    Thanks,

     

    Hello,

     

    I suppose that this latest proper clean install (and, above all, the fact that, this time, I disabled self-protection before the uninstall and made a shutdown of my security suite) has resolved the issues, but I prefer to test the 2 points (systray icon and self-protection not remaining activated) during a few days to be sure. As mentioned earlier, I'm on Win 10 only since 09/29 and had the systray icon issue only 2 or 3 times up to now. (BTW : should it happen again, I'll firstly check if the 2 concerned MBAM services are launched before "reactivating" the icon). As for the self-protection issue, I only noticed that today because I had a look in the Scan log before attaching it to my first post. 

    If it wouldn't be for the scheduled scan issue, I don't open MBAM very often, which is quite normal if everything is running as it should be ...

     

    Concerning the exclusions : the "D" partition (which I created) only contains everything related to the programs (latest versions, tweaks, notes, tips) that are installed and related to the Windows installation.

    I always maintain its content up to date and therefore never include it when I format the drive (before a clean install of the OS) or if I have to load a previous disk image.

    Nothing comes directly from the net.From time to time, I make a manual scan on it, to be safe.

     

    All my "real" personal or sensitive data are saved on protected external HDDs, never on the desk/laptop drives ...

     

    I'll post back next Monday to let you know how it goes with the systray icon and the self-protection. And let's hope that the scheduler issue will be solved soon in a future release ...

     

     

    Thank you a lot for your time !   :)

    Various issues with MBAM 2.2.0.1024 on Win 10 Pro x64

    in Malwarebytes for Windows Support Forum

    Posted

    Hi,

     

    Thank you for the reply.

     

    "I could be wrong, but I thought users upgrading to Win10 must first perform the "upgrade" from 7/8/8.1, and THEN (if they wish) perform a clean reinstall of 10?"

     

    There exists a method allowing to make a clean installation without performing the upgrade first. But at the moment I switched to Win 10 (09/29/2015), there was no guarantee (AFAIK, there still isn't) that the activation through this workaround would be maintained even after 07/29/2016 (end of the free upgrade period); that's why I did it on the regular way : upgrade first through Windows Update (to have my actual license key stored on Microsoft's servers) and immediately afterwoods a clean installation of Windows 10 (with a DVD created through the Media Creation Tool proposed on the MS site).

    Anyway, this all will be kind of "history" with the upcoming big November Patch (through Windows Update, now announced for 11/12 - sorry, in German) as after that the users will have the possibility to clean install Win 10 directly with their Win 7/8/8.1 Key (no need to upgrade !).

     

     

    "That issue has been reported to the devs/QA team"

     

    That's excellent news; until a fix is released, I'll continue to modify it manually after each weekly scan ...

     

     

    "The license problem, though, is not normal or expected behavior - mbam-check should log Premium if you have a properly installed and activated MBAM Premium license" 

     

    Solved (see new attached CheckResults) by following your suggestion and instructions for a new clean install.

     

     

    "And we don't know exactly what procedure you followed with the Win10 install, or whether you tried a clean reinstall of MBAM after installing Win10."

     

    In fact, when I installed MBAM the first time, my ID and Key were not accepted (first time since I bought this lifetime license in January 2009). I contacted immediately your support (reading on the forum that a lot of other users had the same issue) and got a reply on 10/07/2015. That's the date where I could eventually activate MBAM again. (Just for my own info : where did you see in the logs that it was not activated until today (in fact now yesterday, 11/03/2015 ? I couldn't find it. Thanks ). At the same date, I decided to make a (new) clean installation of MBAM, using Revo Uninstaller Pro which worked perfectly (strictly no left overs : I checked my "C" and the registry). However, 2 points I didn't do correctly is to disable the program self-protection before uninstalling and to temporarily shutdown my security suite (I only suspended it).    :blush:

     

    Today, I uninstalled and installed MBAM again but this time following to the point your instructions.    :)

    As already mentioned, CheckResults shows now the correct type of license (Premium); I can't already have an opinion on the issue with the systray icon and the self-protection not remaining activated but it could also have been solved now ... Attached you'll find the new Diagnostic logs as well as the CheckResults and a fresh Scan log.

     

     

    My suggestion, if this is feasible, would be to leave this topic open until the end of this week so I can let you know here how it goes by next monday (11/09) at the latest.

     

    Thank you !

     

     

     

    CheckResults.txt

    FRST.txt

    Addition.txt

    Scan log.txt

    Various issues with MBAM 2.2.0.1024 on Win 10 Pro x64

    in Malwarebytes for Windows Support Forum

    Posted

    Hello,

     

    I'm currently running latest version 2.2.0.1024 (Premium) on Win10 Pro x64. I made a clean install of Win10 (meaning not through the upgrade proposed by Windows Update), thus also of MBAM.

    Be advised that I never encountered these issues on Win 8.1.1.

     

    Hereby the issues :

    • sometimes it happens that, after a reboot, MBAM has not started correctly (systray icon not present at start up). A solution (in my case) is to execute "Malwarebytes Anti-Malware Notifications" from the Start Menu and the icon appears after the UAC prompt. Be advised that this happens only after reboots.
    • self-protection does not stay activated all the time (in Advanced Settings, I checked the option "Enable self-protection module" when I installed MBAM; from time to time I notice that the box is suddenly unchecked)
    • the date of the next scheduled scan is not following the configured settings; this issue appears after each scheduled scan. As it can be seen in the attached screenshots, I have a weekly scheduled scan; after the task has been executed, the date for the next scheduled scan is set for + 2 weeks instead of just 1 week. As mentioned before, this is the case every week (I rectify it manually to 1 week)

    I attached the diagnostic logs, as per your FAQ's request. BTW, I noticed that some infos in the CheckResults are not correct (OS and License).

     

    Thank you for your assistance !   :)

     

     

    Edit : added latest Scan log.

    post-43330-0-22217700-1446516854_thumb.j

    post-43330-0-12414600-1446516870_thumb.j

    CheckResults.txt

    FRST.txt

    Addition.txt

    Scan log.txt

    Malwarebytes Anti-Malware 2.1.x Release Candidate 2

    in Malwarebytes Anti-Malware 2.1 Beta Test

    Posted

     

    Agree there should be some license infomaton as to when the current license expires preferably on the front GUI where it is easily visible but not obnoxiously so.  If it is a lifetime license it can say "Lifetime Premium License."   If it is not a lifetime license it can say something like "Preimum License XXX days left"

     

    +1

     

    +2

     

    +3

     

    Hoping the list will grow even more .....    :P 

    Malwarebytes Anti-Malware 2.1.x Release Candidate 2

    in Malwarebytes Anti-Malware 2.1 Beta Test

    Posted

    Update to v 2.1.3.1017 without any problem (internal updater); works & looks great !   :)

     

     

    @ bdubrow

     

     

    • @throkr - Right now we have self-protection disabled by default, but we do want to change that to be enabled by default. Since we intentionally didn't want to pull in too many functional or behavioral changes with this release due to the fact our users would also be dealing with a major change in look and feel, we haven't changed that default just yet.  

    And then the self-protection delay is just a one-time delay as the service is enabled for the first time.  You shouldn't see any extra delay from that if you have both of those options enabled.

     

    Thank you for these clarifications.

     

     

    I have also a suggestion : it would be nice to have the option of maximizing the protection logs window (as it is possible for the scan logs)

     

    I suppose that this option is not planned for now ... ?

    Malwarebytes Anti-Malware 2.1.x Release Candidate 2

    in Malwarebytes Anti-Malware 2.1 Beta Test

    Posted · Edited by throkr

    Running v 2.1.2.1016 (french version) since yesterday evening without problems up to now ...   (OK, still some layout problems under "Automated Scheduling" as reported by other members in this topic, but it is already much better than in the betas).

     

    I have 2 questions concerning the "Advanced Settings" of version 2 in general :

    • if  the self-protection module is enabled, clicking on "Recommended Settings" unticks this setting. Should the user understand that it is "recommended" (IOW that the first choice is) to not enable the self protection ?
    • if self-protection AND delay protection are both enabled, does this result in a sort of addition of the delays (as each enabled setting introduces a delay) ?

     

    Thank you !   :)  

     

    Edit : typo & screenshot.

    post-43330-0-69695200-1426159440_thumb.j

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.