Latest Version of Malwarebytes

Brink · 30 Mar 2017

Thank you Jim. First post updated. :)

swarfega · 30 Mar 2017

OldMike65 said:

Interesting, by looking at your spec's we have the exact same Intel chip, and same MB ....I am running Windows build 14393.969 thou. Not running any insider build, and MB runs fine here. Only thing I do is run MB manually, I don't start it up at boot.

It's nice to find someone running a broadly similar specced machine to mine. I am running build 14393.969. Like you I run Malwarebytes and SuperAntiSpyware (as on demand). Machine two is my old machine before I got this new one last December.

OldMike65 · 30 Mar 2017

swarfega said:

It's nice to find someone running a broadly similar specced machine to mine. I am running build 14393.969. Like you I run Malwarebytes and SuperAntiSpyware (as on demand). Machine two is my old machine before I got this new one last December.

I also run SuperAntiSpyware too.....on demand, same as you.....(lifetime license, same for MB)

Phone Man · 30 Mar 2017

Brink said:

Thank you Jim. First post updated. :)

There is an error on the first page and was an error on the MB site.

The Component Package is 1.0.96 and not 1.0.1096.

Jim

OldMike65 · 30 Mar 2017

Phone Man said:

There is an error on the first page and was an error on the MB site.

The Component Package is 1.0.96 and not 1.0.1096.

Jim

Thanks for all this new info today JIM

TDOZ · 01 Apr 2017

Just a quick heads-up about a minor bug in this latest version - an in-line read attempt of a PDF document atachment email in the Outlook (2013, and possibly 2016 as well) local client, will get an error window showing that the Adobe Reader will not open in Protected Mode. The workaround is to either click on the "open without protected mode" button, or detach the PDF before reading (or exit MB3 for a short while, until you are done with your PDF's). I posted this already on the MWB forum, so maybe there will be an update at some point.

ondablade · 08 Apr 2017

Hi all. I ran into the usual V3 problem with real time and web protection switching off a couple of days after installation - the problem returned again even with the very latest V3.0.6.1469/1.0.96/update package V1.0.1658 edition installed as instructed by MB here: Malwarebytes 3.0.6.1469 Premim Bugs - Fix Schedule, Risks, Strategy? - - Windows 10 Forums

It now (after a day or so) seems to have sorted itself out. I did nothing, but the update package version has (unless I'm losing it) somehow changed to V 1.0.1688

Does anybody have any idea what might be happening? Both in terms of why so many issues over so long, and how it fixed itself ?

Thanks

OldMike65 · 08 Apr 2017

MalwareBytes will update your "update package" itself along with it's definition files automatically, mine is the same as yours
V 1.0.1688. So your not losing it. :)

ondablade · 09 Apr 2017

Ta Mike. The very good news is that it's still running fine....

ian

Phone Man · 12 Apr 2017

New Component Package 1.0.103 released today to fix problem with MB 3 disables Windows Defender in Creators Update.

The initial workaround was to set MB 3 option for Windows Action Center to never.

CP update will be pushed through MB updates.

Latest Version of Malwarebytes-mb-action-center.jpg

https://forums.malwarebytes.com/topi...atest-version/