Jump to content

LiquidTension

Staff
  • Content Count

    3,723
  • Joined

  • Last visited

2 Followers

About LiquidTension

Recent Profile Visitors

7,440 profile views
  1. Hello, Thank you for the report. Please start by carrying out the instructions linked below and attach the generated files. https://forums.malwarebytes.com/topic/191468-readme-first-posts-here-need-to-include-mbae-logs/
  2. That's certainly understandable. I will provide an update in this forum topic once we release the update containing the fix.
  3. Thank you to everyone who has tried the beta and provided feedback. It's greatly appreciated. A forum announcement will be made once the latest release candidate is released to public.
  4. Hi @kingzee, Thank you for the report. We have a defect currently for this issue and are still in the process of investigating it. If you would prefer not to post the logs in public, you are welcome to send me a private message with the logs attached. We have found the issue is not reliably reproducible, so environmental information will assist our efforts here. VS Code version? Are you using stable or insiders? Installed VS Code extensions? OS information? Malwarebytes component version (found in Settings -> About)? Are you running VS Code in a virtual machine or live machine?
  5. Thank you for the update. If you encounter any further issues, please let us know. We have a defect filed and hope to have a fix available in the future.
  6. Hi Chris, Thank you for your patience. The permanent fix (mentioned in the quotation included in your first post) is not yet available in Malwarebytes for Windows. We have been working on a fix and hope to make it available in an upcoming component update. In the meantime, we recommend sticking with one of the two known workarounds for the issue.
  7. The latest online installer for Malwarebytes version 4 has now been updated to block installation on ARM systems.
  8. The issue with Malwarebytes Support Tool is caused by FileASSASSIN being installed. If you uninstall this, you will find the Support Tool completes log gathering successfully. ---------- To confirm, when you uninstalled KIS 2020, did you reboot the machine at least once? And after the reboot, did you confirm the issue with Snagit persists? Or did you only check if the issue with the Support Tool persists? Note that the issue with the Support Tool is completely unrelated to the other two issues you've mentioned. We've not been able to reproduce an issue with Snagit and the latest beta update (see below). Could you provide the exact steps you're taking that result in the issue occurring? ---------- Regarding the hang that occurs with file compression, are these the steps you're taking? Open Malwarebytes and launch a Custom Scan. Right-click a folder containing multiple files -> Send to -> Compressed (Zipped) folder. Windows file compression hangs. How are you configuring your Custom Scan? Is rootkit scanning enabled? Where is the folder you're attempting to compress located? What type of files are you attempting to compress? What's the total size of the folder? As you're using the native/built-in Windows file compression utility, it is interesting that adding an exclusion for the WinRAR installation folder mitigates the issue.
  9. Hi @helios77, That's great! Thank you for providing feedback.
  10. Hello, Please gather logs with the Malwarebytes Support Tool and attach the generated file: https://support.malwarebytes.com/docs/DOC-2396 Are you able to identify if a Real-Time Protection component in Malwarebytes is responsible? If you disable all 4 components, does the issue disappear? What happens when you re-enable them one-by-one?
  11. Hello, Could you confirm if the issues still persist with Kaspersky fully uninstalled and the machine restarted?
  12. Please try the latest beta version available and let us know if this addresses the issue: https://forums.malwarebytes.com/topic/252170-a-new-malwarebytes-4-beta-is-now-available/?do=findComment&comment=1357781
  13. Hi @saxophone21, We believe the cause of this issue is the same underlying cause of another Web Protection issue we're currently dealing with. We hope to have a fix available shortly. No additional troubleshooting data needed at this time.
  14. The Support Tool uses a scheduled task to relaunch when a reboot is required to complete the uninstall process. Once relaunched after the reboot, the scheduled task is removed. It's possible removal of failed. If the issue still persists after the above suggestions, the log generated by the instructions in post #2 will help.
  15. Thanks for the feedback. Yes, a fix has been released for both.
×
×
  • 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.