Autopilot Keeps Turning On After Pc Restart!
First of all I hope the Bitdefender Supports won't ignore the issue here. I've been using the Bitdefender in-app "Contact Support" feature, but at least a month has passed and I never got a response. Hope I'll get one here.
So the issue is that Bitdefender Autopilot keeps turning itself ON every time I start/restart my computer. I'm using the latest BitDefender Internet Security 2016. I have the same issue on several other notebooks where I have Bitdefender too.
In the past having the Profiles feature turned ON would keep Autopilot OFF for some time (even after OS start/restar) but it would still randomly turn ON. But right now no matter what I do, Autopilot keeps turning ON after every restart.
Is there any way to forefully turn Autopilot OFF for ever, or any other kind of fixes for this?
Comments
-
To turn off Auto Pilot click on the icon with the blue dot at the top of the GUI. Then click on General Settings. Finally turn on Paranoid mode.
0 -
I have the same problem - submitted a support ticket twice - NO RESPONSE!!!0 -
Hello,
/index.php?/profile/207215-john-van-niekerk/&do=hovercard" data-mentionid="207215" href="<___base_url___>/index.php?/profile/207215-john-van-niekerk/" rel="">@John van Niekerk the last ticket you submitted is from 2 months ago where the support team sent you a email and you never replied back. Please check your Spam folder or any active rules you may have setup.
To resolve the encountered issue I suggest upgrading to the 2017 version of the product for free.
http://www.bitdefender.com/support/upgrading-to-bitdefender-2017-on-my-computer-1711.html0 -
My apologies - I never received that reponse.
However - if you had a look at my attached files you would see that I am already using the 2017 version!!!!
So what now?
0 -
Hello,
Please let me know what build of Bitdefender you have installed on that machine and also the Windows version and build.0 -
Hello,
Please update your Windows 10 the latest version and do a fresh reinstall of the product.
Afterwards you should no longer encounter the reported issue.0
