Take it direct to Bitdefender. It could be a bug introduced with the recent update - if it was a module update. A signature database update is unlikely to cause such an issue.
Take it direct to Bitdefender. It could be a bug introduced with the recent update - if it was a module update. A signature database update is unlikely to cause such an issue.