September 6, 2016
Russian anti-virus company Doctor Web has updated Dr.Web Scanning Engine (11.1.2.201608300), Dr.Web Anti-rootkit API (11.1.6.201608170), the anti-exploit module Dr.Web Shellguard (11.01.02.09010), Dr.Web Updater (11.0.7.08260), Dr.Web Net Filter for Windows driver (11.1.2.08261), and Dr.Web SelfPROtect (11.01.04.08150) in the products Dr.Web Security Space 11.0, Dr.Web Anti-virus 11.0 and Dr.Web Anti-virus 11.0 for Windows Servers as well as in the Internet service Dr.Web AV-Desk 10.0 and Dr.Web Desktop Security Suite supporting centralised administration (part of Dr.Web Enterprise Security Suite 10.0). Dr.Web Updater and the scanning engine have also been updated in Dr.Web 11.0 for MS Exchange and Dr.Web 11.0 for IBM Lotus Domino. The update resolves known software issues.
Specifically, it eliminates a scanning engine problem that caused the system to freeze while the virus databases were being updated and SpIDer Guard was running in paranoid mode. Furthermore, it corrects a defect that prevented Dr.Web from logging file monitor actions after exceptions had been defined in the settings.
A Dr.Web Shellguard problem that occurred on machines that had Microsoft Office XP applications installed on them has been fixed. The update also eliminated problems resulting in false positives when printing Microsoft Word 2007 documents on Canon LBP 1120 printers, working with JavaScript in Mozilla Firefox, and using the iBank2 service and the BIFITSigner plugin in Internet Explorer In addition, changes were made to the module so that Microsoft Office applications launched using VMWare ThinApp software now operate properly. A problem involving the abnormal termination of Internet Explorer 9 while webpages using ActiveX were being loaded has been resolved.
Also corrected was a Dr.Web Updater issue that caused problems when updating the anti-virus via a proxy server.
A self-protection module defect that might cause system crashes if Microsoft Hyper-V was enabled has been corrected.
The update will be performed automatically; however, a system reboot will be required.
View the article
