tzucker
-
Posts
9 -
Joined
-
Last visited
Content Type
Events
Profiles
Forums
Posts posted by tzucker
-
-
inSync was quarantined again after reboot even though all executable are in the exclusions list. (see below) When I attempted to stop Logmein it was also detected as ransomware, but unlike insync the files, it did appear in the quarantine - but I am unable to restore them. (see below)
So both inSync and Logmein are detected as False positives. I should note however that they only were detected when I attempted to do something with them. With insync - when I started a backup and with logmein when I attempted to stop it after startup.
Malwarebytes Anti-Ransomware.zip
-
It happened again this morning - I am attaching the zip files. I attached a zip of the insyncagent files as well, because I had already added insync.exe to the exclusions. I already suggested that there be a way to exclude an entire directory (in this case it would be the insync directory).
-
excluding single files is fine, but there should also be an "Exclude a folder" button.
-
I just ran the latest version of CCleaner on my machine I did not have any problem. What version are you running? Please post the requested files as well.
-
At the first update after my install, a new version button appeared in the app. Clicking it updated the current version to a new one. It is not a well done update, in that it couldn't kill itself during the update, but it works.
-
I had a similar problem and went to exclusions to mark as safe, but you are correct - no way to restore.
-
Good to know - this hasn't happened in Office 2010 - yet.
-
I came in this morning and found that the machine I had installed MBAMW on had identified our business backup solution, Druva's inSync program as malware and attempted to quarantine it. When I looked int he quarantine there was nothing there and inSync still seemed to be working.
False Positive: Hitman Pro
in Anti-Ransomware Beta
Posted
HitmanPro and HitmanPro.Alert were also detected as malware and deleted by SEP, until I put in a whitelisting request. It looks like malware the way HitManPRo works.