Please click here to see the most recent update.
UPDATE 4/28/17 11:45 a.m. MNT: We have 0 calls in queue on our phone line, and are working through about 80 tickets related to the False Positive repair utility. A good portion of those are simply awaiting customer verification.
Please note, the utility was built to address only this specific false positive issue. It will be deactivated in the future.
If applications are operating normally on your systems, you do not need to implement the utility.
If you haven’t yet submitted a support ticket and you need the repair utility, please do so here. Include your phone number as well with the support ticket.
Best answer by freydrewView original
NOT GOOD ENOUGH.
A fix is an automatic rollback.
Figure it out.
Then I attempted to restore the files for the individual endpoints that ran into issues but that has not worked. Does this typically take a while to restore or am I perhaps doing something incorrectly? It has been about an hour since I restored.
Thank you for your hard work getting this back to normal.
As you can imagine, we are all working hard at finding the best resolution for this issue.
However what about restoring files when the listed MD5 method is not working?
We are facing having to restore to previous day and lose entire day's work for multiple clients. Anyone else seeing a better way to address this problem on a global scale to recover/restore files.
This is costing us lots of time and resources to deal with. Could use some positive fixes.