Jump to content

LiquidTension

Staff
  • Content Count

    3,084
  • Joined

  • Last visited

Everything posted by LiquidTension

  1. Hello, Thank you for providing the mbst-grab-results.zip file. Please could you also carry out the instructions in the following article: https://support.malwarebytes.com/docs/DOC-1318 Attach the two generated files (FRST.txt and Addition.txt) in your next post.
  2. That's correct. There's a single installer file for Malwarebytes, that encompasses both the Free and Trial/Premium versions. Once you've installed Malwarebytes using the following instructions, refer to the articled linked in Porthos' post above for steps on how to activate Premium with your license ID and Key. We recommend running Malwarebytes alongside the built-in Windows 10 for the best combination of protection and performance. Most users experience no issues running both programs together and exclusions are typically not required. However, if you do notice an impact on performance or other issues with the computer, exclusions can indeed be configured to help mitigate the issue.
  3. Hello ncodex, Thank you for reporting the issue. Please see this post for further details:
  4. Thank you to everyone who has provided feedback on this issue. We're investigating the cause and will provide further details shortly. Please keep in mind that with this issue affecting a beta Operating System, issues are to be expected. It would help if troubleshooting logs could be provided. Please refer to the following topic: https://forums.malwarebytes.com/topic/190532-having-problems-using-malwarebytes-please-follow-these-steps/ In addition, a Process Monitor log would also be helpful. Please refer to the steps below. Run Process Monitor Quit Malwarebytes by right-clicking the Malwarebytes notification area icon (next to the clock) and clicking Quit Malwarebytes. 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 black Command Prompt window will appear. When prompted to carry out the tasks, please do the following: Try to launch Malwarebytes and wait for the DDA Driver error. Don't click Yes to restart. 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).
  5. Thank you to everyone who has provided feedback on this issue. We're investigating the cause and will provide further details shortly. Please keep in mind that with this issue affecting a beta Operating System, issues are to be expected. It would help if troubleshooting logs could be provided. Please refer to the following topic: https://forums.malwarebytes.com/topic/190532-having-problems-using-malwarebytes-please-follow-these-steps/ In addition, a Process Monitor log would also be helpful. Please refer to the steps below. Run Process Monitor Quit Malwarebytes by right-clicking the Malwarebytes notification area icon (next to the clock) and clicking Quit Malwarebytes. 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 black Command Prompt window will appear. When prompted to carry out the tasks, please do the following: Try to launch Malwarebytes and wait for the DDA Driver error. Don't click Yes to restart. 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).
  6. Yes, it's related to use of MB-Clean DLL that's utilised by Malwarebytes Support Tool Repair.
  7. Hi Mike, It looks like you clicked Start Repair when you ran the Malwarebytes Support Tool. Please rerun the tool and click Advanced followed by Gather Logs. Please avoid using the Start Repair button.
  8. Please ensure the files inside the procdump.zip file are extracted first (right-click procdump.zip > Extract All... > Extract). You'll then have the option to run the memory.bat file as administrator.
  9. Thanks for the update. Did you confirm Malwarebytes is up-to-date? If you have, we'll need to collect some troubleshooting logs to investigate further. Please carry out the instructions in the forum topic linked below: https://forums.malwarebytes.com/topic/190532-having-problems-using-malwarebytes-please-follow-these-steps/ Upon completion, a file named mbst-grab-results.zip will be saved to your desktop. Please attach this file in a forum post.
  10. Thanks for the image of the block! We removed the block on doubletwist.com yesterday. Please ensure your Malwarebytes is up-to-date by opening the program and clicking Current as depicted below. Let me know if you still encounter the same block afterwards.
  11. Thanks for the update. I've passed on this information to the developers.
  12. @TekGamer Thank you for reporting the log file issue. We've identified the cause of this issue and will be working on a fix.
  13. Hi Gary_D_from_Canada, Do you have the URL/address of the webpage generating this fake alert? It should be visible at the top of your browser window. Once provided, we can add it to the Malwarebytes database so it gets blocked by the Web Protection component.
  14. Thank you for reporting, COBKA. To confirm, the high CPU usage is experienced with the Avast service named "avast! Antivirus" (that points to C:\Program Files\AVAST Software\Avast\AvastSvc.exe)? Please reproduce the high CPU usage with AvastSvc and then carry out the steps below so we can obtain a memory dump. ProcDump (Memory Dump) Please download the attached procdump.zip. Open your Downloads folder. Right-click procdump.zip and click Extract All... followed by Extract. Reproduce the high CPU usage with AvastSvc. Locate the extracted procdump folder inside your Downloads folder. Open the procdump folder. Right-click memory.bat and select Run as administrator to run the file. Note: If you are prompted by Windows SmartScreen, click More info followed by Run anyway. Wait 10-30 seconds and the Command Prompt will eventually disappear. Return to the procdump folder. Inside you should now find a file with a .dmp extension. Right-click the .dmp file and click Send to followed by Compressed (zipped) folder. This will create a Zip file in the folder. Please attach the Zip file in your next reply procdump.zip
  15. Thanks for following up with us, Rich! Let us know if you encounter any further issues.
  16. For Windows 10 machines, our recommendation is to use Malwarebytes in conjunction with the built-in Windows Defender. We believe this offers the best combination of protection and performance. Aside from that, many users run Malwarebytes along with a third-party Anti-Virus without issue. However, this is not always the case and can result in performance issues or other problems with the computer. We typically recommend configuring mutual exclusions in both products if a third-party Anti-Virus is installed alongside Malwarebytes. This resolves any issues in a lot of cases. Other times, tweaking settings may be required to allow coexistence between the two products. Have you configured mutual exclusions in Malwarebytes and VIPRE? If you fully disable or temporarily uninstall VIPRE, does the issue persist?
  17. Hi Mike, Please provide us with the log file referenced in the post above. This will allow us to look into the issue you're experiencing.
  18. Thank you for the follow-up. Out of interest, when you were changing settings with the previous version, were you dragging the toggle across to the off position or clicking directly on the off position?
  19. Thank you everyone for the continued feedback. To those reporting improved startup/shutdown performance with CU 1.0.527 - is this with all Real-Time Protection components enabled (Ransomware Protection included)?
  20. As Porthos mentioned above, we meter component package updates out gradually overtime to the Malwarebytes userbase. A lot of software rolls out significant updates like this to help handle support requests or try to catch issues that may arise. Manually checking allows you to obtain the update immediately. If a manual check is not performed, you will still eventually receive the update automatically in the background - it may just take additional time for that to occur.
  21. Yes, that'd be a great - thank you. Also, please could you configure Process Monitor to perform boot-time logging > restart > reproduce the hang > upload the generated Process Monitor boot logs.
  22. @Kabutocub Did the issue occur prior to installing 18323 (19H1)? @siliconman01 Thank you for the logs. Please carry out the Process Monitor instructions below and provide the generated file. Run Process Monitor 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 black Command Prompt window will appear. When prompted to carry out the tasks, please do the following: Try to launch Malwarebytes and wait for the DDA Driver error. Don't click Yes to restart. 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).
  23. Hello, Thank you for providing the troubleshooting logs. Please do the following: Right-click the Malwarebytes icon in the notification area (next to the clock) and click Quit Malwarebytes. Press the Windows Key + R on your keyboard at the same time. Type services.msc and click OK. Scroll through the list of services until you reach Malwarebytes Service. Right-click Malwarebytes Service and click Properties. Set the Startup type to Automatic (Delayed Start). Click OK and close the Services window. Once done, please restart the computer (Start button > arrow next to Shut down > Restart). After the restart, please open Malwarebytes and verify the state of the Malware Protection, Web Protection and Ransomware Protection. Let me know how you get on.
  24. Hi RTL434, Thanks for the updated logs. Do you occasionally disable/change your network adapter or disconnect from the Internet for extended periods of time? Please do the following: Ensure Malwarebytes Premium is activated. Download MBSupportInfo.exe using the following link: https://malwarebytes.box.com/s/qhyxw7gwikqs213znxwht4q1xnqpav5h Double-click MBSupportInfo.exe to run the tool. Note: If you are prompted by Windows SmartScreen, click More Info followed by Run anyway. A Command Prompt window will briefly appear then close. A file named SupportInfo.dat will be created in the same folder as MBSupportInfo.exe. Please rename this file to SupportInfo-Before.dat and move it to a safe location. Please wait until the next time the issue occurs. Afterwards, please rerun the MBSupportInfo.exe tool. A new file named SupportInfo.dat will be created. Please rename this file to SupportInfo-After.dat. Please attach both files to a forum post.
×
×
  • 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.