Hi:
Yes, this is issue is known to the developers on the
LONG list of issues, and has been reported by many users.
The vendor has to start "somewhere" with getting this new product out in the wild, but the current "beta" seems more like an "alpha", vis-a-vis performance, stability, UI/UX.
Unless you have a test box or a VM, you might want to stay with the current release build (2.2.1.1043) until things improve.
>>Note: there is no "mbam-clean" removal tool, yet. To uninstall, use the Windows program uninstall from the control panel, as noted
here.
And it would be nice if they would further clarify their marketing stance as an "AV replacement":
Is it a true AV, with full AV capability, in which case users would need to remove their other, 3rd-party AV (and disable WD under W10) to prevent conflicts/compatibility/performance issues?
Or is it a multi-faceted anti-malware tool that is and will remain compatible (as they ALSO
claim) with other, 3rd party AVs**?
Or is this a marketing strategy to vaguely claim that one can rely on it for sole protection and that one does not "need" an AV?
MM
(**Time will tell, if/when the 3rd-party AV vendors drop their compatibility efforts and begin to treat "Malwarebytes Malwarebytes" (a.k.a "MB3") as an incompatible, competitive product, rather than a complementary application.)