Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by LiquidTension

  1. Hi @RCasteel, Thanks for reporting this issue. I've sent you a private message with follow-up instructions to troubleshoot this issue. The problem is with the wintun driver that Malwarebytes Privacy uses to establish the VPN tunnel.
  2. Hi @CristianM, After you've clean reinstalled, please let us know if you continue to experience the BSOD. An Avast driver is implicated in one of the minidumps you provided. Please do consider temporarily uninstalling Avast and check if the BSOD persists or not. This is likely a conflict between Web Protection in Malwarebytes and Avast.
  3. Hi TWBUser, With Malwarebytes running, are you able to interact at all with the Malwarebytes user interface? If so, could you check if this issue is limited to a specific Real-Time Protection component by disabling them all and then re-enabling one-by-one until the culprit is identified?
  4. Hi Forrial, Only certain members of the forum have access to download the file. If you're still concerned, feel free to private message the file to me. Once the file is provided, we can take a closer look at your issue.
  5. Hi @PBealtway, Thanks for the report. Could you zip up and provide us with C:\Windows\MEMORY.dmp so we can investigate this further. Please run the Malwarebytes Support Tool as well: https://support.malwarebytes.com/hc/en-us/articles/360039023453-Upload-Malwarebytes-Support-Tool-logs-offline Thank you!
  6. They may help explain what caused your issue. Note that we've addressed several issues identified in the update process, so it's possible what you encountered has already been addressed or is due to be.
  7. Hi @throkr, Thanks for the update. This is expected as the report was generated before you disabled Ransomware Protection. Could you elaborate on this? What do you mean by position "OFF"? Where did you see the drive letters change? Was this a permanent change? ----- Some additional information would be useful. Delete C:\FRST. Enable debug logging in MB4 (Settings -> Event log data -> Enable "Collect enhanced...". Run Process Monitor: https://docs.microsoft.com/en-us/sysinternals/downloads/procmon With Ransomware Protection enabled in MB4, run MBST. Wait for the hang to occur. Once the hang has occurred, stop the Process Monitor capture (File -> Capture Events). Save the Process Monitor log and zip it up. Zip up the following folders: C:\ProgramData\Malwarebytes\MBAMService\Logs C:\ProgramData\Malwarebytes\MBAMService\ARW Attach the zipped up Process Monitor log and folders. Also, whilst still in the issue state (so before you disable Ransomware Protection), please open Task Manager and look for the FRST process. Expand it if there are child processes running and take a screenshot of what you see.
  8. Hello, We weren't able to reproduce the same detection you were experiencing. However, we have made a couple of changes that we believe should prevent any future occurrences. If you'd like to check for yourself: Install the latest beta version of Malwarebytes: https://forums.malwarebytes.com/topic/257042-malwarebytes-41-beta/?tab=comments#comment-1384494 Remove the exclusion you added earlier. Check if the detection occurs again.
  9. Hi all, Thank you for the reports. Please do carry out the instructions in the post above. In addition, please let us know if you're able to identify if a particular Real-Time Protection component is responsible. You can do this by disabling each of the components using the buttons found on the Dashboard and then re-enabling them one-by-one.
  10. Hi @Skier, Thank you for the report. Whilst Malwarebytes is currently uninstalled, logs will still help with identifying potential environmental factors that may be involved. We haven't found this issue is exhibited with all machines running Windows 10 v2004. Please consider carrying out the instructions above to gather logs with the Malwarebytes Support Tool. Thank you!
  11. @SPDIF, @sefton22 Please run the Malwarebytes Support Tool and gather logs so we can take a closer look: https://support.malwarebytes.com/hc/en-us/articles/360039023453-Upload-Malwarebytes-Support-Tool-logs-manually
  12. Thanks @throkr. The revised beta version (1.0.931) we released now may have a fix for this issue. Please do the following to confirm: Delete the C:\FRST folder. Rerun MBST. Verify there are no issues when Ransomware Protection is enabled.
  13. Thank you for the feedback. We have a defect filed for the erroneous creation of that directory.
  14. Thank you for the information. We're looking further into this. It appears to be related to the registry backup functionality in FRST. If you run MBST again with Ransomware Protection, do you still encounter an issue? Now that FRST was able to complete successfully and perform the registry backup, there's a good chance it will run successfully now.
  15. Hi all, Please try out the latest Malwarebytes beta version and let us know if this corrects your issue: https://forums.malwarebytes.com/topic/257042-malwarebytes-41-beta/?do=findComment&comment=1383903
  16. Thank you for the feedback! Please let us know how you get on in the upcoming days.
  17. Thank you for the feedback. When you initially encountered an issue, did you find that clicking "Install" to an update prompt had no effect and did nothing? If so, we have a defect filed for this. Could you clarify what you mean by "it"? Was this a manually initiated reinstallation? The logs mentioned in the post above will help provide clarity.
  18. Thank you for the feedback. The two part process to this is expected (Component package update first followed by the Service package/Malwarebytes version update). We have defects filed for the other issues.
  19. Thank you for the feedback! We have a defect filed for the issue with Self-Protection.
  20. Hi @frozen, Thank you for the feedback. The standalone Anti-Ransomware is currently ahead of the Ransomware Protection in Malwarebytes. We will be updating Ransomware Protection in an upcoming update, so you'll be able to benefit from the fix for this in Malwarebytes once that update is released. In the meantime, you can either stick with the standalone Anti-Ransomware or go back to Malwarebytes and temporarily disable Ransomware Protection.
  21. Hello, Could you try the latest beta version of Malwarebytes please and let us know if the issue persist: https://forums.malwarebytes.com/topic/257042-malwarebytes-41-beta/?do=findComment&comment=1382782 If it does, please provide us with the full memory dump generated from the crash (C:\Windows\MEMORY.dmp).
  22. Hello, Could you provide us with C:\Windows\MEMORY.DMP please so we can investigate further? Do you have any details on what was taking place at the time of the crash? What programs were running?
  23. Hello, Thank you for the report. If you're still experiencing an issue with blue screens when running the latest beta version (Component package 1.0.924), please provide us with the full memory dump generated from the blue screen (C:\Windows\MEMORY.dmp) so we can investigate further. Please run the Malwarebytes Support Tool as well: https://support.malwarebytes.com/hc/en-us/articles/360039023453-Upload-Malwarebytes-Support-Tool-logs-offline
  24. Thank you for the feedback. We have a defect filed to get this corrected.
  25. Hi @cchilderhose, We believe this latest beta update will address some of the current Web Protection issues, including some related to performance and third-party compatibility. Please let us know how you get on.
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.