I have noticed the same problem. I have also noted that on the machines running Bitdefender 2013 this is an issue but on the machines running 2012 it is not. I have stumbled on a work around for...