Hey all,
Couple things to address at it appears the issue @MajorHavoc is having is different from the one @russell.harris is encountering.
The first issue: If you notice the application resides in the time machine area of the the Mac, we’ve seen this issue before and its due to the way MacOS changes its file locations and information stored on the file while in the time machine. Our current in place methods don’t prevent it from showing as a False Positive. We do have a solution in the works, but in doing so we discovered an Apple MacOS bug that severely degrades performance of both the system and our application. Until that Apple MacOS bug is resolved we can’t implement what we consider to be the long term solution to Apple MRT False Positives. For now, your best bet is to allow the file and move forward, and I apologize for the annoyance of having to do that. But we are working to make sure this detection doesn’t happen in the future. Our Customer Support team might also have some other suggestions on how to mitigate the issue.
The second issue: Our Agent does currently support localized command line arguments to restore a file based on a SHA or MD5, the issue is that the console side has yet to be enabled yet. I believe they had an internal tooling that they needed to develop that was taking their capacity and time, but I can reach out to them and see what the current timeline is. We are seeing significantly less False Positives on MRT in the field since we implemented our stop gap solution, but clearly there are still some issue with that. As above, once our full solution is in place we expect to no longer see these False Positives pop up.
