Opinions on Mbam's Anti Exploit program.

Thanks for the clarification.

I suspect that you are both running different versions of MBAE (1.05 versus 1.06?) and/or different versions of Windows OS.
(I am running 1.05 Free under Win7/64 and my "feature" activate button is grayed out, as LF reported.)
As Win10 is not yet released, some inconsistent behavior is to be expected.
Perhaps it is a bug on that OS platform, or related to the VM environment?

However, this forum here is not the best place to troubleshoot.
Doing so requires at least some basic system logs, as requested here.
Then, it would be best to post those logs in a forum topic in the MBAE support forum here.
That's really the only way the product team can research, replicate, identify and fix bugs.

In any event, it still stands that one cannot use/activate a "premium" feature/shield until the program has been activated with a valid, paid license ID and key.

Thank you,

The version is displayed under the "General" tab, at least in 1.05 Free.

I don't know why you are seeing the premium shields "activate" tab enabled in 1.06 Free under Win 10 TP in a VM.
It could be the expected behavior for 1.06 or it could be a bug.

Parsing that out would necessitate reporting what you're seeing to the product team, as suggested in my previous reply.

Thank you,

DavidE said:

I'd guess the activate shield button is working correctly in 1.06.
The message i get clearly explains what is needed to activate a shield.
With the button grayed out, the user might not know why, now they will know what is needed to activate a shield ...
It's probably an undocumented change they made in 1.06 ???

I suspect it is this one:

Added Premium notifications in Free/Trial builds.
https://forums.malwarebytes.org/inde...8/#entry952209

I have not yet received 1.06 on my boxes via the auto-updater, and I do not have a test box or VM.
So I cannot confirm that just yet.

But you are welcome to post over at the MBAE product forum, and I am sure @pbust would be able to provide a fast "yes" or "no" answer.

Thank you,

Thanks David!

Looks like it wants me to buy a licence to activate it for Comodo Dragon ....or mayb its already activated? Whats the padlocks meaning?

Mmm....I think its already active? The GUI is a bit confusing....too many activate buttons.

DavidE said:

Lady Fitzgerald said:

I have several of the programs listed by MBAE free as being protected (IE, Adobe Acrobat, M$ Word, M$ Excel, M$ PowerPoint, WMP, and VLC Player) but the General tab shows only one Shielded application; according to the logs, that is IE. The option to activate a shield is grayed out. Is this normal?

I just installed MBAE free on a WTP Build 10049 VM.
I can click on activate and get a message showing the Premium version is needed.

Attachment 354839

Curious. I can right click, left click, and wheel click on it and it just sets there and laughs at me.

Golden said:

Thanks David!

Looks like it wants me to buy a licence to activate it for Comodo Dragon ....or mayb its already activated? Whats the padlocks meaning?

Mmm....I think its already active? The GUI is a bit confusing....too many activate buttons.

It's basically a "toggle".
If you see a "locked" padlock, then that particular shield *is* activated.
So, only the "Deactivate" button is enabled.

If you click "Deactivate" for that shield, the padlock should open, meaning that the particular shield is not active.
If you then click the "Activate" button, the padlock should "lock, and the "Deactivate" button should now be enabled.

SO, it appears that Comodo Dragon may, in fact, be included in the list of browsers shielded by 1.06 Free.
I was not aware of that and I stand corrected for my original statement where I said I thought it was NOT.
I do recall that the product team DID solicit suggestions from users about browsers a while back.
So it seems that this may have been one that was added to default list for version 1.06 Free.

(I have not yet been offered 1.06 via the auto-updater on my boxes, and have neither a test box nor a VM on which to test it.)

Thank you,