Please be advised we will be publishing an update for Managed Antivirus MAV-BD v6.6.7.106 available for all Modern Windows Operating Systems (Windows 7+/Windows Server 2008 R2+) Tuesday February 19th. The new Bitdefender engine version should not require any reboot. If a reboot should be needed, it will be displayed with the RMM dashboard. Ensure the delay and reboot settings in your policies are set accordingly for your customers.

Enhancements

• Scanning of packed files is enabled for all types of scanning.
• Improved messages for Advanced Threat Control detection events.
• Added exclusions for System Center Configuration Manager 2012 (SCCM 2012) following Microsoft recommendations.
• Added support for Windows 10 October 2018 Update (Redstone 5 / version 1809) and Windows Server 2019.

The following issues were fixed in this build:

• The user interface did not specify the threat name in case of infected files downloaded from the Internet.
• Central Quarantine did not work properly with Distributed File System (DFS) network shares.
• Fixed an issue where deployment failed with error code 1627 instead of error code 31 when third-party security software could not be removed.
• Fixed an issue with Advanced Threat Control slowing down the upload of Microsoft Office documents to a remote shared location.
• Fixed an issue with Advanced Threat Control blocking Exchequer and MYOB applications.
• Fixed an issue where Support Tool recursively collected unnecessary files from the temp folder, causing low disk space.
• Fixed an issue with Advanced Threat Control slowing down the upload of Microsoft Office documents to a remote shared location.
• Fixed a particular issue causing critical error (BSOD) when accessing items on an external shared drive.
• Fixed a particular issue causing critical error (BSOD) on Windows Server 2012.
• Fixed an issue with unquoted uninstall path.
• Fixed an incompatibility issue with MsSenseS.exe that was causing the product folder bdcore_tmp to grow in size during on-demand scanning, until the disk space was consumed.
• Fixed an issue that caused Bitdefender Endpoint Protected Service to stop in particular conditions.
• Fixed an issue with EPSecurityService causing up to 30% CPU usage on some endpoints running Windows 10 Enterprise.
• Fixed an issue that caused explorer.exe system errors with the message “txmlutil.dll is missing” on some servers.

Delaying Engine Upgrades

• MAV-BD Engine upgrades can be delayed by up to 10 days in the Managed Antivirus protection policy. Upgrades can also be delayed for weekends and evening hours.  Please refer to RMM’s help file for more detail on this feature.

Handling MAV-BD Reboots

• Reboots can be automatically enabled for the upgrade process by selecting an option in the MAV policy under the “Installation Settings” tab. Automatic reboots occur within 5 minutes of taking the update. Please ensure this option is disabled if you do not want your end user machine to automatically reboot. If the automatic reboot option is not enabled, the reboot will be displayed as a blue dot within the North Pane of the RMM Dashboard, indicating that the machine needs a reboot to complete the installation.  Reboot the machine at your earliest convenience.
• 

Determining the version on a device:

The version of the MAV agent, as well as the MAV engine version, can be seen in 2 places – by looking at the Managed Antivirus Check (Bitdefender), or by running the Managed Antivirus Protection Report.

To see the version of the agent within the MAV check, navigate to the South Pane of the device and find the Managed Antivirus Check – Bitdefender and select the “More Information” link.  To see across devices, run the Managed Antivirus Protection Report under Reports > Managed Antivirus > Antivirus Protection Report. Ensure that the Agent Version and Engine Version columns are selected from the Column drop down.