Jump to content

throkr

Honorary Members
  • Posts

    407
  • Joined

  • Last visited

Everything posted by throkr

  1. Hi, Thanks for your fast reply. As I have set this policy myself, I'll add it to my exclusions. I just was surprised by this detection because I have this setting since quite a few years and it was never detected before.
  2. Hi, These 2 entries seem to be false positives; see attached scan log. Thank you ! MB Scan log.txt
  3. Hi, Good news: I just installed next DriverMax version 10.16 with MB 3.7.1.2839 - 1.0538 without any problem (As previously, I have set DriverMax under the protected applications). So, it seems that this issue is now resolved ...
  4. No problem here on Win10 1809 - Build 17763.292. Clicking on the bell icon (no notification) brings up a little window telling that there are no notifications; another click closes this window and reverts back to the GUI.
  5. In addition to my previous post #4 , the context menu entry was still present (installation over previous CU 519).
  6. Working fine here on Win10 1809 - Build 17763.292.
  7. Latest version 10.15 installs as it should now (I mentioned previous version 10.14 for info only, as I'm always using latest version(s)). Now I have an additional question: will this issue show up for every future new version of DriverMax (this would be quite annoying and unusual ...) ? Thanks for your time !
  8. Hi, Just a reminder : this layout problem is still present in latest version 3.6.1 (I suppose it's still on the to do list) ... Thanks !
  9. Done. FYI : this issue already happened with previous version DriverMax 10.14.exe and MB 3.5.1. DriverMax.zip
  10. Hi, DriverMax.exe is suddenly detected as malware (see attached log) ... Thank you. Malware.txt
  11. Just as info from another user (thought it might be useful): I have a lifetime license for both of these products, run them both in real time since a very long time now and never had an issue. Hope this helps. ?
  12. Hi, I just noticed a slight layout problem in the new dashboard (see screenshot). Additional question: the program who monitors the available updates of my installed software (SUMo) advises me that there is a build 2527; how / where can I get this latest version because through settings it tells me that there is no newer version after build 2522 ? Thanks !
  13. Update to my 1st post here : I'm now running MB 3.4.5 on "Spring Creators Update" (Win10 1803 - Build 17133.1 x64) since a few hours and had no issues so far ...
  14. Hi, Updated from 3.4.4 through "Settings"; no issue(s) so far ... - Win10 1709 Build 16299.334 - x64) -
  15. Hi @exile360, Thank you for replying; I had no doubt about the "priority" of this suggestion but to have it "on the list" is already a good thing. All the best to you ..... ;-)
  16. Hi, I suggest adding the following settings : 1. save /not clean scan logs (no detections) 2. don't keep logs older than XX days (XX = 30 by default and may be changed by overwriting) Thanks for reading !
  17. @dcollins Here are my test results : strictly no problem ! I even ran the MBAE Test. - see screenshot - (MBAE 1.11.1.40 / LO 5.4.3 x64 / Win10 1709 Build 16299.64) By the way, I also have good news for your team concerning another still pending exploit issue. As you were also involved in this discussion, please have a quick look at this topic :
  18. @dcollins No problem. I'll test that later on and report back here ...
  19. Thanks for your advice, I'll keep the default setting. As for MBAE standalone, I can test it and report here. I never used this software, so I suppose that I will have to remove MB first, correct ?
  20. Sorry to hear that you're still having problems ... The mentioned failing DLL (located in the System32, Win SxS and SysWOW64 folders) seems to be directly related to the OS. Why don't you try my (temporary) approved workaround described in post #9 ? If this one also works for you, you would have LO at least protected until the staff can help you out. Additionally, should it work (or not), it would give them even more information about your issue (remember to attach the requested logs). The more indications they have, the better they can help ... At the moment, I'm waiting for their advice ( see post #10).
  21. Hallo Kupke, Bevor eine "offizielle" Antwort erscheint, denke ich dass Sie für solche Fälle vermutlich ein Ticket bei dem offiziellen Support öffnen müssen : https://support.malwarebytes.com Gruß, throkr
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.