AFAIK MalwareBytes doesn't have a rescue CD product, and may be unsuitable (unsafe) for use in such environments.

It's been a while now, so my memory has lost the details, but what I remember was an issue where MalwareBytes would automatically "fix" some settings that broke bootability, and get this disasterously wrong when the expected drive letters didn't line up properly.

So if you'd integrated it into Bart, for example, which boots as drive X:, it may "fix" "incorrect" paths for key boot files by changing them from C: to X:. Then the next attempt to boot the hard drive falls on its butt.

Specifically, the filespec that was changed, was the Userinit.exe line in the registry. Whether it would be able to "see" that natively, I don't know, but as I'd normally wrap registry-aware (but not off-HD-boot-aware) apps in RunScanner, that would be a serious and very real risk.

I think with MalwareBytes, it's a case of "we don't have it, so you don't need it". Given that it's a free tool, and developing a Rescue CD solution is difficult, I'd say fair enough - but that puts them in second-tier status for me.