Search the Community

Today my Kaspersky Standard got an update and now it's full of pink AI tags? Like so many people all around the world, I don't want or need any AI crap. How can I disable it in my Kaspersky Standard? I simply refuse to get this crap forced down my throat.

Hello @eina, Thank you for the information! IF the *update* errors persist - READ & follow *all* of: General recommendations for solving database update issues in Kaspersky applications. Uninstall Kaspersky Premium using Windows -> Add or remove programs & READ: How to uninstall the application in Windows 8 or later - in the check-boxes that appear - Save subscription *only*, leave all other check-boxes clear - at the end of the *uninstall* of Kaspersky Premium shutdown the computer using SHUTDOWN, not Restart, when the computer is OFF, power ON by pressing the power button, log in. Download a new Kaspersky Premium installer from (your) MyKaspersky account OR https://www.kaspersky.com/downloads#update-product, install Kaspersky Premium, run a manual Database update -> *make sure it's successful*? Recheck the Arknights: Endfield and OR Duet Night Abyss issue, IF *either* persist log a request with Kaspersky Customer Service, https://support.kaspersky.com/b2c#contacts -> select Email, then fill in the template as shown, include a *detailed history*. Support may request logs, data & traces, they will advise you. *Note - don't use the AI-bot to submit the case* Please share the outcome with the Community, when it's available? Thank you🙏 Flood🐳+🐋

Hallo Zusammen, für das KSC 15.1 für Windows steht inzwischen Update 2 zur Verfügung - Version 15.1.0.22239. KSC15.1 Update 2 - Version 15.1.0.22239 Vollständiger Support - 15. September 2027 Eingeschränkter Support - 15. September 2028 Infos https://support.kaspersky.com/de/ksc/15.1 Download https://support.kaspersky.com/de/dl_ksc Online-Hilfe https://support.kaspersky.com/de/ksc/15.1/5022 Neuerungen https://support.kaspersky.com/de/ksc/15.1/12521 Systemanforderungen https://support.kaspersky.com/de/ksc/15.1/96255 Eine Neuerung, die nicht in der Liste steht: Nun lässt sich nach "Windows Server 2025" filtern. Grüße Alex

I did get this problem when I updated the version manually instead of waiting for it to auto update. I now wait for the auto update. In the past I found the only way to fix this was to uninstall/re-install Kaspersky

Hello Kaspersky Support Team, I am writing to report a serious issue with frequent Blue Screens of Death (BSOD) that started occurring immediately after a recent update to my Kaspersky Plus software. I suspect there may be a compatibility issue with the latest version. Problem Description: The BSOD error is consistently IRQL_NOT_LESS_OR_EQUAL (a). This issue began on or around September 2nd, 2025, which coincides with when my Kaspersky Plus updated to version 21.22.7.466(a). The crashes primarily happen when I am running specific games. The issue is most severe and easily reproducible with the game Delta Force, but it also occurs with Honkai Impact 3 (BH3.exe). System & Software Information: Kaspersky Version: Kaspersky Plus 21.22.7.466(a) Operating System: Windows 11 Pro for Workstations OS Version: 25H2 OS Build: 26220.5770 Experience Pack: Windows Feature Experience Pack 1000.26100.240.0 Graphics Driver: NVIDIA Studio Driver 580.97 Technical Details from BSOD Dump Analysis: I have analyzed a memory dump file, and the findings point towards a potential driver conflict leading to stack corruption. The key points are: The crash occurs within the NT Kernel (ntkrnlmp.exe). The faulting function is nt!RtlpUnwindPrologue, which fails during a stack walk operation. The call stack indicates this stack walk was initiated by Event Tracing for Windows (ETW), likely for logging purposes. This pattern often suggests that a filter driver (such as those used by antivirus software) may have caused an unstable state, leading to a crash when the system tries to read the stack. Could you please investigate if there is a known issue with version 21.22.7.466(a) regarding game compatibility or conflicts with specific system components? Are there any suggested workarounds or diagnostic steps I should take? Minidumps are available and glad to share. Thank you for your time and assistance.

Advice and Solutions (Forum Knowledgebase) Disclaimer. Read before using materials. 0 - Update completed successfully 1 - All files are up-to-date (No available updates) Result codes depending on OS type: Windows Linux(FreeBSD) Return code description -1 255 Command line parsing exception -2 254 Update Utility error (exception or another malfunction including incorrect command line arguments) -5 251 Update process failure (Not all components are updated, File does not exist on update source, Invalid file signature, Index file damaged, File is not valid XML structure or does not exist) or network error -6 250 Bases are not consistent after update -3 253 Fail (error code for other update process failures)

Advice and Solutions (Forum Knowledgebase) Disclaimer. Read before using materials. Product: KSC 11+ Applies also to the update utility version 4.1 and more recent. Consider the following problematic scenarios: You have installed KSWS on the KSC server and enabled Traffic Security component and Traffic Security uses MITM mechanism to analyze traffic. You use a 3rd party software or hardware appliance for traffic filtering and this appliance disrupts connections to HTTPS-enabled public update servers. It can be a hardware appliance like BlueCoat or F5, FortiGate SSL Deep Inspection, or a software proxy like Squid that uses ICAP to redirect traffic to another security application for scanning. KL uses HTTP public key pinning mechanism to verify update server authenticity; certificate used for authentication is self-signed by KL. Using any MITM-based solutions for SSL traffic inspection will lead to failures in establishing connection between KSC and a HTTPS-enabled KL update source. It happens because any MITM traffic inspection will forward a wrong certificate to KSC after inspection and KSC11 will break the connection. The following string can be found in up2date trace: self signed certificate in certificate chain The following trace files are required for accurate diagnostic: $up2date-1103.*, $up2date-1103-eka.* Please bear in mind that Kaspersky Support needs KSC traces mentioned above to be collected BEFORE you apply any of the workarounds listed in this post. Troubleshooting steps If you have KSWS blocking traffic, add Up2Date.exe process or the update source certificate to trusted in Traffic Security settings. If you use a 3rd party appliance to filter traffic, you can explicitly allow traffic signed by KL certificate. Otherwise you can use HTTP to download updates. There are two ways to make KSC use HTTP: Set a server flag on KSC using following commands: klscflag.exe -fset -pv klserver -s Updater -n DisableKLHttps -t d -v 1 and on Update Agents (Distribution Points) getting updates from the internet, if any: klscflag.exe -fset -pv klnagent -s Updater -n DisableKLHttps -t d -v 1 Explicitly set update task to use HTTP sources URLs, for example http://p00.upd.kaspersky.com. Full list of HTTP-enable sources can be found in <insecure_sites_list> parameter in http://dnl-05.geo.kaspersky.com/updates/upd/updcfg2.xml Download updates using update utility 4.0. More recent version of update utility uses https.

hI, Kaspresky Standard, i noticed last few days problem with update. when i start it manually it says: "Update databases. Last update: not run" through Home screen: it starts and after it finishes "we recommend that you update databases and application modules." in reports it says that it has finished!? Kaspersy is green but with 1 warning "Databases are out of date" Windows security says the same. before few minutes i opened an email thorough outlook and word attach. kaspersky 15 sec later found trojan (kasp. couldn't delete it. i did it manualy) should i be worried and what to do about update? Thanks in advance.

tengo kaspersky premium, la version 21.21.7.384a, y he visto que ha salido la 21.22.7.466, pero a mi no seme actualiza.. y no quiero actualizar manualmente, porque se rompen las extensiones de los navegadores y hay que desistalar entero kaspersky volver a instalar , se sabe cuando se lanza el auto update??

Last month until now I tried to update anydesk software on app updater feature but couldn't update.

Здравствуйте. Версия 4.2.0.1438 (и GUI и console) при запуске на Windows 7, windows Server 2012 r2 от имени другого пользователя выдаёт ошибку: Update Utility system error occured Failed to create instance of BlGlobalsImpl: 0x80000045 (Access denied) Соотвественно нет возможности запустить из планировщика windows. На Windows 11 работает.

Advice and Solutions (Forum Knowledgebase) Disclaimer. Read before using materials. Product: KSC 11 and more recent versions Consider the following problematic scenario: You use a caching proxy server to download updates for the KSC Server, for example, Squid. KSC is configured to download updates via https (default config). $up2date-1103-eka.log analysis KL uses the HTTP public key pinning mechanism to verify update server authenticity; a certificate used for authentication is self-signed by KL. A certificate revocation list is also implemented. More information about the certification revocation process is available here: https://learn.microsoft.com/en-us/archive/blogs/ieinternals/understanding-certificate-revocation-checks https://technet.microsoft.com/en-us/library/ee619754(WS.10).aspx A recent update of CRL was performed at the end of July 2023. CRL is available on this link: http://crl.kaspersky.com/cdp/KasperskyLabPublicServicesRootCertificationAuthority.crl Old CLR was valid till 23.7.2023 and is expired now. When KSC requests the CRL file, the proxy server sends back to KSC the cached version of it and the CRL verification fails. The details can be found in the $up2date-1103-eka.log to identify the issue precisely. 04:01:48.817 0x326c INF httpcli cert_revoke 0x70e2908 Got error: 0xa0010019 (http_client::eCrlHasExpired) 04:01:48.817 0x326c INF httpcli Req 0x70e2908 <- HttpsErrorOccurs: Revocation Error [0xa0010019 (http_client::eCrlHasExpired) 04:01:48.892 0x1d0c INF updater core: ========= Downloading primary index result TLS error ========= Troubleshooting steps To solve the problem, an administrator of the proxy server should turn off caching of the http://crl.kaspersky.com/cdp/KasperskyLabPublicServicesRootCertificationAuthority.crl file. It is recommended to turn off caching for all files downloaded from public update servers using this mask: *.kaspersky.com *.kaspersky-labs.com An alternative workaround: Set a server flag for KSC using the following commands: klscflag.exe -fset -pv klserver -s Updater -n DisableKLHttps -t d -v 1 Also, set a server flag for Update Agents (Distribution Points) that get updates from the Internet, if any: klscflag.exe -fset -pv klnagent -s Updater -n DisableKLHttps -t d -v 1 Explicitly set an update task to use HTTP sources for URLs, for example, http://p00.upd.kaspersky.com. The full list of HTTP-enabled sources can be found in the <insecure_sites_list> parameter at http://dnl-05.geo.kaspersky.com/updates/upd/updcfg2.xml

Problem Description, Symptoms & Impact When deploying Auto patches from KSC, installing Network Agent or Kaspersky Endpoint Security, installation fails with bad junction errors. Diagnostics While Auto patch deployments over KSC will directly generate an event in Events section of KSC, manual Network Agent or KES installations will end with Fatal Error message and installation logs will contain information such as below: Application: Kaspersky Security Center Network Agent – Error 25002. Error while installing: Error 1205/0x0 (‘The system cannot find the path specified.’) accessing filesystem object ‘C:\ProgramData\Application Data\KasperskyLab\adminkit\data\.bases’. Error 25002. Error while installing: Error 1205/0x0 (‘The system cannot find the path specified.’) accessing filesystem object ‘C:\ProgramData\Application Data\KasperskyLab\adminkit\data\.bases’. A GSI collected from the device will also contain a txt file named Junction_ProgramData_PCNAME.txt which will show faulty junction points that prevent installation. GSI log: Junction Point Log with Junction: To find bad junction points manually, you check use the command below in CMD: dir /AL C:\ProgramData Workaround & Solution To remove the faulty link, you must follow the steps below: Open a CMD Prompt with elevated account Run the commands below (According to our example above, the fault junction point shows Z:\ drive) rem In order to delete the link, you must first access the directory. cd C:\Programdata rem Removing the link rd "Application Data" rem Recreating the link is not mandatory as the installation itself will create the link if not found mklink /J "C:\ProgramData\Application Data" C:\ProgramData These 3 commands can be used to create a batch file to be sent to multiple devices that are having the issue.

Problem KSC and KS4Android are implemented but KSC is offline and could not access Internet. KUU can be used for updating KS for Android and distribute the update databases. But after running KUU (Kaspersky Update Utility), you cannot find actual KES for Android versions. Solution AV bases for new KESM versions will appear in KUU UI after running KUU with empty application list. The KUU settings should look like the following (in order to update the list of supported applications, you need first to press 'Start' with a blank application list as follows):

We've been experiencing the same critical issue for almost a month, during this period you managed to fix it and broke it back again with the latest update, it's affecting multiple users, devices, networks and platforms. Support keep asking for the same, switch networks, try other locations, send screenshots of the same behavior, at this point all the info you're gathering for users don't move the investigation forward and only delay escalation. This issue is reproducible, affects all sites and services, affects multiple platform and has been ongoing for weeks. That clearly indicates a backend / infrastructure / core client issue not a configuration mistake. We respectfully ask Kaspersky to: Acknowledge the incident publicly, an provide with a timeline for a fix or a temporary workaround or at least an official status update. Many of us rely on this service daily and right now is unusable. We are asking for transparency, escalation an a real resolution.

De automatische update naar de nieuwe versies MR24 (21.24.8.522) NL Kaspersky Standard - Plus - Premium is begonnen. Na installatie is een handmatige database-update + reboot aanbevolen.

Consider the following scenario: Open update or scan KSWS task. Go to Schedule->Advanced→Task stop settings: Solution Task's stop settings are greyed out and cannot be changed. This is by design behaviour: Task stop settings can be changed only for real-time tasks - Real-Time File Protection and Script Monitoring. These tasks can be configured in KSWS policy to pause the execution at certain time not to interfere with 3d apps or speed up heavy operations. Task stop settings cannot be changed for Updater and On Demand Scan tasks. These tasks should be executed without pausing them.

update root certificates - https://support.kaspersky.com/kess/3.0/diagnostics/13727

Thank you for your replies . I will update you.

Problem In some cases, it is possible to run a database upgrade task on the KSWS/KICS/KESS host, but despite the upgrade task successfully completing, the databases are still out of date. Solution Most probably product operates in UpdateBlackListOnly mode. This happens in cases when product is activated with activation code and is unable to reach our activation servers. Thus KSWS fails to receive/refresh activation ticket and downloads updates only for Blacklist. Possible ways to solve the problem: 1. Activate with a key file; 2. In case KSWS needs to be activated with the code make sure that either KSWS server is able to reach our public activation servers directly or set up KSC to act as activation proxy and make sure that KSWS server is able to reach KSC on TCP17000.

Status update: Cервис Youtube не доступен через VPN. Kaspersky Secure Connection обеспечивает шифрование трафика для защиты интернет-соединения пользователей. Продукт позволяет работать с ресурсами, которые ограничили доступ для российских пользователей по собственному решению, и с сайтами, доступными в России. В соответствии с действующим законодательством Российской Федерации, решение не предназначено для обхода ограничений доступа к определенным информационным ресурсам. В отдельных случаях сайты или онлайн-сервисы могут сами ограничивать подключение при обнаружении защищенных или анонимизирующих технологий — это связано с внутренними политиками безопасности этих ресурсов. Данная тема закрыта.

My company wants to avoid exposing data to the public internet, so we prefer to deploy the KSC server on the internal network. However, to obtain the latest updates, we plan to deploy another Kaspersky Update Utility server on the external network as an update server. I have enabled the FTP service on the external Kaspersky Update Utility server, with the shared folder set as "Updates folder," and FileZilla has verified it as accessible. In the internal KSC web console, I configured the task as shown in Figure 3 and set up the update source, but it still failed. Is it because some files were not downloaded in the Kaspersky Update Utility? Or is the FTP configuration incorrect? Or are there other issues?

Hello @Bernd Wechner, Welcome! KSK time report discrepancy issues may be difficult, we always try to replicate the original complaint for comparison, so apologies for the delay. Regarding (your) 12year old hacking KSK or the OS: Have (you) asked them - in all seriousness - it's much better to be upfront, something along the lines of, it's not that we don't trust you but you're a smart kid, we don't want to waste time with Community support / support if you've messed with the system, the reason we have KSK is to keep you safe. In our tests we replicated the issue - then resolved it - this is where it took so long bc KSK is a PIA when it comes to uninstall & clean install & post install. That's what (you) need to do, shutdown *absolutely-everything*, then, using Windows Add & remove programs - uninstall KSK, then shutdown the computer, make sure it's a *full* shutdown, restart, login. Download a *new* KSK installer from here: https://www.kaspersky.com/downloads - scroll down to the downloads section & select KSK. Install KSK, after the full install, reboot the computer, make sure it's a *full* shutdown, restart, login. At this point KSK time reporting will be *accurate* but KSK will send a notification in 24 to 48 hrs to do *another* *full* shutdown bc it will have applied the latest version *silently* - make sure you do the *full* shutdown, restart, login *again*. At that point KSK time reporting will still be working & you & the kid are good to go. A couple of other points to note: BOTH children must only have a LOCAL Windows user account - no elevated profiles whatsoever. Both Children - IF the children use Android phones (as well) the Settings application must be Forbidden. To permit access to this is the equivalent of giving an elevated profile on a Windows device. Images: the 1st set shows KSK version originally installed, version post install & replication of (your) KSK time settings Set 2 shows: KSK version post silent update & KSK report, for todays time-test we allocated 10 minutes, was on the computer for 8, KSK updated accurately-in-real-time. Please share the outcome with the Community, when it's available? Thank you🙏 Flood🐳+🐋

Description and cautions This article describes how to configure dump for capturing memory dumps, including application memory. Details The recommended text editor is nano, below is a quick tutorial on how to use it if you are using it for the first time. Configure kdump Altlinux There is no kdump-tools package in the default repository, so it has to be downloaded from the sisyphus repository: Go to https://packages.altlinux.org/en/sisyphus/srpms/kdump-tools/ In List of rpms provided by this srpm select the kdump-tools package for the required architecture (can be checked by running uname -m) Download the package from the Download link Install it by running apt-get update && apt-get install <path to the downloaded rpm> After that, follow the Debian instruction from Edit /etc/default/kdump-tools step Red Hat based distributions (tested on Fedora 38, Rocky Linux 9, Red OS) Install kexec-tools sudo dnf install kexec-tools Edit /etc/kdump.conf. In the configuration file edit the core_collector setting: option -d should be set to 17 instead of 31 Edit /etc/default/grub. Edit GRUB_CMDLINE_LINUX, add crashkernel=256M to reserve enough RAM for the dump kernel to run, and nmi_watchdog=1, to capture a dump in case of a system hang Run sudo grub2-mkconfig -o /boot/grub2/grub.cfg Reboot Enable kdump service sudo systemctl enable --now kdump.service Debian based distributions (tested on Debian, Astra CE, Alt Linux) Install kdump-tools sudo apt update && sudo apt install kdump-tools -y Edit /etc/default/kdump-tools. In the configuration file edit the MAKEDUMP_ARGS variable: option -d should be set to 17 instead of 31 Configure the bootloader In /etc/default/grub edit GRUB_CMDLINE_LINUX_DEFAULT, add nmi_watchdog=1 to capture a dump in case of a system hang In /etc/default/grub.d/kdump-tools.cfg change crashkernel value to 384M-:256M (default is 384M-:128M) Expected result: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=384M-:256M" ave and run sudo update-grub SUSE Linux Install kdump sudo zypper in kdump kexec-tools Edit /etc/sysconfig/kdump Change KDUMP_DUMPLEVEL variable to 17 Edit /etc/default/grub Edit GRUB_CMDLINE_LINUX_DEFAULT, add crashkernel=256M to reserve enough RAM for the dump kernel to run, and nmi_watchdog=1, to capture a dump in case of a system hang Update the bootloader configuration sudo grub2-mkconfig -o /boot/grub2/grub.cfg Reboot Enable kdump service sudo systemctl enable --now kdump.service Configure SysRq dump trigger To enable SysRq trigger, these key combinations 'kernel.sysrq = 8'(without quotes) has to be added to /etc/sysctl.conf. Reboot or run sudo sysctl --system After the set up above is complete, to manually trigger a dump press Alt+SysRq, Alt+C. Alternatively: echo 8 | sudo tee /proc/sys/kernel/sysrq (Command above is only needed if kernel.sysrq is not set in /etc/sysctl.conf) echo c | sudo tee /proc/sysrq-trigger Location of the dump files may vary between different Linux versions, it is configurable in the kdump configuration file. In Debian based distributions it is set by KDUMP_COREDIR variable. In Red Hat based distributions it is set by the path setting, generally the default location is /var/crash. Make sure that the dump folder has enough free space for the dump to be written. You may search by filemask: vmcore. Related Information

I want to configure a KSC as an update server on the external network and a KSC as a functional server on the internal network to distribute agents. After completing the initial setup, I found in the help documentation that I need to configure it in "General," but I couldn’t find the "General" section—where is it? Additionally, I've granted myself all roles，why are the "Infrastructure" and "Console Settings" options grayed out? Currently, the only account I can log in with is the local account using the local machine password—what are the passwords for the other accounts?