The June 1 overnight scan on a few computers in our office detected false positves in old files on drives that were not supposed to be scanned.
My BD scan detected Exploit.M###cel.Gen in a 5 year old excel file. BD blocked the file and now I can't open it. This is no big deal on this file, but how to I correct a false positive on a file I need to get to? Why is there no info about Exploit.M###cel.Gen on this site if BD detected it?
Why was BD scanning this server disk when it is not set to scan it? I double-checked the settings and BD was not supposed to scan the F:\ drive.
It looks like the scheduled scans did not actually run on May 31 either, so maybe it was a May 31 update that messed up the June 1 scans?
Has the update that caused these problems been corrected so that this won't happen again or are people going to be asking me every morning about these annoying errors?