Thank you for the response, and as if have stated, I understand its beta and not going to be perfect. I love the malwarebytes products and have been very happy with them in the past. I am also very happy that no files were encrypted and i was able to recover them, so its all good.
All i was indicating is that i submitted the requested logs/directories and heard nothing about them. It would be nice know if it was an actual infection or just a false positive, not to mention why the machine because unusable (though this would have been better info to know before the machine was rebuilt). I updated the blog in-case anyone else was having such issues and came across it.
You state that the beta program is designed to find bugs. Well, I either found an infection or a bug, but i just figured someone there would be interested in the fact that after the product found an "infection" (real or not) and was rebooted at its request, the machine became non functional. Production machine or not, I don't think that this behavior was by design, correct? If the behavior is by design, like some kind of lock down mode, it would be nice to have that info going in, maybe have some indication of what is going on when it happens, and maybe a procedure to bring it out of that mode.
I hope the logs i provided will help to avoid such issues in the future, especially when the product comes out of beta.
thank you for your time!