I’ve paraphrased the information I got from MBAM support: ![]() The critical steps that I hadn’t done were restarting the computer (twice) AND the second set of steps below. This information is for me in case it happens again, and for anyone else who has a problem with a legitimate piece of software getting quarantined by MBAM. They were prompt in getting back to me, and with a solution that seems to have worked. We restored it from quarantine and made sure it was in the Allow List (it was), but it continued to get zapped by MBAM.Ī quick internet search didn’t yield any answers that matched our circumstances, so I reached out to the MBAM support team. ![]() Until last week, when MBAM decided it didn’t like this software (after years of playing nice together) and decided to quarantine it as soon as we tried to open and run the software. We’ve used Malwarebytes Anti-Malware (MBAM) for years and have never had a problem with it conflicting with a particular piece of software on one computer.
0 Comments
Leave a Reply. |