Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About malicide

  • Rank

Recent Profile Visitors

2,802 profile views
  1. Hello Enoch11, It looks like you are using an older driver for the 802.11n USB Wireless LAN Card. The version reported in the logs in, the most current version is You can find the most current version from the provider MediaTek, Inc. at their website http://www.mediatek.com/en/downloads1/downloads/ Please download and install the latest driver. If the issue persists please let me know.
  2. Hello KenW, are you certain that these scheduled scans have not occurred? Looking at the CheckResults.txt it seems that the lastriggered time for a scheduled threat scan was Tue, 10 Nov 2015 05:47:06.992395 -0700. If you are certain that no scheduled scan has triggered when it should have, please send me a copy of your scheduler.conf. This .conf file is located in C:\ProgramData\Malwarebytes\Malwarebytes Anti-Malware\Configuration
  3. If you are using a lifetime license for the host, a separate license would be needed for premium on the VM. If a subscription license is used then you could use it for both the host and VM, which would count as two different systems.
  4. Hello Ken, if this happens again could you please provide your configuration folder. It is located in C:\ProgramData\Malwarebytes\Malwarebytes Anti-Malware\Configuration by default.
  5. Hello Ken, if this issue occurs again could you please provide a procmon log? You can download procmon here http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx To create a log with the desired events: 1) Run procmon 2) Open MBAM, and attempt to enable protection. 3) Attempt to Update MBAM 4) Then save the promon log. You can save the procmon log by clicking on the highlighted button Or by using Ctrl + S in procmon Choose a convenient location to save the log and press OK.
  6. Hello Cmoore68, Have you tried to do a clean re-installation? I know you said you tried uninstalling, and then reinstallating. I wanted to make sure you tried using the mbam-clean tool and then installing once more. https://forums.malwarebytes.org/index.php?/topic/122284-mbam-clean-removal-process/
  7. Hello Sinster, which version of Malwarebytes Anti-Malware are you using?
  8. Thank you for reporting this Vorteth, I have successfully replicated this behavior and will bring it to the devs attention. TrueCrypt is definitely the culprit. I was only able to replicate the BSOD when I mounted the encrypted drive and ran a custom scan on it.
  9. Hello Vorteth, you mentioned that your drive is encrypted. Judging by the FRST log it looks like TrueCrypt, is this correct?
  10. Thank you for reporting this issue and for all the assistance Georgedn. I am not aware of any work around at this time. Our development team has been alerted to this issue, although it is uncertain if it is something on our side.
  11. Would you be comfortable uninstalling "My Lockbox", so we can narrow down that this is in fact causing the issue?
  12. I have seen compatibility issues between older versions of My Lockbox and MBAM Premium. The most current version of My Lockbox is You can verify and update the version you are currently using by opening My Lockbox Control Panel. On the bottom left of the My Lockbox control panel is an "advanced" button. Click on the, "advanced" button. The default tab displayed should be the about tab, which displays version number and the update button. Using the update button should download the most current My Lockbox installer. Note: When installing the older version I noticed PUP's(Potentially
  13. Could you please try to either: 1) Unlocking those files/folders with MBAM's realtime protection on and restarting your computer. or 2) Disabling MBAM's realtime protection and restarting your computer. Please let me know if this helps.
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.