When I try to run the registered version of Flash Memory Toolkit (2.01 professional), if I enable the write test in the low-level benchmark (not available in the free version) the application is immediately terminated.
A Bitdefender popup appears declaring it was terminated because it was "deemed harmful by active virus control".
The tool is attempting to perform low-level block writes to a flash card as a part of a benchmark suite. Yes, a dangerous operation in the general sense. However, as a benchmark to profile device performance without filesystem overhead, it perfectly reasonable.
Is there a way to bypass, or get the false positive fixed?
I've tried temporarily disabling every aspect of Bitdefender that is available in expert mode, but there seems to be no way to disable this particular aspect of Bitdefender, short of uninstalling the product. I guess that's reasonable if the feature is trying to cover more sophisticated malware, but it makes the FPs considerably more annoying.
What I find highly disconcerting is that no logs were made about the issue anywhere I can find. When this problem first happened, I'd fired off a read followed by write benchmark, and found the app had stopped running mysteriously when I came back an hour later. I only found the problem after trying it again in write-only mode. This caused me to check the Bitdefender logs, but no mention of any problem was present in them.
This is troubling to me because if there was some form of genuine malware on my machine being terminated by AVC, I'd never know it unless I happened to be there watching. Clearly in a normal context, anything triggering the AVC should be considered one of the most grave dangers to the system. As a user, I'd really like to know if such a threat was found so I can perform a rescue-disc level scan. But strangely, bitdefender hides these issues, logging them seemingly nowhere.. or at least nowhere visible in the "view logs" section of the app.
Come on guys, Bitdefender makes really good products, I'd expect you to have enough common sense to use your logs to bring the most serious threats to the user's attention. That's just a bare minimum standard of AV behavior, and you really should be ashamed for not integrating this properly.