New
#591
Thanks, and glad to hear that works for you.
Yea, I don't understand some of their reasoning and attitude ...
Guess I'm spoiled by the folks like you here in these forums
Thanks, and glad to hear that works for you.
Yea, I don't understand some of their reasoning and attitude ...
Guess I'm spoiled by the folks like you here in these forums
A simple reinstall will fix the issue, there is no need for a clean removal. No attitude meant, simply don't have time to go back and forth over and over on how to fix it and make everyone happy. If your solution works users are more than welcome to use it.
A simple update from the Scan window may fix the issue, no reinstall needed.
I believe you edited your post after I replied ...
Semantics aside, a simple MBAM install on top of a previous MBAM install will resolve the issue. No MBAM uninstall nor use of mbam-clean is necessary and the task should only take a few minutes. You may need to temporarily disable the MBAM self-protection module and then re-enable it when the install is completed.
The benefit being all your system's MBAM settings and logs are retained while the issue should have been completely resolved.
HTH :)
I'm still using 1.75.0001 until all these problems with the new version get ironed out (which is taking an absurd amount of time).
Did as others have done with updating the definitions and clicking Fix, rather than reinstalling. I didn't know at the time about the problem, but went to the Malwarebyte website after to see if others were having the same problem. I've shutdown and restarted several times to test and no further problems so far.