Jump to content
Update to the Latest Version for Smooth VPN Performance ×
Kaspersky Support Forum

About this blog

Entries in this blog

Known Problem

Information on Trojan.Multi.Accesstr detection [KES for Windows]

Advice and Solutions (Forum Knowledgebase) Disclaimer. Read before using materials. This article is about Kaspersky Endpoint Security for Windows (KES for Windows)   Trojan.Multi.Accesstr detection is triggered when KES detects that one of Windows utilities in %systemroot%\system32 folder is replaced by cmd.exe or powershell.exe. Please see below for a list of affected files with exact detection names. Detection event looks like this:
svc_kms

svc_kms in Known Problem

0
Known Problem

Data collection for troubleshooting the KES Bitlocker management error "The policy can not be applied" [KES for Windows]

Advice and Solutions (Forum Knowledgebase) Disclaimer. Read before using materials. This article is about Kaspersky Endpoint Security for Windows (KES for Windows) In cases when Bitlocker encryption of a certain volume is started using KES Bitlocker management, and the product returns the following error: Event type: The policy can not be applied. Action: Encryption Reason: The system drive is not compatible with the Microsoft BitLocker encryption. Type of encryption: dis
svc_kms

svc_kms in Known Problem

0
Known Problem

Application startup control rules based on the file's metadata [KES for Windows]

Problem Application category based on the "Metadata" conditions created, but does not work. Solution This is expected behavior, in case the file does not have a digital signature, that can be trusted by local KES on the host in question, or is not known in KSN. Use sigcheck tool to see if the file has a valid digital signature – https://technet.microsoft.com/ru-ru/sysinternals/bb897441.aspx  Use other criteria, to determine the category (for example file hash).
svc_kms

svc_kms in Known Problem

0
Known Problem

KES installation error 0x80004005 [KES for Windows]

Advice and Solutions (Forum Knowledgebase) Disclaimer. Read before using materials. This article is about Kaspersky Endpoint Security for Windows (KES for Windows)   Problem When KES installation fails with error message "Failed to access local group policy. Error 0x80004005", installation log should be checked. If it contains something similar, follow the steps below. MSI (s) (F4:94) [11:27:28:103]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MS
svc_kms

svc_kms in Known Problem

0
Known Problem

KSWS Application Control rules with Digital Certificate FAQ [Kaspersky Security for Windows Server]

Security administrator can create KSWS Application Control rules based on Digital Certificate. What does product actually checks and how it is related to the file itself? First of all, product checks whether the file matches certificate. Secondly, whether certificate is valid. If any of verifications fail - launch of the file will be denied. And vice versa. If signed file which execution was allowed by certificate has been modified, will execution of the file be allowed? Alte
svc_kms

svc_kms in Known Problem

0
Known Problem

KSWS Error sending the request to KSN 0x80000063 (0x80000500) [Kaspersky Security for Windows Server]

This error message means that KSWS KSN-Client was unable to reach KSN Cloud servers (in most cases if KSN Proxy is used). Possible causes of the issue: Various transport-level issues KSC Server has been moved to another host with new DNS-name and IP-address Troubleshooting steps: Check that KSC is accessible via both its IP address and its hostname Check that option "Bypass proxy for local addresses" is enabled (KSC server properties > Advanced > C
svc_kms

svc_kms in Known Problem

0
Known Problem

KES for Windows on KES Cloud installation fails with '(1187/0x0 ("Bad parameter "VerifyCertDate"")' [KES for Windows]

Problem Description, Symptoms & Impact Local installation from a standalone package fails Diagnostics Check installation logs of the product. We are looking for the following string: 09.02.2022 17:06:19.453 00000374.000028B4 L1  KLSTD: #1, Error was caught in KLERR_throwError, c:\a\b\a_6vlf7p9h\s\csadminkit\development2\klri\pkginst\klpkinst.cpp@1061. Error params: (1187/0x0 ("Bad parameter "VerifyCertDate""), "KLSTD", c:\a\b\a_6vlf7p9h\s\csadminkit\development2\klri\pkgi
Stan Shpatar

Stan Shpatar in Known Problem

0
Known Problem

OS hangs caused by excessive use of file descriptors [KES for Linux]

Symptoms OS hang, sometimes with open file errors in journals Customer application degrades with errors "unable to open file", "too many open files" Hangs and third-party (compatibility) issues often require advanced data collection and are sophisticated to investigate. However, a quick check is possible: On a system where KESL has worked for some time (not immediately after reboot/restart), validate the output of the following command, ran as root, for numerous records of /u
Stan Shpatar

Stan Shpatar in Known Problem

0


×
×
  • Create New...