djzeratul

There's always ping pong

See you all on pornhub, goodnight

Updated, good to go. Everyone can breathe a sigh of relief.

Check my post earlier, someone at MBAM confirmed to BernardL that anti-expoit and anti-ransomware still works.

Yeah that sounds like one of those tech support scammer companies that RD into your box and "prove" you have some kind of infection then try to sell you a year of protection for $300 and then steal your credit card number.

That would be the most logical solution. That's how we always handled these kinds of problems with releases at my last place of employment. Roll back to last SVN tag and push the files back. However, the issue may be more complicated than this due to how the program handles the files... that, or their release crew isn't around to actually do a rollback, or they determined that a fix would be faster than to roll back.

Swarkman, let your mind be at ease...

Literally all it does is check to see if processes are applying encryption to files... lol. So why would it be broken by a definitions issue?

We don't know if it's the blinker fluid, it could clearly also be the muffler bearings...

Maybe someone left a bottle of Tres Comas tequila on the delete button

its 5:30 AM, engineers don't show up to work until like 8 or 9

Thanks for that... it looks like they changed everything around from 2.x to 3.x Sorry to have you go on a wild goose chase.

I don't... work here... lol. But the issue causing the bug is different, based on the testing we've done in this thread.

I don't particularly have time to spin up a VM with ransomware running to get empirical evidence, but based on that document I posted, it doesn't need definitions to work, so why would it be broken?

That's good to know, I hadn't tried doing the update. Thanks for posting that, it might save some people some time

Actually the defs files are a zip file with 2 executables that will install when you run them. just run the one that corresponds to your version (mbam2 for 2.x or mbam for 3.x)

https://support.malwarebytes.com/customer/en/portal/articles/2558649-malwarebytes-anti-ransomware-faq?b_id=14681 The anti-ransomware client is an agent that performs system-wide behavior monitoring and blocking of ransomware activity. It is a proactive and real-time protection which does not rely on signatures.

This is 100% a different issue than you were experiencing before, we've already isolated the issue and know what the problem is, and yes it affects EVERYONE using 3.x and they know this, and are working on it.

The ProgramData folder is hidden in windows, you'd likely have to paste that string into the location bar of explorer to get there

Your anti-ransomware protection will still work, it's just the web content filter and regular scan definitions that are not working.

Here's a link to last week's defs file if anyone needs it... this should get you at least more current than the last version release. https://data-cdn.mbamupdates.com/v1/tools/mbam-rules/data/mbam-rules-2017.05.11.zip

Still hoping that Enderstar saw my request and can check what the sizes are for 2.x

The other protections are heuristics based, so they don't use definitions files to run... Such as the Ransomware protection, that just checks to see if things are being encrypted by rogue processes...

Yes, and no, it's the same problem.

Enderstar I'm curious, can you post a screencap of your C:\ProgramData\Malwarebytes\MBAMService folder in detail view with filesize shown? thx.