Webbie1

We have been using the Enterprise version of Malwarebytes for a couple of years now, but just recently turned on the 30 day trial of the Anti Exploit product, which we will be adding to our agreement shortly. I have a user who is attempting to run a program that he's been using for years that is now being blocked by the anti exploit. When I find it in the console and try to allow it, I get the message that it cannot be excluded because the threat doesn't contain a valid payload checksum. From other posts like this, I understand that this is because it's being blocked before the checksum is

Hello. We have been using the Enterprise Malwarebytes for a couple of years now. We just turned on the 30 day free trial of the anti-exploit, which we will be adding on to our agreement shortly. I have a user that had a program blocked by the Anti Exploit (a valid program that he's been using for years), and I see it in the security logs for his PC in the console. When I click on the treat, I get the message saying the threat can't be excluded because it doesn't contain a valid payload checksum. I understand (from other threads) that this is because it's being blocked before a checksum ca

Thanks Gonzo....we'll give that a shot. I figured that was the issue, but didn't know there was anything beyond the windows uninstall required. Warner

I'm a fairly new user of Malwarebytes Enterprise (a couple weeks installed with about 150 clients). Most of the clients look correct in the console, but some just refuse to update the "last scan time" column. If I click on one of the clients in question, then look at the system log I can see where I manually kicked off a quick scan and it completed (and when I do this, the client's status color changes to blue, indicating that it is scanning). So the question is, why do these clients NOT show the correct "last scan time" status? Part of me suspects that it's possible that these may have