Latest Version of Malwarebytes

[A Guy]

Just curious, did you make any changes to the default settings in Avast, Malwarebytes and/or EMET?
Did you set mutual exclusions between Avast and Malwarebytes 3.0?


Thanks,
MM

I have not made any changes or exclusions. Often when MBAE was a stand alone program, I would have to disable certain EMET browser protections when MBAE updated. In changing to V3, I did not have to alter EMET.

I had no issue changing EMET as MBAE updated, assuming MBAE was now handling those protections. This leaves me with the rest of EMETs settings.

But Avast and MBAM 3 I have changed nothing to allow them to coexist. A Guy

 

[Seffrid]

From what I have read on this forum and other places it seem to me the new release is more of a beta version and not ready for prime time.

Jack

That's why they haven't released if though the automatic update yet.

That would be fair enough but for the fact that they have withdrawn versions 1.75 and 2.x from sale so that if you want to find the downloads for those it's extremely difficult (other than with the aid of MM's links of course), and separate forum sections for those versions have been removed. If you click on the dashboard link to any aspect of the earlier versions it takes you straight to version 3.

All of that is happening while there are still 6 months to go with support for version 2.x (and with definition updates still happening for version 1.75). So they have switched all promotion and discussion to version 3 at a time when it is seemingly not in a fit condition to be out of beta.

As discussed earlier in this topic, I had still been running version 1.75 on both my home Windows 7 machines without any issues but have now updated one of them to version 2.x without any problems as yet, although it's my secondary machine and not used daily.

On my primary machine, however, while still for the moment using version 1.75 without issue I have started getting problems with MBAE. As someone else has posted on the Malwarebytes forum it throws up an error message after the machine has been switched on for a few minutes saying MBAE was taking too long to start and the machine should be rebooted to fix it. That worked the one time I did reboot, but I've had the same problem again today.

It concerns me that Malwarebytes may have bitten off more than they can chew with all these products they're trying to muscle in on and that by combining them all into one all-encompassing product they are creating more problems than they're solving and, moreover, forcing those problems onto long-term users well before the new product is ready while already abandoning the old tried and tested products while many users are still reliant on them.

As a free user I can't in one sense complain, but then the way to convert free users into paying customers is surely to impress them with the quality of the products and the ongoing support provided for them, not to force people into testing a new product that is still in beta in all but name while dumping the old products that those people are still happily using.

Malwarebytes seem to be heading down a different road all of a sudden, and I'm not sure it's one that a lot of their established users will choose to follow.

 

[MoxieMomma]

Just curious, did you make any changes to the default settings in Avast, Malwarebytes and/or EMET?
Did you set mutual exclusions between Avast and Malwarebytes 3.0?


Thanks,
MM

I have not made any changes or exclusions. Often when MBAE was a stand alone program, I would have to disable certain EMET browser protections when MBAE updated. In changing to V3, I did not have to alter EMET.

I had no issue changing EMET as MBAE updated, assuming MBAE was now handling those protections. This leaves me with the rest of EMETs settings.

But Avast and MBAM 3 I have changed nothing to allow them to coexist. A Guy

Interesting, especially re: EMET.
Running it with MBAE was never supported and "tweaks" were needed to get the two programs to co-exist. As of just a few weeks ago:

Enhanced Mitigation Experience Toolkit (EMET). Both EMET and MBAE are exploit mitigation products that apply similar protections and apply similar API hooking & techniques. However MBAE provides more comprehensive protection due to its Layer0 and Layer3 protections. More information here. It is not recommended to run MBAE and EMET together. Some users have reportedly managed to run both together by tweaking the EMET techniques, but this is not a Malwarebytes officially supported configuration.

And the anti-exploit portion of Malwarebytes 3.0 has its own, new issues.

But if it works for you, then that's good.

Thanks for reporting your results.

MM

MM

 

[MoxieMomma]

On my primary machine, however, while still for the moment using version 1.75 without issue I have started getting problems with MBAE. As someone else has posted on the Malwarebytes forum it throws up an error message after the machine has been switched on for a few minutes saying MBAE was taking too long to start and the machine should be rebooted to fix it. That worked the one time I did reboot, but I've had the same problem again today.

There's no credible reason to be running version 1.75 -- it has been outdated since March 2014.

As was explained HERE and HERE, the fact that version 1.75 may still be getting database updates for a few more months hardly matters. It lacks several important features, such as anti-rootkit scanning, as well as many, many improvements to the scanning engines and real-time protection capabilities under the hood (such as heuristic detection). Running version 1.75 now - even with current "databases" - is a false sense of security. It may be better than nothing at all, but it's not nearly as robust as version 2.x.

So I cannot fault Malwarebytes for removing their official download links to a program that is nearly 3 years out of date.
As for version 2.2.1.1043, at least for now, either of these download links ought to work:

https://downloads.malwarebytes.com/file/mbam_2x
https://data-cdn.mbamupdates.com/web/mbam-setup-2.2.1.1043.exe

It's up to you, but I strongly suggest that you upgrade your 1.75 installation to 2.2.1.1043.
If you need help with it on that system, you will be out of luck, once support for 2.2.1.1043 ends.
And the transition from 1.75 to version 3.x will be more of a UI/UX shock than going from 2.x to 3.x.
Support articles for version 2.x are posted HERE.

You may try an "on-top" upgrade, but a "clean" upgrade may be more reliable.
The "clean" reinstall instructions are HERE -- the only difference from the posted steps is that you would use the links I just provided to obtain the 2.2.1.1043 installer, rather than using the 3.x installer.

• Be sure you have your license info handy before you start - you will need it to activate the Premium features
• Be sure to reboot when prompted by the removal tool - important!
• It's a good idea to reboot again after installation of 2.2.1.1043

As for the rest of your comments, I agree with much of what was said about the company's current direction and tactics. Time will tell if there will be a favorable outcome, either for the company or for its customers.



Cheers,
MM

 

[Seffrid]

Thanks MM, as I indicated I have already upgraded to version 2.x on my secondary machine. If that continues to run ok then I shall upgrade the primary machine as well. That's my method with all updates and upgrades, no way will I ever apply anything to both machines together!

I'll then see how things go come June.

Meanwhile I'll also continue to run MBAE as and when it works! I suspect, however, that they're only working on that within version 3 so may not fix the current issue on the freestanding version.

 

[MoxieMomma]

Thanks MM, as I indicated I have already upgraded to version 2.x on my secondary machine. If that continues to run ok then I shall upgrade the primary machine as well. That's my method with all updates and upgrades, no way will I ever apply anything to both machines together!

As you wish.

I'll then see how things go come June.

Indeed.

Meanwhile I'll also continue to run MBAE as and when it works! I suspect, however, that they're only working on that within version 3 so may not fix the current issue on the freestanding version.

Actually, no, that's backwards.
The standalone version of MBAE has been moved to "perpetual beta".
That means that it's the standalone, "beta" version that is currently being "worked on".
Changes to that standalone version will then eventually be incorporated into the anti-exploit component of Malwarebytes 3.0.
In fact, some Win10 Insider users running MB3 are being advised to disable the AE piece in MB3 and to install the current standalone until the built-in AE module is patched next month.

Without knowing your current MBAE version (Free or Premium) or build (current "release" build of MBAE is 1.09.1.1291) or more about the system in question (e.g. other real-time security applications, etc.), it's hard to troubleshoot.
Unfortunately, the MBAE logs are not particularly end-user friendly.
So I cannot really provide much help, other than to look at some FRST logs.
(AND this thread pertains to MBAM, not to MBAE.)

If you need help troubleshooting MBAE, your best bet would probably be to start with THESE SUGGESTIONS and then to post a new topic in the MBAE-BETA forum for expert help from the MBAE team.

Cheers,
MM

 

[DavidE]

Malwarebytes 3.0.6 Release Preview - Now Available! - Malwarebytes 3.0 - Malwarebytes Forums

 

[Brink]

Thank you David. First post updated.

 

[Layback Bear]

From
Malwarebytes 3.0.6 Release Preview - Now Available! - Malwarebytes 3.0 - Malwarebytes Forums

We've addressed over a 100 items in this release, so that's too many to list here, but we tried to get most of the top issues people were seeing.

How in the hell did Malwarebytes ever release 3.0 with this many problems??

Could it be that Malwarebytes did it like Microsoft did with W-10?
Both seemed to put their product out for the rest of the world to do the needed testing.
Obviously it's cheaper letting the world do the R&D rather that doing the needed R&D in house.

I would suggest to both companies that their reputation does have a value and these types of methods are not good for such reputations.

Just my opinion.

Jack

 

[Lady Fitzgerald]

From
Malwarebytes 3.0.6 Release Preview - Now Available! - Malwarebytes 3.0 - Malwarebytes Forums



How in the hell did Malwarebytes ever release 3.0 with this many problems??

Could it be that Malwarebytes did it like Microsoft did with W-10?
Both seemed to put their product out for the rest of the world to do the needed testing.
Obviously it's cheaper letting the world do the R&D rather that doing the needed R&D in house.

I would suggest to both companies that their reputation does have a value and these types of methods are not good for such reputations.

Just my opinion.

Jack

It's not just your opinion, Jack!

 

[jadinolf]

From
Malwarebytes 3.0.6 Release Preview - Now Available! - Malwarebytes 3.0 - Malwarebytes Forums

We've addressed over a 100 items in this release, so that's too many to list here, but we tried to get most of the top issues people were seeing.

How in the hell did Malwarebytes ever release 3.0 with this many problems??

Could it be that Malwarebytes did it like Microsoft did with W-10?
Both seemed to put their product out for the rest of the world to do the needed testing.
Obviously it's cheaper letting the world do the R&D rather that doing the needed R&D in house.

I would suggest to both companies that their reputation does have a value and these types of methods are not good for such reputations.

Just my opinion.

Jack

In my opinion it is STILL in beta.

Sure didn't fix the problems I had.

I think I will wait until July and if it doesn't work by then, I will tear up my licenses.

 

[Seffrid]

My personal view was always that Version 2 was in beta in all but name for at least a year after launch, probably longer. It looks like Version 3 will be no different.

 

[kado897]

I just updated mine. It upgraded smoothly and seems to be solid.

 

[jadinolf]

I just updated mine. It upgraded smoothly and seems to be solid.

Here's what I'm getting.

 

[kado897]

Here's what I'm getting.

All my protections are on. Have you tried rebooting?

 

[jadinolf]

All my protections are on. Have you tried rebooting?

Yes, but a little later it is turned off again.

 

[kado897]

Yes, but a little later it is turned off again.

Worth reporting on the MB forum?

 

[ThrashZone]

Hi,
Yep anyone with issues and thinking of trashing an old pro license you can give it to me if you don't want to roll back to 2....1043

 

[Callender]

I haven't used MBAM since all those v2.x releases kept giving BSOD's on my machine. Anyway new version of MBAM is released. It's a preview with fixes.

Fixed issue where ‘Real-Time Protection turned off’ notifications would display incorrectly on initial startup

Malwarebytes 3.0.6 Release Preview - Now Available! - Malwarebytes 3.0 - Malwarebytes Forums

I see it was already posted.

 

[Alexey2912]

Hi,

I purchased a subscription for 2 years, found it to be buggy, web protection won't start, reboot errors displays, many technical support emails, promised they would fix.

But couldn't, canceled by subscription.

IMO, MBAM 2.XX was far better, this is crap.

Thanks.