bdubrow

Staff
  • Content count

    676
  • Joined

  • Last visited

About bdubrow

  • Rank
    Staff

Recent Profile Visitors

33,983 profile views
  1. To back up everything that Devin said, the entire team has been working very hard to solve these problems because we are as frustrated as you. It pains us to hear about the program not working as expected. We have been regularly releasing updates and upgrades in an attempt to solve the top reported problems. And with each release we've tried to address the most pressing problems so that you see that we're listening and working to fix things as quickly as possible. Sometimes a big part of the delay is our inability to reproduce the exact symptoms on our own in-house systems. This is why we're constantly asking for logs -- we need to find clues to help us replicate exact environments so we can see the same bad behavior and then narrow down the cause. And since we're focused on getting updates out as quickly as possible we don't always have lots of extra time to spend on the forums. Because of this our valued forum helpers have been pulling double-duty and have also been doing their best to help others out, and we're incredibly grateful for their help! But I'm sure it gets frustrating for them, too, having to deal with the problems being reported. So I think everyone's nerves are a bit on edge. We appreciate everyone who's stuck with us and who continues to help, both on the forum and via private troubleshooting efforts. To those who are frustrated, again, I totally understand. It can take a lot of time and back and forth, and sometimes your issue still isn't fixed. Just know even if you're not actively working with us we'll still work on solving your issues however we can. We just ask that you give our subsequent releases a chance -- I'm confident the known issues will eventually be settled.
  2. Thank you for confirming this!
  3. Thank you for the feedback, PhoneNumberZero! Glad it's working well for you!
  4. Thanks for the additional feedback, mightaswell! Glad you're no longer seeing the BSOD.
  5. Hi Hardhead-- Thank you for your feedback. I've updated my original announcement to suggest that folks first uninstall any earlier version then install the beta. This seems to avoid the issues that you ran into. Glad all is working well for you in the end.
  6. Thank you for the logs, John A and mimghtaswell. We'll review the logs and see if we can repro.
  7. Oops, my bad! I've fixed the typo in main announcement.
  8. Hello all-- Thank you for the feedback! We're monitoring all the comments closely. I've updated my original announcement post to suggest a clean uninstall / reinstall instead of over-installing if you have an earlier version of MB3 installed. This seems to work much better with these special "beta" installers. Please keep us posted on any further issues.
  9. Hi paulderdash-- Thanks for reporting this. This is a symptom we see sometimes if you over-install the "bundled" beta installer over an existing Malwarebytes 3.0 installation. If you do a clean uninstall / reinstall instead you can usually avoid this problem. I've updated the announcement post to reflect this. The reason disabling your license also works is that self-protection is not designed to run in Free mode, so it shuts down automatically. So, if you do a full uninstall of the previous version and then reinstall the 3.0.6.1469+1.0.96 build, are the self-protection settings now responsive? Bottom line, you should be able to adjust self-protection settings as you like, so this is definitely a bug.
  10. Hello-- The product will automatically revert to Free mode after 14 days, so you can always just wait and enjoy the Premium features available during this time. Or, you can simply go to Settings > My Account and click the Deactivate Premium Trial button. Note that once you do this, you cannot re-enable the trial again later. Hope this helps,
  11. Hello-- The recently published “DoubleAgent” attack was disclosed by Cybellum to Malwarebytes on January 20th, 2017. We were already aware of the issue at the time and were working on measures to improve the self-protection mechanism in our product to protect against this attack vector. We released a fix for this in late February. The vulnerability used in the attack is not specific to anti-malware software, it affects any Windows application that does not have the appropriate protections in place. Furthermore, the vulnerability requires the attacker to have local administrative privileges on the target machine.
  12. Hello all-- We have another component package update coming out soon and we wanted to provide the opportunity for you to test it out before we release the final version. Please note, this BETA version should not be installed by anyone running Windows Vista 64-bit. There;s an issue that we're working on with Vista x64, so for now you should simply skip this beta. The bundled installer, which is Malwarebytes v. 3.0.6.1469 plus Component Package Update 1.0.96, can be downloaded from this link. If you have an earlier version of Malwarebytes 3.0 installed, please uninstall it first and then install this new version. Typically with these "bundled" installers for testing a clean install seems to work best. Here's the Change Log for this release: Fixed issue where real-time protection modules do not enable correctly Fixed Bad Pool Header BSOD while web browsing (in majority of cases) Fixed issue that could cause user to have to login with a temporary profile instead of their standard user profile Additional enhancements to improve memory usage Fixed issue where 3.0.5 could revert to version 3.0.0 in certain conditions Fixed numerous crashes, including service crashes Addressed several vulnerabilities The Web Protection block page now redirects to https://block.malwarebytes.com Fixed issue where Web Protection would not re-enable properly after booting back from minimal safe mode on Vista Numerous enhancements to overall protection and remediation Please post a new topic in this forum with any feedback you have on this latest version. Thanks in advance!
  13. Hello, calintexas-- You're correct that you'll no longer find the old Daily Protection Log in the new Malwarebytes 3.0. All program logging and reporting is completely different in the new version. The Daily Protection Log has been replaced with more robust logging to our mbamservice.log (pretty much only needed for troubleshooting purposes if you contact support) and then Protection Events in the Reports section. You'll see an individual Protection Event report every time you have a real-time protection block on your system -- ransomware detection, website blocked, malware blocked, etc. Glad 3.0.6 is working well for you!
  14. Hello-- We're not able to notify people individually, but we always post an announcement with a Change Log listing all fixes and enhancements whenever a new version is released. What I would suggest would be to click the Follow button in upper right for this post: And then ensure your forum Notification Settings are set up so that you'll receive a notification when a new post is added. This way you don't have to proactively come back and check the status but will be notified as soon as there's news.
  15. @Honey097 @feltchcc and any others who may have seen the update status not refreshing earlier... Please do a a check for updates and ensure you're on Update Package 1.0.1562 or later, and then reboot your system. There was an issue with an earlier update which caused some systems to get stuck in the odd update state. To fully recover, the reboot is necessary.