Is this problem fixed in this/these release(s) ?
I am refering to this topic https://forum.avast.com/index.php?topic=146135.0
And the last post in that topic https://forum.avast.com/index.php?topic=146135.msg1077974#msg1077974
I can’t Beta test myself right now 
Greetz, Red.
I believe this bug has been resolved (Can’t find info on release history though). The MBAM version at the time was v. 2.1000beta and we know that Avast devs were working on the fix in April I believe.
Unfortunately, I am not beta testing either, however from my readings, I am not seeing any reports of this issue recently or anyone on the MBAM forum that I’ve noticed. 
Thank you for the input
But at the moment I am (re-)installing my Win 7 x64 system from scratch, and the problem is definitely not resolved with the latest stable Avast! 2014.9.0.2018 - and MBAM 2.02.1012 ( professional ) build.
Greetz, Red.
Thanks, Noted. 