Jump to content

New CP 1.0.207


Recommended Posts

10 minutes ago, Phone Man said:

Any information on it?

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.

Link to post
Share on other sites

2 hours ago, Porthos said:

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.

Hi Porthos:

This policy makes no sense at all.  What difference does it make if the version number of the main program or the CU changes when a bug fix is released?

Several users were told that the new CU would contain a bug fix for an issue where Firefox can crash if the MB Self-Protection module is enabled (see Malwarebytes employee nikhils' comment <here> for one example).  What harm would it do to pin a change log at the top of the board to let affected users know they should run Settings | Application | Install Application Updates to receive the new CU ASAP and re-enable their Self-Protection module?
-----------
32-bit Vista Home Premium SP2 * Firefox ESR v52.3.0 * NS Premium v22.10.1.10 * MB Premium v3.2.2.2018 (CU 1.0.188)

Edited by lmacri
Link to post
Share on other sites

2 hours ago, Porthos said:

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."

 

This bug is important yes. What they are saying is unless a full new version is released for example 3.3.0 you are not going to see lots of fanfare. 

Link to post
Share on other sites

  • Staff

Hi all--

@Porthos is completely correct when explaining that typically there will be no fanfare when releasing new component updates.  They should be considered business as usual.

In cases such as the issue with Firefox, what our staff typically do in those cases is reply to threads they're watching here once a fix has been released.

As @nikhils mentioned, the fix was released in the latest component package 1.0.207.  If you have not received that component update automatically yet, if you have Malwarebytes 3.2.2 installed you can go to Settings > Application > Install Application Updates to get it. (Note: manually checking may not work with versions earlier than 3.2.2 due to upgrade limits enforced on the backend.)

Also, just a note that we typically post a refreshed installer on our website with the latest component package bundled in.  We'll be doing that again with this one a little later today.  Once we do that you'll see a revised installer -- a new look and we've reduced the number of steps required to install with default settings.  Just wanted folks to be aware that this is legit since it will look very different from the old installer look we've had for years.  :)

Link to post
Share on other sites

1 hour ago, bdubrow said:

@Porthos is completely correct when explaining that typically there will be no fanfare when releasing new component updates.  They should be considered business as usual.

In cases such as the issue with Firefox, what our staff typically do in those cases is reply to threads they're watching here once a fix has been released...

Hi bdubrow:

I have a slightly different perspective as a customer.  That could also be interpreted as "we don't want any permanent record of CU bugs documented in our change logs".

Malwarebytes only releases CU updates every month or so, so even if they don't contain an important bug fix why not just have a separate change log for the CU with the ubiquitous "minor improvements" (if the change is minor), or post a description of the bug fix after early testers have had a chance to provide feedback on how well the fix works?

If Malwarebytes wants to promote the new MB Premium v3.x as an "antivirus replacement" and try to convince me that I don't need my current third-party AV,  or claim that MB Premium v3.x CU components like Exploit Protection will run seamlessly in real-time alongside my AV without conflicts, they're going to have to do a much better job of documenting known bugs in their product.
-----------
32-bit Vista Home Premium SP2 * Firefox ESR v52.3.0 * NS Premium v22.10.1.10 * MB Premium v3.2.2.2018 (CU 1.0.188)

Edited by lmacri
Link to post
Share on other sites

  • Staff

Hi lmacri--

Interesting perspective!  Certainly not at all what we're intending, especially as we try to be as transparent as possible here on the forum and elsewhere regarding any defects in the program.

But we'll definitely take your feedback into consideration.  We had discussed this a while back when we first started releasing component updates, so we'll see what we can do.

We also intend to more actively use our new "beta channel" to verify fixes. While the beta channel did get this package earlier than the rest of the world, we still need to improve that process and get more info out there.  So if anything the beta forum might have the detailed changes spelled out earlier in the future.

For the record here's a list of changes for the 1.0.207 update:

  • Numerous enhancements to detection and remediation
  • Improved driver management
  • Fixed issue on XP where Firefox would crash when self-protection was enabled
  • Closed connection to AWS that did not need to be left open

 

Link to post
Share on other sites

Information like this is good to have, for instance, if a user uninstalled MBAM due to issues with Firefox ( or any other issue for that matter) then knowing that said issue was resolved would aid the customer into knowing that they could re-install without any problems arising. Transparency with a customer base is always the best policy in my opinion.

Link to post
Share on other sites

3 hours ago, bdubrow said:

....We had discussed this a while back when we first started releasing component updates, so we'll see what we can do...

For the record here's a list of changes for the 1.0.207 update:

  • Numerous enhancements to detection and remediation
  • Improved driver management
  • Fixed issue on XP where Firefox would crash when self-protection was enabled
  • Closed connection to AWS that did not need to be left open

Hi bdubrow:

Cheers, and thank you for taking customer feedback about posting of CU change logs under further consideration.
-----------
32-bit Vista Home Premium SP2 * Firefox ESR v52.3.0 * NS Premium v22.10.1.10 * MB Premium v3.2.2.2018 (CU 1.0.188)

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • 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.