Jump to content

LiquidTension

Honorary Members
  • Posts

    4,182
  • Joined

  • Last visited

Everything posted by LiquidTension

  1. Hi all, Thanks for the submitted troubleshooting data. We are currently testing a fix for this issue and hope to make it available shortly. In the meantime, refer to this post for available workarounds.
  2. Hi all, Thanks for the submitted troubleshooting data. We are currently testing a fix for this issue and hope to make it available shortly. In the meantime, refer to post #15 for available workarounds.
  3. Thank you everyone for the feedback. Investigation into this issue is still on-going. We hope to have a fix available in a future update.
  4. Thanks for the update and information. Please continue to monitor and let us know if the issue returns. We will try some additional tests and see if the issue is reproducible on our side.
  5. Hi @ITC23, Could you try adding folder exclusions for the following and check if this has any impact: C:\Program Files (x86)\Common Files\Apple C:\Program Files\Common Files\Apple
  6. Hi @toomm1, Thank you for reporting the issue. This is being caused by the Ransomware Protection component. To assist our investigation, could you provide us with some additional troubleshooting data please. Open Malwarebytes and click Settings. Turn the Event Log Data setting on. Capture a Process Monitor log as the issue is reproduced. Please download run_procmon.bat using the link below. → https://malwarebytes.box.com/s/he92cwwd71sa0w7waiub8wx69ymb5d4i Open your Downloads folder. Double-click run_procmon.bat. Click Yes if prompted by User Account Control. Note: If you are prompted by Windows SmartScreen, click More info followed by Run anyway. A blue window will appear. When prompted to carry out the tasks, please reproduce the issue with iTunes Sync in full. Once done, click inside the Command Prompt window and press Y on your keyboard followed by Enter. Upon completion, a file named procmon-log.zip will be saved to your Desktop. Please attach the file in your next reply. Note: If the file is too large, you will be provided instructions to upload the file to a file hosting website (wetransfer.com). Gather logs with the Malwarebytes Support Tool and attach mbst-grab-results.zip to your post: https://support.malwarebytes.com/docs/DOC-2396
  7. Hi @UweKraatz, Thanks for the report. We've tried reproducing this issue but have not encountered any issues. Please could you provide some additional information: Is this a consistent occurrence for you when Ransomware Protection is enabled? Have you rebooted and checked if the issue still occurs? Is this the structure for the files you're attempting to rename? %UserProfile%\Desktop\{parent folder}\{files} What file formats are affected? Does this occur with non-image files? Do you see the same issue when attempting to rename files in other locations? How long have the files you're attempting to rename been present on the computer? E.g. Are you transferring the files from an external device and then immediately attempting to rename them? In addition, please carry out the "technical issue" instructions in post #2 and attach the generated file.
  8. Hi @srisar, I wasn't able to reproduce this issue. With Web Protection enabled, I saw no impact on AdGuard's blocking functionality. Could you provide the logs referenced in post #2 please? Also, have you configured AdGuard in a non-default manner?
  9. Hi @MWUser, Thank you, but it looks like you've attached the wrong file. Could you try attaching mbst-grab-results.zip once more or rerun log gathering using the following instructions: https://support.malwarebytes.com/docs/DOC-2396
  10. Hi @Jim48, Thank you for the report. We apologise for the issue you're experiencing. To assist our efforts in addressing the issue, please do the following: Open Malwarebytes, click Settings and enable the Event Log Data setting. Reproduce the issue you're experiencing. Gather logs with the Malwarebytes Support Tool and attach the generated file to a post: https://support.malwarebytes.com/docs/DOC-2396
  11. Hi @Homer712, Thank you for the information. This issue is reproducible and we have a defect filed. We'll be investigating the issue further and hope to have a fix available as soon as possible. In the meantime, you should find that adding a file exclusion for C:\Windows\System32\wevutil.exe mitigates the issue entirely. Please refer to, Add to the Allow List in Malwarebytes for Windows v4.
  12. Hi @Yuuki, Please start by rebooting the machine and getting the latest version of Malwarebytes installed. Ensure you use the "Restart" option; not "Shut down". After the reboot, you can install the latest version of Malwarebytes by opening the application -> clicking Settings -> clicking Check for updates. Please check if the issue still persists after completing the above steps. If it does, please confirm if the behaviour is still the same when AVG is uninstalled and the machine rebooted once more.
  13. The 3.5 version is only intended for Windows XP and Vista machines. For Windows 7 or higher, you are best served installing version 3.8.1 (download link) if you wish to revert from version 4.0. Both version 3.8.1 and 3.5 will continue to receive database updates for the foreseeable future. @OldMainframeGuy Thank you for providing data on the issue. We hope to have a fix available shortly. In the meantime, you may wish to keep Web Protection disabled or revert to an earlier version. See here.
  14. You could either disable Web Protection in your current version, revert to an earlier Malwarebytes version 4 component package version (download URL) or revert to Malwarebytes version 3.x (download URL). If you disable Web Protection, you may want to also prevent the real-time protection disabled notifications from showing (until you re-enable Web Protection). The option can be found in Settings -> Notifications. If you revert to a previous Malwarebytes version, you will need to disable the "Application updates" settings found in Settings -> General. Once we release a fix, you will need to update to the fixed version manually.
  15. This is expected on Windows 10 and part of the extra protection that the Malwarebytes Service receives. In addition to the notification area icon option, there is also an option within the Malwarebytes user interface settings to prevent the application from starting with Windows. It can be found under Settings -> Security -> Windows Startup. As Porthos mentioned, if you have Windows Fast Startup enabled, you must use the "Quit Malwarebytes" option before shutting down to ensure the service is not running when the machine is next powered on. This is not required if you use the Windows "Restart" option instead of "Shut down" or if you disable Fast Startup.
  16. The "Allow an application to connect to the Internet" only corresponds to the Web Protection module. It doesn't hurt to try, but will unlikely have any impact. @ITC23 To assist our investigation with the iTunes Sync issue, could you provide us with some additional troubleshooting data please. Open Malwarebytes and click Settings. Turn the Event Log Data setting on. Capture a Process Monitor log as the issue is reproduced. Please download run_procmon.bat using the link below. → https://malwarebytes.box.com/s/he92cwwd71sa0w7waiub8wx69ymb5d4i Open your Downloads folder. Double-click run_procmon.bat. Click Yes if prompted by User Account Control. Note: If you are prompted by Windows SmartScreen, click More info followed by Run anyway. A blue window will appear. When prompted to carry out the tasks, please reproduce the issue with iTunes Sync in full. Once done, click inside the Command Prompt window and press Y on your keyboard followed by Enter. Upon completion, a file named procmon-log.zip will be saved to your Desktop. Please attach the file in your next reply. Note: If the file is too large, you will be provided instructions to upload the file to a file hosting website (wetransfer.com). Gather logs with the Malwarebytes Support Tool and attach mbst-grab-results.zip to your post: https://support.malwarebytes.com/docs/DOC-2396
  17. Hi @scifiguy, Thanks for the report. Does the mean you've verified the issue still occurs when Avast is not installed? Your attached logs show that Avast is still installed. Please disable the Real-Time Protection modules one at a time using the Malwarebytes user interface and check if there is any impact on the issue. Please let us know if you're able to identify if a particular Real-Time Protection module is responsible.
  18. Thanks for the data, @PeterJ. In an upcoming update, we are planning on adding additional options (user interface and command line-based) to disable hardware acceleration, that will provide a more convenient means of resolving issues like this.
  19. @TheGift73 Thank you for providing the dump file. This is consistent with the other Web Protection blue screens we've been seeing. A fix is currently being worked on and we hope to release it shortly. In the meantime, Web Protection will need to remain disabled.
  20. Hi @pquart, Thank you for providing the dump file. This is consistent with the other Web Protection blue screens we've been seeing. A fix is currently being worked on and we hope to release it shortly.
  21. Hi @boombastik, Thank you for the logs. What are the specific steps you're taking that results in this issue? If you use Restart option, do you encounter a similar issue? If you disable Ransomware Protection but leave the rest of Malwarebytes running, does the issue occur? Please enable debug service logging, reproduce the issue once more and provide new logs with the Support Tool. To enable debug logging: Open Malwarebytes. Click Settings. Turn the Event log data setting on.
  22. Hi @Homer712, Thank you for the report. To assist our efforts in reproducing the issue you've reported, could you provide the following please: The log file (mbst-grab-results.zip) mentioned in the "technical issue" instructions above. The exact command (or combination of commands/script file) you're running that triggers the issue. Roughly, how often do you clear the event logs?
  23. Thanks for confirming. This explains why there is no dump in the CrashDumps folder after the recent crash. Please let us know if you encounter any further issues.
  24. Thank you for the file! We intend on adding a command line option as well to help with situations like this.
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.