Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by Leo2

  1. Reinstalled. The MBAM tray icon has been reinstated and works. No malware found on the system with new scan. Downloaded ESET offline scanner and ran it too - no infections. As this app crash happened at Windows login, I expect there was something that Windows did not like about the tray icon start-up process. Maybe: Qt5Core.dll Thanks for your time exile360.
  2. File attached. mbst-grab-results.zip
  3. Source Malwarebytes Tray Application Summary Stopped working Date ‎12/‎15/‎19 9:07 AM Status Not reported Description Faulting Application Path: C:\Program Files\Malwarebytes\Anti-Malware\mbamtray.exe Problem signature Problem Event Name: APPCRASH Application Name: mbamtray.exe Application Version: Application Timestamp: 5df16440 Fault Module Name: Qt5Core.dll Fault Module Version: Fault Module Timestamp: 5dcd60b9 Exception Code: c0000005 Exception Offset: 001b487e OS Version: 6.1.7601. Locale ID: 4105 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789 Got the black screen of death (W7x86) after starting Windows logon. There was sporadic disk activity then none for about 5 mins, so I did a ctrl alt del. Windows logon screen came up with all icons and MBAM was running. I got a notification from Windows that the MBAM tray exec APP had crashed (see above). I closed the popup, but the MBAM tray icon was nuked. I can reinstate the tray icon by clearing the notification area cache but I think the MBAM tray icon exec may be corrupted. However, I expect another BLSOD if I do this. Hope the info provided helps with the diagnosis.
  4. Thank you exile360, I appreciate your response - that was fast! Now that you have pointed me in the right direction, I see that I should not use the default (recommended) setting on the Security Tab. I will set MBAM as my preference when I uninstall MSE to ensure that Windows gets the memo.
  5. I still have V3.8.3 Premium installed on my W7 systems. I checked out the blurb on MBAM V4 on this site and I see that W7 support will be in place for some time to come, however the only reference to the 'register change' is to W10/Windows Defender. W7 will be EOS in 2 months but I intend on keeping W7 operational thru to the end of 2023 without extended support. I also have MSE installed and it shows up in the W7 Action Centre under Security - Virus Protection, Spyware and unwanted software protection. That would have been an auto register by Windows for MSE at the time because I did not have MBAM then. It was added later. When W7 becomes EOS on Jan 14, 2020, so does MSE, so I will uninstall it. With this 'register change' in V4, will W7 recognize the AV and its protection status automatically?
  6. Support asked me to run the support tool again yesterday and send them the logs. They contacted me today and now all is in working order at both ends. The activate key is no longer grayed out - I entered my lifetime premium license and key just now and all looks as it should. I'm happy! So, a big thanks to the MBAM Support Team and the volunteers here on the forum who gave me some much appreciated guidance.
  7. Even though I closed that trial popup I got the premium trial anyway - 13 days left!!!!
  8. Tnx Maurice and Ron, I have just completed the support tool process. MBAM came up offering me a 14 day premium trial. Should I close that and try to activate my license or am I supposed to accept the trial?
  9. Tnx Ron. I got a response this morning - my email address needed updating. It is now showing my current email in the profile. I was told to reactivate my license key but the 'activate' key is grayed out.
  10. Hello Ron, tnx for replying. Here is the ticket (I used a different email to contact support than the one I have on file here at the forum). Malwarebytes Support Ticket 2657236.
  11. The is the first time this has happened to me with MBAM. I have had the PRO/Premium version since 2013 on this CPU. When I clicked on 'YES' for the upgrade to 3.8.3, the upgrade ignored my registered premium license and I now have the free version. I have read most of the latest threads here on the subject (and those similar), and from the expert responses, it appears that I should not try to re-activate the license myself as it may exasperate the situation further. I followed the advise and opened a support ticket and included a screenshot of the email regarding my payment and the key ID/license info (ticket 2657236). In the email I asked if I should try to re-activate my license myself. Support auto replied with a recommendation to a link to read about 'license exceeds max. device activations on a windows device' which I found confusing as I have not received that message and 'myaccount' indicates that my license and key ID is already registered. That was confusing. Also, my question was ignored, so I am left with assuming that support will be doing something at their end to remedy the situation. Am I understanding this correctly?
  • 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.