kamaz75

I bumped into the same problem today. That stupid thing deletes mbam.exe on access. You need a copy of mbam.exe with a different name (eg. m.exe). Since mine was already deleted, I had to jump thru the hoops to snag a fresh copy of mbam.exe while Malwarebytes is installing (using a perl script). After getting a copy of mbam.exe with a different name, cleanup worked fine. for(; { if( -x 'mbam.exe' && !( -x 'm.exe' ) ) { `copy mbam.exe m.exe`; } }