bdubrow

Staff
  • Content count

    712
  • Joined

  • Last visited

About bdubrow

  • Rank
    Staff

Recent Profile Visitors

35,659 profile views
  1. Hello-- Thank you for providing the information! Just wanted to confirm that we will have another component update released shortly for Malwarebytes 3.1 and this should no longer be a problem once that update is applied. After a scan all detected traces will be able to be excluded properly.
  2. A later component package update has been released: 1.0.141 This included a minor change to how threat data is sent back to us. The installer from the website has also been updated to include this package now.
  3. Hi all-- Just wanted to clarify that in general component package updates (CUs) will not be announced and we won't be posting specific change logs for these. These updates are meant to be applied silently and automatically in the background. We've broken this rule in the recent past because we had a few high-profile issues that were addressed by a particular CU and we wanted to specifically call those out. But this shouldn't be considered "normal." These updates are meant to address miscellaneous defects, protection technique improvements and stabilization enhancements. In fact, those items can be considered the perpetual change log for these CUs going forward. We are constantly improving process and access to the latest versions of our software. Within a day or so after a new CU is released we'll have up updated full installer available from our website with the latest CU and database updates included. This means anyone downloading Malwarebytes 3 from our website will always have the most up-to-date software. We are also working on improvements that will allow you to always pull down the latest components or full program versions from within MB3 even if the "allowable level of upgrades for the day" set on our side has been met. This means that clicking Install Application Updates will automatically pull down any available CU updates or program upgrades regardless so those wishing to manually upgrade can always do so quickly and easily.
  4. Thank you for reporting this! We will look to getting this corrected.
  5. We have just released a new component update package for Malwarebytes 3.1 -- 1.0.139. Here are the high level items fixed: Improved performance with Microsoft Edge Some additional memory usage enhancements Fixed an issue where the “Enable self-protection early start” setting could interfere with upgrades Fixed a conflict with K9 Web Protection Several other miscellaneous crash and defect fixes This update is applied automatically if you have automatic application updates enabled. If you don't wish to wait for the automatic update, you may manually install using our updated Malwarebytes 3.1 installer, which can be downloaded from our main website or from this link. Thanks!
  6. On May 19, 2017, we received reports from Malwarebytes 3.x users that Malware and Web Protection modules disabled themselves and any attempted scans stopped almost immediately after starting. Malwarebytes Anti-Malware 2.x users were not impacted by this incident. During the investigation, we identified that the root cause of the problem was by a database publish processing error that caused certain Malwarebytes 3 incremental database packages to be built incorrectly, causing the symptoms mentioned above. We have also confirmed that this problem only affected 64-bit packages starting with Update Package Version 1.0.1973 published at 5:04AM ET, which was validated by our telemetry. Upon confirming the issue, we immediately paused updates (at 7:31AM ET) to prevent further corrupted updates from being sent out to any Malwarebytes 3.x customers. We then fixed the issue on the database processing pipeline and published an updated database package with version number 1.0.1976 posted to our servers at 8:49AM ET. Simultaneously, we resumed normal database update deployment. The majority of Malwarebytes 3 users with automatic updates enabled recovered from this situation automatically. In a small number of cases, a reboot or restart of the Malwarebytes service might be required to re-enable the protection modules. We deeply apologize to those who were affected by this issue and our deepest gratitude for your patience with us during this ordeal. We do believe you deserve better than this. As you read this, we have already identified several areas where our database publishing process can be improved and have started implementing better error checks, and will continue to do so, to ensure that this does not happen again in the future.
  7. Thanks for the feedback, Firefox! The other bit of info I can provide is that we do periodically reset the trial flag so that even if an installation has already received its trial there's a possibility to trial in the future. We can't guarantee when that might be, but just wanted to throw that out there. The type of control you're looking for will most likely not be added back into our standard home version any time soon. I'll get it added to the list for consideration and discussion though.
  8. Hi Phobos_Anomaly-- The product will notify you when it is expiring and so long as you renew your current subscription and do not let it lapse, your subscription will be renewed at your original subscription rate. Renewing 1 day prior to expiration is fine. If the subscription lapses, then basically it means you would need to purchase a new subscription at the new price. Hope that helps,
  9. Hi MikeAustin-- To add to Firefox's advice and request for logs, I wanted to mention a couple things. What you're seeing on your system is definitely not normal. If you're still running Kaspersky, then mutual exclusions may very well be necessary to get the two products to play nicely together. The new Malwarebytes 3.x is a complete rewrite from the ground up and integrates several new protection technologies which is why it behaves differently from the legacy MBAM 2.2. Just because an older version didn't require exclusions for certain other security apps does not mean a completely new version would not require them. I can tell you we have many, many users running Malwarebytes 3.x alongside Kaspersky with no issue. Even if whatever is going on on your system is not due to compatibility issues, we are typically able to help troubleshoot if you work with us. The level of protection provided in 3.x greatly surpasses what you have in 2.x, so I'd encourage you to upgrade.
  10. Hi prombamuser-- This is actually expected now with version 3.1.2. You will only see a notification if malware has been detected via a scheduled scan. You can still see full Scan Logs and results in the Reports section should you ever want to verify scans are running. Hope that helps,
  11. Hello, PPg-- Thank you for checking with us! We actually just released a new version of Malwarebytes earlier this week: There was an issue with Defender that has been corrected, so I would suggest you upgrade to v. 3.1. You can set the Windows Action Center settings however you like--you can leave it at "Never register" if you like. This just means you won't see Action Center notifications regarding Malwarebytes, but it doesn't affect the program's protective capability. But if you want to change it back to the default "Let Malwarebytes decide" then it will register Malwarebytes alongside Defender and you'll see both there. Thanks,
  12. Great news! Thank you for confirming, Nerius!
  13. Hi Nerius-- Glad v. 3.1.2 is running well for you. Regarding your comments on self-protection, are you still experiencing system slowdown with this protection module enabled? This new version should perform much better there. Also, the issue with self-protection event log errors has been solved for some time--since the initial release of 3.0. You shouldn't see those types of entries in event log with 3.1.2, so if you do, please let us know. Thanks!
  14. Hi Fryl-- Please go with the newly released Malwarebytes 3.1, as this version replaces the last beta. Please let us know how it goes. We did make improvements to the Web Protection so hopefully you'll see better performance there. Thanks,
  15. Greetings! I'm happy to announce that Malwarebytes v.3.1 is now available. You can download this new version -- v. 3.1.2.1733 -- from our main website or from this link. You can install this new version directly over any earlier Malwarebytes version you might be running. Here's What's New & Improved: Performance/protective capability Multiple enhancements result in reduction of memory usage Faster load time and responsiveness of third-party applications Improved performance of Web Protection Faster Malwarebytes 3 program startup time and responsiveness of user interface New detection and protection layer with machine learning based anomaly detection (to be deployed gradually even if it shows “enabled” under Settings) Improved Self-Protection by requiring escalated privileges to disable protections or deactivate a license Enhanced malware protection techniques and remediation capabilities Added an automatic monthly scheduled scan in Free mode Usability Added ability to control the priority of manual scans on the system Added setting to turn off ‘Real-Time Protection turned off’ notifications when protection was specifically disabled by the user Added ability to exclude the last website blocked by Web Protection via the tray menu Fixed several defects related to configuring Custom Scans, including selecting child folders and fixing issues with touch screens Fixed problem where a right-click context scan appeared broken after scheduled scan due to misleading "Cannot start a scan while another one is in progress" message Fixed issue where you could not add or edit a scheduled scan in Spanish and some other languages Fixed issue where scan could appear stuck on Heuristics Analysis when it had actually completed successfully Fixed issue where Self-Protection setting would fail to toggle correctly after an upgrade Stability/issues fixed Fixed several crashes in the Web Protection module Fixed issue where Ransomware Protection would be stuck in ‘Starting’ state after a reboot Fixed a conflict with Norton that caused web pages not to load and plug-ins to crash in Chrome Fixed issue with WMI protection technique in Exploit Protection that could cause Office applications to crash Fixed several crashes related to the service and tray Fixed security vulnerabilities that could be chained together to perform local privilege escalation - special thanks to Wayne Low of Fortinet's FortiGuard Labs for alerting us to the vulnerabilities Fixed many other miscellaneous defects and user interface improvements Thanks,