Comments
-
It appears to me that this situation may not be a bitdefender issue, or is at least easily fixed (at least, it was for me...) I received the exact same problem when I opened Outlook after I had run a bitdefender scan, and I "fixed" the problem by closing the Outlook application that received this error, and reopening it.…
