Advance Notice: Update for AV Defender scheduled Thursday July 22nd for Fresh Installs/Upgrades

Please be advised we will be pushing an update to activated N-central servers as of Thursday July 22nd for AV Defender ( Releasing the ability for Fresh Installs and Upgrades for . Please note the ability to Update has already been made available.

AV Defender Version

The AV Defender is available for Windows modern Operating Systems, designed for Windows 7/Windows Server 2008R2 and higher.


This is the last release on the version 6.6 series. The next AV Defender release will be using the new version 7 series. There is two key pieces of information to be aware of moving forward:

First, Bitdefender is only making the update/upgrade capability to version 7 available to those on

Secondly, we would also like to advise you that version 7 of AV Defender will no longer be eligible for Windows 7 installations that have not secured the Extended Security Updates. Microsoft is changing the way executables can be signed, it will no longer be possible to be signed with SHA1. Any Windows 7 installations that have not applied SP1 should consider the following Microsoft articles:



Devices without these in place will NOT be able to update/upgrade or install to any subsequent versions of AV Defender.


  • Added improvements to the Firewall feature on Widows 10 OS. Upon installation it will no longer deactivate Windows Firewall, leaving control to Windows Security Center.

The following issues were fixed in this build:

  • In some instances, websites with untrusted certificates were being blocked and not providing the “Accept risks and continue” option, this option has been restored.
  • The Content Control module failed to report the web category of a blocked website, in the Blocked Websites report, this has now been restored.
  • The Firewall Events timeline from the local interface displayed wrong messages for incoming and outgoing connections, this issue has been corrected.
  • Firewall module addressed an issue where blockPortScans remained active even when the Firewall module was enabled.
  • Firewall module addressed an issue where traffic was received from an unknown profile.
  • The Firewall driver generated a memory leak in EPSecurityService on Windows machines, this issue has now been resolved
  • Fixed an issue with the On-Access Scanning feature, where users without administrative rights could restore a quarantined file. These users are now prompted to enter their username and password when using the Restore button.
  • In a certain scenario, a previously whitelisted website through Security Content whitelist could not be blocked via Web Traffic Scan rules.
  • Firewall module addressed an issue where after connecting to a wireless network, the user received the “connection to a wireless network has been established” notification even when the Firewall module was turned off.
  • Disk Encryption module addressed an issue where in certain scenarios, the Disk Encryption module maintained the Bitlocker feature suspended state.
  • Fixed an incompatibility with Cisco Advanced Malware Protection (AMP) for Endpoints that caused crashes of File Explorer processes and overall performance issues on Windows 7 machines.
  • Fixed an issue where Product update and Security Content update remained in a continuous “Updating” state.
  • In a certain scenario, due to a missing cleanup mechanism, continuous crash dumps of the Product piled up and used almost all available disk space on endpoints, eventually leading the system to crash as well.

Updating to this Release
The AV Defender update can be scheduled at an appropriate time by adding a maintenance window to your devices. Updating involves an incremental update of components or modules without the need to remove protection. The device will be rebooted after the update if the maintenance window allows AV Defender Reboots. A reboot may be required based on Installation Status. If you do not want updates or reboots to proceed automatically, you can disable them by removing the appropriate maintenance windows from the device or rule.


This entry was posted in N-central. Bookmark the permalink.