Latest Version of Malwarebytes

Phone Man · 02 Mar 2017

wordsworth said:

Installed 1475 over 1469 and within two minutes being on the Internet had a bad pool header error just as when 3.0 was first released and that occurred on the old build computer and also the very first time I went on the Internet with 3.0 installed on the new computer build (new OS drive hardware as well).

Reinstalled 1469 after using mbclean and appears well again. I had to LOL when the BSOD occurred.

Never heard of 1475. the newest is:

Malwarebytes version: 3.0.6.1469
Component package version: 1.0.75

Jim

f14tomcat · 02 Mar 2017

Phone Man said:

Never heard of 1475. the newest is:

Malwarebytes version: 3.0.6.1469
Component package version: 1.0.75

Jim

Probably just a typo slip of the 1.0.75 and the 1469. Lots of numbers floating around in there. Need a scorecard! :)

Latest Version of Malwarebytes-2017-03-02_19h42_15.png

Phone Man · 02 Mar 2017

I agree. MB has confused us with these Component Package Updates and leaving the version the same.

Jim

wordsworth · 02 Mar 2017

I stand corrected as I'd thought that they went from 1469 to 1475 when I saw the 75 at the end. I fixed it in the original post.

wordsworth · 02 Mar 2017

Phone Man said:

I agree. MB has confused us with these Component Package Updates and leaving the version the same.

Jim

They've also confused me when they go from a version that works on this box to one that reverts to the behavior that the original 3.0 exhibited. Two steps forward and one step back is the method to their madness then. Sigh.

Phone Man · 02 Mar 2017

wordsworth said:

I stand corrected as I'd thought that they went from 1469 to 1475 when I saw the 75 at the end. I fixed it in the original post.

I thought that is what happen but I went looking for a 1475 version. Thought I missed something.

Jim

wordsworth · 02 Mar 2017

Yea, that's why I corrected it so no one would get confused and look for it at their site. Thanks for correcting that since as you say these version numbers can get confusing enough.

Phone Man · 02 Mar 2017

So what Component Package are you on now. 1.0.69 ??

Jim

f14tomcat · 02 Mar 2017

wordsworth said:

They've also confused me when they go from a version that works on this box to one that reverts to the behavior that the original 3.0 exhibited. Two steps forward and one step back is the method to their madness then. Sigh.

I don't mean to muddy your waters any more than they are, but it smells like there's a piece of the old 3.0, a driver or a .dll or something floating around. I know you've run their cleaner and all. Do you have Revo uninstaller? I recall having a real problem a while back with one of the 3.0 flavors, and I had to use Revo forced uninstall and still go back with Autoruns and look for anything that was even remotely MBAM. Found some Chameleon leftovers and a driver. Nailed everything I could find, looked thru Program Files & x86 & Program Data and deleted anything suspicious. Rebooted and installed. All fine.

wordsworth · 02 Mar 2017

Phone Man said:

So what Component Package are you on now. 1.0.69 ??

Jim