April 13, 2015

Russian anti-virus company Doctor Web has updated SpIDer Agent for Windows (10.0.7.201504060), Dr.Web Control Service (10.0.7.03310), Dr.Web Scanner SE (9.1.3.201504030), Dr.Web Anti-rootkit API (10.0.5.201503250), Dr.Web Scanning Engine (10.0.5.201503260), the component Dr.Web SysInfo (10.0.3.201503250), Dr.Web Net filtering service (10.0.5.04010), the firewall (10.0.2.03230) and the configuration scripts (10.0.1.03240) in the following products: Dr.Web Security Space and Dr.Web Anti-virus 10.0, Dr.Web Desktop Security Suite which supports centralised administration (part of Dr.Web Enterprise Security Suite 10.0), and Dr.Web 10.0 for Windows Servers (the Dr.Web Net filtering service and the firewall updates aren't applicable for this product). The scanning service and configuration scripts have also been updated in Dr.Web for MS Exchange. The update delivers new features and resolves known issues.

In particular, it resolves a SpIDer Agent for Windows issue involving files originating in a system partition root directory being restored from the quarantine into the folder System32. The information table background issue in the Quarantine manager has been eliminated.

The routine for gathering system information in Dr.Web SysInfo has been upgraded.

The firewall had issues that could cause it to terminate abnormally when interacting with other applications resolved.

A configuration script error involving the installer not saving user-defined Dr.Web Cloud operational settings has been corrected.

Also corrected was the Dr.Web Enterprise Security Suite scanner defect involving an incorrect value being displayed for the option to restrict access to system resources if the settings had been changed via the Dr.Web Control Center. The update also alters the traffic-filtering routines used by the Office Control. Previously access was blocked for all system processes, which could lead to Windows Update and Dr.Web Control Center connection errors in cases when no active user accounts were found on the computer. Now these issues have been resolved, and network access is only blocked for processes initiated under the current user account.

The update will be performed automatically; however, a system reboot will be required.