Jump to content

throkr

Honorary Members
  • Content Count

    307
  • Joined

  • Last visited

About throkr

  • Rank
    True Member

Profile Information

  • Location
    BE

Recent Profile Visitors

7,574 profile views
  1. Updated from 3.8.1 and had to re-enable the context menu item. (Win10 1903 - Build 18362.207)
  2. Hi, Running fine here (up to now) on Win10 1903-Build 18362.175; manual install.
  3. 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.
  4. Hi, These 2 entries seem to be false positives; see attached scan log. Thank you ! MB Scan log.txt
  5. 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 ...
  6. 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.
  7. Hello @Jekko, Thank you for this info.
  8. Installed (through Settings) and working fine on Win10 1809 - Build 17763.292. Just a reminder to the devs: this problem still remains ( in French and Spanish language) ... Thanks !
  9. In addition to my previous post #4 , the context menu entry was still present (installation over previous CU 519).
  10. Working fine here on Win10 1809 - Build 17763.292.
  11. @dcollins , thanks for this super fast reply !
  12. Hi, Was on component package 1.0.495, updated (expecting to be on announced 1.0.505 version) but now I'm on component package ..... 1.0.508 ... Is this correct ? Thanks ! - Win10 1809 - Build 17763.168 -
  13. Alright, thank you for this info.
  14. 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 !
×
×
  • 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.