3.2.2.2029 Release Notes?

[Krusty]

Are there any?

[AdvancedSetup]

Hello @Krustyy

Please see the following

https://www.malwarebytes.com/support/releasehistory/

 

[Krusty]

Hi Ron, remember me? 

Aren't they the Release Notes for 2.2.2.2018?

Thanks.

Edited September 15, 2017 by Krusty
Too many "R's"

[AdvancedSetup]

Yes, I remember you. Hope you're doing well. There are notes for all versions there now.

Cheers

Ron

 

[Krusty]

... But that is still dated 22nd of August.

Thanks.

[AdvancedSetup]

I'll let the web team know. Thanks

 

[Krusty]

Cool!

Thank you, Sir.

[bdubrow]

Hi Krusy--

The Malwarebytes 3.2.2.2029 version was simply the exact same v.3.2.2 release with a small change to the installer.  No other functionality or code was changed. The Release Notes for 3.2 still apply to this version.

There is no need to upgrade to this version if you already have any v. 3.2.2 installed. 

You can certainly over-install if you'd like, but it's not necessary.  So long as you're on v. 3.2.2 you'll receive future Component Package and Installer updates/upgrades as usual.

[Porthos]

1 minute ago, bdubrow said:

with a small change to the installer.

Guess that explains the forced restart before install.

[bdubrow]

That will only happen in certain cases, depending on system, version being upgraded from, etc. This is only in the event of any pending Malwarebytes actions that have not yet been completed (such as not having completed a reboot after a remediation, for example.)  Not everyone will see this. 

And actually, this behavior was in initial 3.2.2 release.  So if you've only just seen it, it shows that it will not happen every time.

Edited September 15, 2017 by bdubrow
clarified this restart behavior was in 3.2.2 before

[lmacri]

22 hours ago, Porthos said:

Guess that explains the forced restart before install.

MB employee Santos117 posted some additional information about this bug fix in the thread New Malwarebytes update removed the program from my PC. If I understand correctly, there was an issue with the Self-Protection module where the MB v3.2.2 installer would not launch after re-boot if users tried to perform a product update or over-the-top upgrade from MBAM v2.1.1.

EDIT:

Sorry, dbudrow.  Didn't realize you'd posted further details while I was composing my reply.
----------------
32-bit Vista Home Premium SP2 * Norton Security Premium v22.10.1.10 * MB Premium v3.2.2.2018 (CU v1.0.188)

Edited September 16, 2017 by lmacri

[Krusty]

On ‎16‎/‎09‎/‎2017 at 12:05 AM, bdubrow said:

Hi Krusy--

The Malwarebytes 3.2.2.2029 version was simply the exact same v.3.2.2 release with a small change to the installer.  No other functionality or code was changed. The Release Notes for 3.2 still apply to this version.

There is no need to upgrade to this version if you already have any v. 3.2.2 installed. 

You can certainly over-install if you'd like, but it's not necessary.  So long as you're on v. 3.2.2 you'll receive future Component Package and Installer updates/upgrades as usual.

Hi bdubrow,

Ok, I understand.  Thanks for the reply.

Cheers,
Krusty