Better

A few things it might be worthwhile for some of you piling on to consider: Yeah, the issue might have shown up relatively quick on your system. Yours is one of several billion possible combinations of factors. Testing software for every possible contingency isn't easy. Nor is analyzing how an entire system behaves on an update before that entire system is running it. Something that doesn't cause major problems with a few thousand test clients may very well indeed indeed cause massive problems with several million live clients. And sometimes it's a problem you can't spot until the conditions under which it may occur exist. If we're smart, we'll use the collective numbers of people affected by this issue to nudge them along to taking the right actions, instead of crucifying them for the fact that sometimes stuff really does just go sideways once it gets in the field, no matter how much you tried to cover all the bases. The difficult truth is that it's not possible to see all the bases. What we should be insisting that the company learn from this is to gracefully cover for the possibility of a serious memory leak. They will never be able to completely eliminate the potential for every possible cause of one, but they can mitigate the risk. And that would be enough to make it a minor issue. As someone who's recently had to deal with having several hundred customers affected by an outage resulting from an attack against us, I can tell you with absolute certainty that these guys already all have their stomach tied in knots already. They don't need us piling on. For any still unable to keep MWB from launching: <Windows Key + R> services.msc <enter> Right-click Malwarebytes Service and select Properties. Change startup type to DISABLED. THEN kill the process. If you don't disable the service or change the recovery options, it will keep re-launching, because that's what it's supposed to do.