September 6, 2016
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.
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.
Tell us what you think
To ask Doctor Web’s site administration about a news item, enter @admin at the beginning of your comment. If your question is for the author of one of the comments, put @ before their names.