![]() Not to mention that mbam.exe itself was detected and quarantined. How did a definition get out that detected so many files incorrectly across the system? I could understand if some random third-party software gets detected as a false positive but when you are detecting and quarantining key Windows files across all version, something got missed. I know the war between malware and security software definitions are an ongoing battle and it’s hard to criticize but I think this event shows that Malwarebytes at the time had little to no quality assurance in place. ![]() ![]() Once more, I apologize that this occurred and hopefully we will be able to get everyone’s systems in proper working order once more without too much trouble. We have also taken extensive measures to ensure that a false positive like this never happens again. Other support options in the thread include using the Malwarebytes Anti-Malware FP Fix Tool for Enterprise customers or contacting home user support and business user support. You may also need to download and install VB 6.0 Run-Time service pack 6, as those files were quarantined and are a prerequisite to running Malwarebytes. Go into the quarantine and restore all of the items quarantined incorrectly. ![]() ![]() Install Malwarebytes Anti-Malware (because Malwarebytes itself was detected as a false positive).Malwarebytes staff have another thread providing steps to fix the problem. Some of those affected by the false positive reported their plight and the files detected in this thread on the Malwarebytes forums. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |