Like Intel's tick-tock model, 2017 feels like a tock.Ģ016 has the same 'issue' where the tray icon and Bitdefender Awake popup takes a minute (GASP!) to show up. This is not to disparage 2017 in any way. At the very least for three or four changelogs to roll by. With over 250 days remaining on my 3-PC license (good for 2017 too), I'm in no hurry and going to stick with IS 2016 for the foreseeable future. I expected it to show up in this final release.

NetDefender libraries, Nimbus, Gonzales and Nexus stuff.įor the short period I was running the TS beta I noticed the lack of 2016's IDS. For those who sadly still think in terms of 'Bitdefender engine,' these are mainly it.Īntispam core both at 2.15. Predictably, bdcore.dll hangs in at 11.0.1.12 where it's been forever for BD and everyone else. However, supporting engines remain at the same major version with some minor and patch increments up.Īvc3.sys from 3.11 to 3.12, for example, with the avcuf injectors being the same version as in 2016. It went smoothly and I took advantage of the option to forego the install scan.Īll the agent, console and client components have been bumped to version 21 from 20. I've got a trial IS installed on a Win10 test system.

For those control freaks, uh control geeks, not interested in either automated uninstall can download an official uninstaller from BD:Ĭomplete that process, install 2017, login to your Central account when prompted and licensing will then be migrated.

Instructs using your Bitdefender Central account where in step 6 'you will be required to uninstall BItdefender 2016 from your computer and you will be assisted to do that.'Ĭentral authentication persists throughout the process and licensing is migrated automatically. 09/24 edit to expand on jjc225's on-top-of upgrade (#2 below) and yet another alternative:īitdefender 2016 must first be uninstalled before installing 2017.

Bitdefender media autorun