Latest Version of Malwarebytes

Brink said:

I get this now with 3.4.5 to not be able to turn on "Exploit Protection".

Attachment 182831 Attachment 182832

Strange. It's on for me.

Brink said:

I get this now with 3.4.5 to not be able to turn on "Exploit Protection".

Attachment 182831 Attachment 182832

There are more than a few people experiencing abnormalities with MB and IP builds, particularly after taking an upgrade via WU.

Have you used the MB Clean tool to uninstall / reboot / install it again, @Brink?

Hey @johngalst,

I just finished trying it without success.

Brink said:

Hey @johngalst,

I just finished trying it without success.

Odd. I know the f14tomcat had a similar issue a couple of builds back, and it took it a while before it fixed itself.

To recap, you're not running with ßeta components enabled in MB, correct?

mrgeek said:

Brink; no problem here with anti-exploit setting. Don't know if it will help but I update inside the program itself vs downloading and installing.

In-app update is not finding an update to install for me. I've downloaded the new version manually, but may hold off on upgrading until I see what happens with @Brink's issue.

Correct, beta settings turned on.

Here's my current versions info:

Brink said:

Correct, beta settings turned on.

Here's my current versions info:

Same as yours Shawn, but my Exploit Protection is on. I had your same issue few months back, only a clean install worked to fix it. I know you already did that Shawn. I made sure there was no trace of MB anywhere, including registry too. Try reporting it to the folks at MB, maybe there is a fix coming out soon.
This problem drove me nuts too Shawn.....

Hopefully, it'll get sorted soon.

Brink said:

I get this now with 3.4.5 to not be able to turn on "Exploit Protection".

Attachment 182831 Attachment 182832

@Brink

Shawn, is working just fine on FCU, but I just booted up Insider 17133 and updated it in-place. I now have the exact scenario you do. Can't even click on it. Even after restart. Doesn't wait to turn itself off like it has in the past, it's just dead from the git-go.