September 29, 2014

Doctor Web has updated SpIDer Agent for Windows (9.1.5.201409160), Dr.Web Control Service (9.1.5.09250), Dr.Web Updater (9.1.1.09240), Dr.Web SelfPROtect (09.01 .02.09240), the configuration scripts (9.1.0.09190), Dr.Web Anti-rootkit API (9.1.5.201409250), Dr.Web Scanning Engine (9.1.3.201409240), the firewall (9.1.1.09240), the file monitor SpIDer Guard (09.01.03.09260), Dr.Web Net Filter for Windows driver (9.1.1.09240) and the installer (9.1.2.09180, 10.0.3.09190) in the following products: Dr.Web Security Space and Dr.Web Anti-Virus version 9.1; Dr.Web Desktop Security Suite, which supports centralised administration (part of Dr.Web Enterprise Security Suite 10.0); and Dr.Web for MS Exchange 9.0.1.

The update delivers fixes of the following defects for Dr.Web Security Space and Dr.Web Anti-virus: A SpIDer Agent for Windows issue involving the location of a key file in a zip archive being specified via the Registration Wizard. An update module error occurring when key files with filename extensions other than .key were being processed. An installer issue connected to the assessment of free disk space which could result in false failures being indicated during product installation.

A firewall issue involving rules for applications whose files reside in network directories (this defect has also been corrected in Dr.Web Enterprise Security Suite).

In addition, Dr.Web Enterprise Security Suite control service issues involving corrupted configuration files causing Dr.Web Agent update errors and abnormal termination of the component at system startup have been resolved.

The configuration scripts have been modified to restore the operation of the self-protection module in the event it was installed incorrectly.

Dr.Web Security Space, Dr.Web Anti-virus and Dr.Web Desktop Security Suite will be updated automatically. However, a system restart will be required.

To use the updated version of Dr.Web for MS Exchange, users will need to install the updated version over the existing installation. After reinstallation, a server reboot will also be necessary.