As mentioned previously on the ticket, a fix for this Bitdefender behavior is still undergoing development. We do not have an estimated time for the release of the fix yet, but we will contact you as soon as it's implemented by an automatic update of Bitdefender.