Kaspersky Security 10 for Windows Server (version 10.0.0.486): critical fix KB14272
Critical fix KB14272 for Kaspersky Security 10 for Windows Server was released on May 11, 2018.
Improvements and fixed issues
- Issues have been fixed in the application driver that led to critical operating system errors (BSoD).
- Issues have been fixed that led to the Kaspersky Security service stopping when the user signed in to the system.
- Issues have been fixed with applying keys for activating the application on the installation step using a KSV license. When installing the application using a build with the KB14272 critical fix integrated, the installation wizard recognizes a KSV license key.
- An issue has been fixed in the graphics file processing algorithms. The issue caused the application to freeze when attempting to analyze some JPEG file types.
- The list of files that can be analyzed has been expanded.
Application Startup Control
- The algorithm for calculating data about run DLL (when the DLL control feature has been enabled) has been optimized:
- The signature checking procedure has changed. The number of dynamic libraries required to check signatures has been lowered, thanks to which the number of system hangs has reduced.
- The application does not calculate all the metadata and control sums for run DLL if the data is not going to be used as triggering criteria or for writing the data to the report. For example, if logging of events under which the starting of such files falls is disabled, or if the starting of a file is processed according to a cache and requires only one parameter to be calculated.
The implemented changes reduces operating system load time and the burden on less powerful systems.
- Issues have been fixed with processing the running of PowerShell scripts via powershell.exe /c.
File Threat Protection
- Issues have been fixed with the iChecker component that led to the slow processing of file operations. This error was reproduced with file reputation requests to KSN included when copying files between local folders.
- Issues moving files to backup storage have been fixed. The application moved files to Backup only partially, which let to repeat attempts to move the same files without first deleting the partial files in Backup. This behavior caused the size of the Backup folder to grow.
- An option has been added allowing you to specify a maximum value for resources that the processor will allocate for performing scans for file threats. To configure a maximum processor load value, specify this value (%) in the system registry:
"CpuUsageOnScanThread"=dword:<value of maximum CPU load>
Due to technical reasons a private fix cannot be exposed to the full cycle of tests that ensure software quality. AO Kaspersky Lab explicitly disclaims any guarantees regarding both features and quality of a private fix. If not explicitly stated otherwise, private fixes are subject to the End-User License Agreement (EULA) under which the respective Kaspersky Lab product is licensed, in particular the following exclusion and limitation of liability notice. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL KASPERSKY LAB (THE RIGHTHOLDER) OR ITS PARTNERS BE LIABLE FOR ANY LOSSES AND/OR DAMAGES (INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR LOSS OF PROFITS OR INFORMATION, FOR BUSINESS INTERRUPTION, OR OTHER PROPERTY DAMAGE) ARISING OUT OF OR IN ANY WAY RELATED TO THE USE OF OR INABILITY TO USE THE SOFTWARE, EVEN IF THE RIGHTHOLDER AND/OR ANY PARTNER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. BY DOWNLOADING AND INSTALLING THIS SOFTWARE THE USER CONFIRMS THAT HE/SHE HAS READ THESE NOTICES, THE RELEVANT EULA, AND IS AWARE OF THE POSSIBLE RISKS.
If the private fix did not help, contact technical support.
How to install a patch for Kaspersky Security 10.x for Windows Server