Search the Community
Showing results for tags 'pacman'.
I was installing some things in msys2 and hadn't thought to exclude my dev tools directory. MB incorrectly identified Pacman.exe as ransomware, and removed all rights from the file. I have added an exclusion, but is there a way to reverse the actions of MB, i.e. make pacman accessible? Deleting it wouldnt' have been worse than this. And is there a log of the anti-ransomware's actions? It took me a while to figure out exactly what it had done, as the alert was not logged. I've received alerts before on things that were not ransomware, and now I'm worried about what it did in the past, as I was never able to find this information even then. It tells me real-time detections 350, and that includes websites it blocks, but without a log of those actions, that number is pretty worthless. Version infromation Malwarebytes: 18.104.22.1683 Component Package: 1.0.262 Update Package: 1.0.4232
Hello MalwareBytes. For the past several days, MalwareBytes has repeatedly identified my installation and upgrading of MSYS2 (specifically pacman.exe) as ransomware. I've had the unusual problem, however, of MalwareBytes causing pacman.exe to ignore my administrator rights completely, and being unable to quarantine or scan the file until a restart is performed. Malwarebytes Anti-Malware does not identify the file as a threat, only MalwareBytes Anti-Rootkit after launching pacman.exe, but does not record any such notification in the logs. If I can trigger the notification again, I will attach a screen shot.