Ergo, the 'Awake' popup and the system tray icon appear a little bit later. In Task Scheduler Bitdefender Agent is now scheduled to start 1 minute after boot. 'bdagent.exe' no longer starts automatically from the Run registry key. " Starting with the latest build version 20. An explanation of the behavior eventually became an article on their Web's support page.Ī snip from the most informative forum thread: 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. #Bitdefender 2017 free ransomware protection Patch#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. #Bitdefender 2017 free ransomware protection install#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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |