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. https://d2wqgvap25i10a.cloudfront.net/emoticons/default_smile.png
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.

and it's showing an end date of 6/8/17t
...end of support, does that mean that after that date if user runs 2.2.1 that its definitions will not update? the info was not entirely clear to me or the font was too small.

and it's showing an end date of 6/8/17t
...end of support, does that mean that after that date if user runs 2.2.1 that its definitions will not update? the info was not entirely clear to me or the font was too small.

Click to expand...

It was posted on their forum that Definition updates would continue but could end at any time. No bug fixes for older versions will be released.

Just got an e-mail from Cleverbridge informing me that they charged my credit card for another year of Anti-exploit.
I am pretty sure when we upgraded with out lifetime Lic for Malwarbytes and then upgraded to 3.0 We were suppose to get The entire product as a lifetime Lic. I don't want 2.0 and pay for Anti-exploit.

If you have a lifetime license, it should work for any version. I gave my license a try and it still works.

Click to expand...

OK at first I was using the lifetime for Malwarbytes but the Yearly for Anti-exploit. Both had different Lic numbers. When I register my Malwarbytes 3.0 and enter my Malwarbytes 2 Lic it shows lifetime. Posted on Malwarbytes forum a bit ago.

I decided to try V3 again.
- downloaded installer from their site
- deactivated licence for V2
- uninstalled V2 and rebooted
- installed 3.1.2.1733 with 1.0.141-1.0.2092
- used V2 licence - accepted
- left all settings at default
and have had no problems, so far.

My auto renewal is on 2017-07-13 so I have some time to evaluate whether I should renew or cancel.

- installed 3.1.2.1733 with 1.0.141-1.0.2092 - left all settings at default

Click to expand...

One setting I would check is "scan for rootkits". It was off by default originally and I don't know if that changed at some point. There's also an option to drop scan priority on manual scans which is handy if you like to keep working while the scan is running.

One setting I would check is "scan for rootkits". It was off by default originally and I don't know if that changed at some point. There's also an option to drop scan priority on manual scans which is handy if you like to keep working while the scan is running.

Click to expand...

Thanks Victek. I turned "scan for rootkits" ON, ran a Scan and the Rootkits scan took maybe 8 seconds, no problems, looks like I'll keep V3.

There were a number of defect fixes, protection improvements and stabilization enhancements, but here are the top items:

Fixed compatibility issue with SEP 12/14 that caused most of our protection modules not to start correctly

Fixed an issue that could occur on a CU update that could cause anti-exploit to not start properly

Fixed a number of issues with Exclusions, including Scan Exclusions not working correctly for all trace detections

The installer available from our website has also been updated to include this package now, available from this link..

Click to expand...

I run MB3 on demand on my primary machine. I opened it now and it did auto-update component package, but from 1.0.122 to 1.0.141.
On the secondary machine, where it starts with Windows, it is also at 1.0.141.
Maybe the 1.0.160 auto-update will roll out over a few days?

New versions of the Malwarebytes MB-Check (version 3.1.2.1001) and MB-Clean (version 3.1.0.1014) utilities are now available to those that may need them.
Announcement, overviews, download links, and changelogs here: Malwarebytes Support Tools

MB-Check 3.1.2.1001

Added ability to check and log Anti-Exploit configuration settings

Added path to the location of mb-check.exe in the log output

Fixed false positive on missing subfolders

Fixed failed download and execution of "mbam-check.exe" when legacy products are detected on XP operating systems

Click to expand...

MB-Clean 3.1.0.1014:

Fixed issue where MB-Clean attempts to delete %systemroot%\System32\drivers\ directory. Note: No harm is actually done to the system, this directory was not and cannot be deleted as it is protected by Windows.

MB-Clean 3.1.0.1013:

Added ability to cleanup Malwarebytes Anti-Exploit when the uninstall key is missing or the product is partially installed

Added ability to cleanup Malwarebytes Anti-Ransomware when the uninstall key is missing or the product is partially installed

Added the option to accept the Malwarebytes End User License Agreement (EULA) before starting up

I run MB3 on demand on my primary machine. I opened it now and it did auto-update component package, but from 1.0.122 to 1.0.141.
On the secondary machine, where it starts with Windows, it is also at 1.0.141.
Maybe the 1.0.160 auto-update will roll out over a few days?