Jump to content

throkr

Honorary Members
  • Posts

    407
  • Joined

  • Last visited

Everything posted by throkr

  1. Hi, I think that this is not related to MB 3.0.5 : I noticed this too since Piriform implemented officially Microsoft Edge as a complete section in their software (CCleaner in this case). I'm really very happy using this latest release of Malwarebytes and didn't have any functional issues. A few things have to be improved as already mentioned here, here, and in this post. Let's see what the next releases bring up ... - Win 10 1607 (Build 14393.576) Pro x64 -
  2. I'm now waiting (just like many other users, I guess) that the buttons "delete" and "edit" become active (see my previous post here). Hopefully with the next release .....
  3. Hi Erix, Thank you for these explanations; I will observe the evolutions in the next releases.
  4. Hi, Latest version 3.0.5 includes already an uninstaller which works just ..... perfectly : I tested it and there was strictly nothing left (just an empty key "first run" .... so let's forget about it). - Win 10 1607 (Build 14393.576) Pro x64 - Hope this helps,
  5. Hi, In addition to my previous post, I have another question concerning the option to "check for updates before scanning" under the scheduled scans settings. Well, in fact this "option" isn't one as it will always stay checked (even if the user unchecks it, it'll revert to checked after closing this window). Of course I agree with the idea to always scan with the latest possible updates, but is this normal ? (..... just curious .....) Again, thanks for your time !
  6. For info, now that KeePass is in the list (see my post #12 above), I have no problem to toggle it off or on in Malwarebytes; I simply noticed that setting off is immediate whilst setting on again lasts a few seconds more (probably because KP is running in the background).
  7. Hi, Following the scan progress, Hyper Scan includes memory, startup, file system, heuristic analysis and potential threats but the scan summary mentions "deactivated" for startup, file system and heuristic analysis (see attachment). Did I miss something here ? If under Protection Settings > Potential Threats, I set e.g PUP to "warn user" (meaning : "You will be alerted to the detection, and you may choose to ignore it, create an exclusion, or treat it as malware."), this setting is taken over by all 3 scan types. But I noticed that in this case the scan summary mentions "deactivated" for PUP. If so, how could MB possibly detect them and warn me as this seems to correspond more to the protection setting "Ignore detections: Malwarebytes will not act on detection, nor will you be alerted." ? MalwareBytes version 3.0.5.1299 - Win10 1607 (Build 14393.576) Pro x64 Thanks for your time ! Scan summary Hyper Scan.txt
  8. Hi, On this official page you'll find a direct link to download latest version 2.2.1.1043 (point 1). Hope this helps ...
  9. Hi, No problem here with LO 5.2.4 on Win 10 Pro 1607 (latest Build 14393.576) x64; updated today to this latest LO Evolution version with no issues up to now ...
  10. Hello, Just for info, I'm on Win 10 1607 (latest Build 14393.576) Pro x64 and couldn't add KeePass at first because it was running; I exited the program and no problem anymore (did it this same way for a few other still running programs). Maybe this helps ...
  11. Thanks for these infos and let's wait for a future correction of this quite annoying bug.
  12. I noticed the same problem; only solution for now is to turn off the ransomware protection before making an image with Macrium Reflect and enable it again afterwards ... I'm using MB version 3.0.5.1299 and latest Macrium Reflect Home Edition version 6.3.1665 (I disabled system restore in Windows as I don't use it). This issue is also largely discussed on Wilders Security Forums here If not done yet, this issue should be passed to the developers. Thanks for your time !
  13. Thanks for your reply. Concerning the issue after safe mode (without networking) : I'm back to version 3.0.5 now but had to install again this version over version 3.0 ... Very strange, this never happened with previous versions. Additional info I didn't mention before : when I upgraded the first time to version 3.0.5, I just installed it on top of latest version 2.x.
  14. This is a complement to my previous message as I noticed a very strange "bug" : after I came out from safe mode (without networking), MB's systray and main UI were asking for an update as they had reverted to version 3.0 (all settings and updates were lost, only the activation key was saved), however version 3.0.5.1299 was still installed ... Please note that this strange behavior does not happen coming out of safe mode with networking ...
  15. First of all, I would like to thank the developers for this very nice new version 3 ! I'm running latest version on Win 10 Pro 1607 (latest Build 14393.576) x64 and like it very much ... One question concerns the protected applications list : the buttons "delete" and "edit" always remain greyed out (I'm logged in an admin account). The other question concerns the exclusions list : where is the correspondent file located (with version 2, a file "exclusions.dat" could be found in C:\ProgramData)? Thanks for your time !
  16. Interesting info; thank you, Firefox. One practical question : is there a possibility to modify the title of this topic (adding "solved"); could certainly be interesting for other forum members / readers ... Thanks.
  17. Hi, I mean updating through the program himself when a new version is proposed (internal updater) vs updating "over the top" of the previous version using an *.exe file downloaded from the site.
  18. 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 !
  19. 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 !
  20. 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). 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
  21. 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. CheckResults.txt FRST.txt Addition.txt Scan log.txt
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.