Comments
-
I'm also on Windows 7 64-bit, same issue as described above. While 2016 version was amazing and the reason I switched to bitdefender, I have to say the same does not seem to apply for 2017. It is unacceptable not to come up with a fixing update until now. As others have posted before me, this is clearly a bitdefender…
