Jump to content

LiquidTension

Staff
  • Content Count

    3,278
  • Joined

  • Last visited

Everything posted by LiquidTension

  1. Hi @Tuxedo, Thanks for testing the beta and providing feedback! We're glad to see you've had a positive experience so far. Turning this setting on isn't necessary. We're currently not providing Malwarebytes 4 beta updates via this in-application channel. For future beta version releases, the best place to obtain them from is this forum section.
  2. Thanks very much. I can confirm this is indeed a false-positive. If you find the file is detected again in a Malwarebytes scan, I recommend excluding it using the steps below: At the end of the scan, remove the checkmark next to the detection. Click Next. Click Always Ignore.
  3. The Malwarebytes Support Tool has been updated to support the Malwarebytes version 4 beta. A full change log for the new 1.5.1 version can be found here. Note: Start Repair and Advanced > Clean will continue to reinstall Malwarebytes version 3 after a removal has taken place. The option to install Malwarebytes version 4 will be available once the product is out of beta. Please create a topic in this forum section if any issues are encountered with the tool when running on a computer with Malwarebytes version 4 installed.
  4. Malwarebytes Support Tool version 1.5.1 is now available! You can find the new change log below. For all archived change logs, you can find them in the first post above. Added log gathering support for Malwarebytes version 4, including setup logs and new configurations/settings output. Added clean removal support for Malwarebytes version 4 to the Start Repair and Advanced > Clean options. Note: Start Repair and Advanced > Clean will continue to reinstall Malwarebytes version 3 after a removal has taken place. The option to install Malwarebytes version 4 will be available once the product is out of beta. Added additional output to mbst-check-results.txt, such as the state of hibernation and fast startup. Updated the System Repair options to fully support Windows 10 v1903. Deprecated support for Malwarebytes Support Tool on Windows XP and Vista. Version 1.4.1 is the last supported version of the tool on Windows XP and Vista. Running a newer version with an active Internet connection will result in the tool downgrading to version 1.4.1. If an Internet connection is not available, the tool can be downloaded manually using the following link: https://downloads.malwarebytes.com/file/mbst1.4
  5. Thanks for the file! The F-PROT detection for FRST64.exe is a false-positive and can be disregarded. The file confirms you have indeed encountered the issue I mentioned. This should be fixed in the next release. Could you provide us with the following file so we can take a closer look at it, please? C:\WINDOWS\INSTALLER\6BDE1B.MSI
  6. Hi @TomSr, The issue with accessing the beta download link should now be resolved. Please try downloading again and let us know if you encounter any further issues: https://malwarebytes.box.com/s/rh184fejmd9iyt3hrh0d2krchdobqcy5 Thanks for being a Malwarebytes beta tester!
  7. Malwarebytes version 3 does indeed open to the UI to the dashboard as well. However, with version 3, there is indication on the dashboard that a check is being performed (with "Updates: Current" being displayed once the check has completed). We've certainly made a note of all the user feedback provided on the update process in Malwarebytes version 4 and are looking into different methods of improving the overall experience with this.
  8. Hi @Dark_IT, Thanks for confirming! We appreciate you trying out the beta and providing feedback. If you do encounter any issues going forward, we'd love to hear.
  9. Hi @ToddLemire, Thanks for trying out the beta. There is a known issue currently where detections that should be displayed in the user interface at the end of the scan are still displayed. To help us confirm, please carry out the instructions linked below and attach the generated file: https://support.malwarebytes.com/docs/DOC-2396 Thank you!
  10. Hi @rlkufrin, Thanks for sharing your feedback with us. This is a known issue which we hope to have fixed in the next release. Regarding the other issues you mentioned - please could you carry out the instructions linked below and provide the generated file so we can take a closer look. https://support.malwarebytes.com/docs/DOC-2396 Thank you!
  11. Hi @Durew, Thanks again for testing out the Malwarebytes beta. In regards to the concern you raised on the HitmanPro.Alert test - here are a few points of consideration: Malwarebytes is committed to providing excellent protection against real-word threats and attack vectors that pose a true danger to computer users. We believe everyone is entitled to a malware-free existence and thus dedicate as many resources as we can to helping achieve this. We consider any indication of Malwarebytes Anti-Exploit being unable to provide protection against a real-world exploit as a serious and urgent matter. Test utilities such as the HitmanPro.Alert test are not real-world exploits with no guarantee of even closely resembling a real threat. It would be a disservice to Malwarebytes Anti-Exploit users if we were to dedicate time and resources away from combating actual threats that pose a true danger to computers. Third-party utilities may be updated and changed on a regular basis, with no rules or guarantees in place that such utilities still function as intended. As a result, not only an initial but also a continual dedication of resources would be required to maintain "support" for these utilities. We simply believe time and resources are better spent fighting actual malware. As a result, we cannot commit to providing support for any and all third-party exploit test utilities.
  12. Thanks @NeilA! Am I correct in saying that when you rebooted the machine (after you were able to open Malwarebytes and run a scan), the program will now no longer open? Prior to the first Malwarebytes version 4 installation attempt, are there any details you can provide on your previous Malwarebytes version 3 installation? For example: Was Self-Protection enabled? How long had version 3 been installed? Did you have any issues with installing version 3? When you ran the Malwarebytes version 4 installer, was version 3 running at the time? Please could you provide us with the following: Export Event Logs Press the Windows Key + R on your keyboard at the same time. Type eventvwr.msc and click OK. Expand Windows Logs. Right-click Application and click Save All Events As.... Name the file application and click OK. Repeat for Security and System. Expand Applications and Services Logs in the panel on the left. Expand Microsoft followed by Windows. Scroll down the list and expand CodeIntegrity. Right-click Operational and click Save All Events As.... Name the file CodeIntegrity and click OK. Navigate to the location of the files. Highlight the four files, right-click one and click Send to followed by Compressed (zipped) folder. Name the Zip file EventLogs.zip and attach the file in your next reply.
  13. Excellent. Thanks for confirming! We have a defect filed for this issue. For now, I recommend leaving the Enable self-protection early start turned off.
  14. Hi @f14tomcat, Just following up to see how you're getting on. We'd very much appreciate the information mentioned above to help us troubleshoot this issue.
  15. Hi @RTL434, Thanks again for the latest information. Have you tried a scenario where Malware Protection is on, only Malwarebytes Service is enabled as a startup item and the machine is restarted? Do you still see the hang with this scenario? It will be useful for us to obtain a memory dump captured when the machine is in the hung state. We can accomplish this by forcing a blue screen. Start by ensuring complete/full memory dumps are enabled: https://www.tenforums.com/tutorials/5560-configure-windows-10-create-minidump-bsod.html Then proceed with the steps below. Download enable_forced_bsod.reg using the link below: → https://malwarebytes.box.com/s/8rxpxrwm4jmdz95dg5p1kudymdl4vtzm Open your Downloads folder or location of the downloaded enable_forced_bsod.reg file. Double-click enable_forced_bsod.reg and click Run followed by Yes if prompted by User Account Control. Click Yes when prompted to continue. Click OK. Restart your computer. Once the machine is in the hung state, hold down the rightmost Ctrl key on your keyboard and press the Scroll Lock key twice. This will force your machine to blue screen. After the computer has rebooted, open the C:\Windows folder and verify a file named MEMORY.dmp is present. Right-click MEMORY.dmp and click Send to followed by Compressed (zipped) folder. If prompted to save the file to your Desktop, click Yes. Upon completion, upload the Zip file to a file hosting service of your choice and provide a download link in your next reply.
  16. Hi @lgkahn, Thanks for the report. The old user interface is expected but the missing results is not. What type of scan did you run? What were the exact steps you took to reach this state? Please could you carry out the instructions in the article linked below and attach the generated file: https://support.malwarebytes.com/docs/DOC-2396
  17. Hi @Dark_IT, Thanks for trying out the beta and providing feedback! This is expected behaviour. The default scan type is only for the system drive. When you configured this scheduled scan, did you also change the scan date? Or just the start time? Thanks for this feedback. We've had similar feedback from other users on the status information that's displayed during an in-progress scan. Our user interface team are aware of this. That's great to hear. Thank you!
  18. Hi @JamieBrown, Thanks for trying out the beta! What type of scan are you running? In addition to the information mentioned above, could you also carry out the instructions in the article linked below and attach the generated file to a forum post: https://support.malwarebytes.com/docs/DOC-2396 Thanks!
  19. Hi cofused, That's OK - thanks for trying out the beta and we're sorry you encountered these issues. If you'd like to revisit troubleshooting, just let us know.
  20. Thanks for the file! Please do the following: Open Malwarebytes. Click Settings. Click Security. Under Windows startup, click Advanced. Turn the, "Enable self-protection early start" setting off. Close Malwarebytes. Once done, please restart the computer and check if the issue still occurs.
  21. Thanks for the feedback, @John A! The update check functionality in Malwarebytes 4 is currently being worked on. This behaviour is being looked into.
  22. Thanks for the file. If you're able to reproduce the behaviour again (significant difference in the time it takes for the UAC prompt to appear when disabling one protection modules vs another), please enable debug logging using the steps below and let us know. Open Malwarebytes Click Settings Turn the Event Log Data setting on.
  23. Hi NeilA, Thanks for the report. Please could you provide the following files as well: C:\Users\Neil\AppData\Local\Temp\mbsetup.log C:\Windows\temp\mbamiservice.log Thank you!
×
×
  • 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.