Search the Community

Hello Kaspersky Forum, Just an inquiry rather than a problem per se. I have been running Kaspersky Standard for several months. Today it forced a self-reinstall/update; is this expected? Please see screenshot for my activity log, showing log activity then non-user initiated reinstall. I tried to search the product update news on the Kaspersky website first; please accept my sincere apologies if I have missed an announcement/update log! OS: Win10 Built 19045 Current App. Version: 21.19.7.527(b) Thank you for your time and help, I appreciate it.

So you agree that Kaspersky needs to update the documentation?

@Doctorull The issue has already been fixed in patch B for 21.22, which is distributed to users gradually. To check the availability of this patch, update the databases of version 21.22 and restart your OS. Or wait for 21.23 release - in this version the issue, of course, has also been fixed.

I can't see clearly any file. Repeat for the third time: first of all, update the product version, KAV is outdated - bugs are no longer fixed.

@ursu82 How can we verify that the exception was created correctly if you're hiding all information? If the first three exceptions in Program Files (x86) were made for the same file, update the product version to K. Standard as @Berny recommended above. And submit the file via TIP (button "Send to reanalyse") or customer service as @harlan4096 proposed.

BÖLÜNMÜŞ TÜNELLEME ÖZELLİĞİNİ DİSCORD.EXE VE UPDATE.EXE EKLEDİKTEN SONRA DİSCORD ÇALIŞMIYOR AMA BÖLÜNMÜŞ TÜNELLEME KAPALIKEN TÜM UYGULAMALAR SORUNSUZ ÇALIŞMAKTADIR. YARDIMINIZI RİCA EDERİM.

The error encountered during the update of certain machines: An error 1186/0x0 ('The specified file was not found.') occurred while copying the file 'C:\ProgramData\KasperskyLab\adminkit\1103$FTClTmp\WUS3015415D59A4ECDD371E043B8BD226430AF9DE0B' to 'C:\ProgramData\KasperskyLab\adminkit\1103\wusfiles\30\3015415D59A4ECDD371E043B8BD226430AF9DE0B.~tip-temp~' Please, can someone help to fix this issue?

KSC (15.1) is deployed on the server, and KES (12.7) on the endpoints. When running updates from the KSC source, many endpoints show the error "Update file set is corrupted," while others (a smaller number of devices) display "Not all components were updated." I have already cleared the storage and re-downloaded the updates, but the issue persists

Administrator receives the notification about outdated anti-spam (AS) and/or anti-virus (AV) bases because a large time interval for updating AS and/or AV databases is set (every 5 hours or more for AS and every 24 hours or more for AV). Anti-spam and anti-virus bases should be updated much more often. Accordingly, Kaspersky Security Center should also update anti-spam and anti-virus bases more frequently. The best way is to update anti-spam bases directly via Internet from Kaspersky Update servers every 5 minutes. Anti-virus bases should be updated every 1 hour. If it is not possible, try to update Kaspersky Security Center and Kaspersky Security for Microsoft Exchange anti-spam bases every 30 minutes or every 1 hour, but in this case you should not expect a high spam detection rate.

In order to upgrade KATA from 3.7.2 to 4.0 > 4.1 > 5.0 > 5.1 > 6.0 please follow the manual below. Step-by-step guide Prior to PCN upgrade you have to disconnect all Sensors, SCNs and Sandboxes. After upgrade Sandboxes and Sensors must be reinstalled, disconnected SCNs – upgrade to 4.0 and 4.1 and then reconnect them to PCN. Upgrade order described here - https://support.kaspersky.com/KATA/4.0/en-US/198801.htm Information which is kept during upgrade - https://support.kaspersky.com/KATA/4.0/en-US/227848.htm Contents of backup - https://support.kaspersky.com/KATA/4.0/en-US/198854.htm NB! Events database is not being transferred if you want to restore backup to new installation (e.g. new physical or virtual server). System requirements are the same for 3.7.2 and 4.0/4.1, so if 3.7.2 installation matches the requirements, you can upgrade keeping the same hardware/VM configuration - https://support.kaspersky.com/KATA/4.0/en-US/194861.htm For upgrade you don’t need .ktgz archives, only the ISO file. Pre-upgrade recommendations This recommendation is optional for vanilla 3.7.2, and it's a must for 3.7.2 PF1 Before upgrading KATA 3.7.2 to KATA4, copy and run this script. Run it as root: python /var/opt/kaspersky/apt/files/kata4-preupgrade-checker.py Expected result for vanilla 3.7.2: In case any issues arise, please contact Kaspersky support, and provide script output as shown on screenshot above and this script log, the script shows log location upon completion: /data/kata4-preupgrade-checker.log Upgrade order Create backup of CN and do the manual backup of /var/opt/kaspersky/apt-preprocessor/preprocessor.conf (from CN and sensors, especially if tuning was made at sensors). Mount installation ISO to KATA VM or boot from drive with ISO, if a server is physical. Select Install Kaspersky Anti Targeted Attack Platform. Select Disk marked as [upgrade] and press Enter. Select Upgrade and press Enter Select Upgrade again and press Enter Wait for the completion and check at WEB UI, that there are no errors / issues / etc. Storage migration is a lengthy procedure and may take many hours, depending on the installation. No visual indication of progress is provided, but it's not frozen. Perform a backup of 4.0 The upgrade procedure from 4.0 up to 4.1 is pretty much the same, you have to map ISO and boot from it, select disk marked as [upgrade], proceed, make a backup of 4.1 Upgrade procedure from 4.1 to 5.0 is described here. Before updating the product from version 4.1 to version 5.0, check which boot mode is used on the server (BIOS or UEFI). If UEFI is used, the update will fail. To avoid this, you need to update from a special KATA 5.0 image which can be provided by Kaspersky Support. Before upgrade DISABLE NTP on 4.1 Information which is kept during upgrade. 1) You can obtain file upgrade_preparation-1.0-py3-none-any.whl in kata-cn-5.0.0-5201-inst.x86_64_en-ru.iso, just mount it in Windows, go to support folder, copy this file and put it to /tmp via WinSCP to your KATA 4.1. 2) Proceed with steps described in Online help After mounting ISO and running from it you will be prompted to say y + ENTER to upgrade Then press ENTER, read EULA and select "I accept" Then you have two options: leave cluster and bridge/overlay subnets by default (just by pressing ENTER in windows below) or you can change them as you want (especially if these subnets crossover with your infrastructure subnets) Upgrade procedure can take a while, after that you'll be prompted to choose management interface, enter it's details again Enter password for admin Configure DNS servers and press ENTER Enable SPAN capturing by typing y or skip this step as n and press ENTER (you can do it later after upgrade). Don't forget to read this article, kindly pay attention to section "Special considerations for upgrading Kaspersky Anti Targeted Attack Platform from version 4.1 to version 5.0" After upgrade you have to perform initial configuration of KATA via web interface using admin (with Local administrator checkbox) credentials being set up during upgrade, please refer to https://support.kaspersky.com/KATA/5.0/en-US/242580.htm and https://support.kaspersky.com/KATA/5.0/en-US/240726.htm Once the configuration is completed, it's possible to log in to Web UI as regular local admin: use Administrator/Administrator login and password, "Local administrator" checkbox must be enabled, too. Change the password for Administrator user and proceed with adding license, creating users etc. Upgrade procedure from 5.0 to 5.1 is described here. Step-by-step guide of upgrade is here. Information kept during upgrade is here. According to KB you have to upload upgrade.tar.gz to /data/upgrade But first, you have to create this directory and set permissions to it to be able to upload upgrade package via WinSCP (in this example we use chmod 777 as an ultimate set of rights, you can use another set) mkdir /data/upgrade chmod 777 /data/upgrade After that upload upgrade.tar.gz to /data/upgrade via WinSCP and unarchive it cd /data/upgrade tar xvf upgrade.tar.gz Give executive permissions to script install_kata_upgrade.sh and install pre-upgrade package Execute as root chmod +x /data/upgrade/install_kata_upgrade.sh sh install_kata_upgrade.sh You'll see this And finally run upgrade (use admin user credentials which you use for ssh) kata-upgrade --data-dir /data/upgrade --user admin --password 'passw@rd' In a while you should receive message about successful upgrade . Upgrade procedure from 5.1 Ubuntu to 6.0 Ubuntu is described HERE Step-by-step guide of upgrade is HERE Information kept during upgrade is HERE Upload kata-cn-ubuntu-upgrade-6.0.0-200-x86_64_en-ru.tar.gz via WinSCP to /home/admin Unpack it to /data by command tar xvf /home/admin/kata-cn-ubuntu-upgrade-6.0.0-200-x86_64_en-ru.tar.gz -C /data/ Install the upgrade package by running the following commands cd /data/upgrade/ chmod +x ./install_kata_upgrade.sh ./install_kata_upgrade.sh Install the upgrade by running the following commands source /tmp/upgrade-venv/venv/bin/activate kata-upgrade --data-dir /data/upgrade/ --password <password specified during component installation> If the password contains special characters, the password variable must be specified in the following format: --password '<password>' Mount the iso image of Kaspersky Anti Targeted Attack Platform version 6.0 and restart the server In the GRUB menu, select Upgrade KATA 5.1 Accept EULA Confirm upgrade Wait for completion, don't forget to remove ISO or ensure that after reboot KATA boots from local disk. Done. Known problem: during upgrade to 6.0 upgrade script may fail With the following error: 2024-10-21 10:56:16,664.664 [kata_upgrade.tasks.upgrade_base_task][ERROR] Upgrade task " (UpdateDeploymentServices)" completed with an error, elapsed time: 191.07 sec Traceback (most recent call last): File "/tmp/upgrade-venv/venv/lib/python3.11/site-packages/etcd3/client.py", line 46, in handler return f(*args, **kwargs) ^^^^^^^^^^^^^^^^^^ File "/tmp/upgrade-venv/venv/lib/python3.11/site-packages/etcd3/client.py", line 257, in get_response return self.kvstub.Range( ^^^^^^^^^^^^^^^^^^ File "/tmp/upgrade-venv/venv/lib/python3.11/site-packages/grpc/_channel.py", line 1161, in __call__ return _end_unary_response_blocking(state, call, False, None) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/tmp/upgrade-venv/venv/lib/python3.11/site-packages/grpc/_channel.py", line 1004, in _end_unary_response_blocking raise _InactiveRpcError(state) # pytype: disable=not-instantiable ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with: status = StatusCode.UNAVAILABLE details = "DNS resolution failed for etcd.dyn.kata:2379: C-ares status is not ARES_SUCCESS qtype=A name=etcd.dyn.kata is_balancer=0: Timeout while contacting DNS servers" debug_error_string = "UNKNOWN:DNS resolution failed for etcd.dyn.kata:2379: C-ares status is not ARES_SUCCESS qtype=A name=etcd.dyn.kata is_balancer=0: Timeout while contacting DNS servers {grpc_status:14, created_time:"2024-10-21T10:56:16.663456976+00:00"}" > After which web interface is not be accessible with Administrator credentials. Solution: Login to web interface using admin credentials (not Administrator) If current sizing by Endpoint Agents is not 0 then remember current value and set it to 0. If this setting cannot be applied because there are 0s for other integrations then set mail to 1. For example: Would be changed to Apply this configuration, login back with admin credentials and configure original values back: The point is to zero out any single of the integrations and then configure it back to original value, so depending on original configuration you may need to zero out other integration instead of Endpoint Agents. After this login to web interface with Administrator should work. Do that and wait till all errors in dashboard are cleared. Now you can restart upgrade script from step 5: sudo -i cd /data/upgrade/ ./install_kata_upgrade.sh source /tmp/upgrade-venv/venv/bin/activate kata-upgrade --data-dir /data/upgrade/ --password ... --current-task-index 5 Known problem: during upgrade to 6.0 when booting to iso an error is displayed: File /mnt/debconf_menu_answers.ini not found Possible causes: Upgrade script that was running before reboot did not finish successfully. Check logs in /var/log/kaspersky/installation/. It is safe to boot not from iso at this point to check that log. In case script failed (but not like above) escalate incident. Wrong partitioning of /dev/sda, where there is sda4 instead of sda3. Check output of lsblk -o NAME /dev/sda Correct output: # lsblk -o NAME /dev/sda NAME sda ├─sda1 ├─sda2 └─sda3 Wrong output: # lsblk -o NAME /dev/sda NAME sda ├─sda1 ├─sda2 └─sda4 Solution: $ sudo -i 1) Create partition table backup # sfdisk -d /dev/sda > sda.bkp # cp sda.bkp sda.new 2) Edit partition table file # vi sda.new 3) Enter edit mode by pressing "i" and change /dev/sda4 to /dev/sda3 For example if you have Change the number 4 to 3. Nothing else should be changed in the file! To save press ESC then :wq! and Enter. Apply new partition table # sfdisk --no-reread -f /dev/sda < sda.new Now you can boot from iso and continue upgrade. Upgrade procedure from 5.1 Ubuntu to 6.0 Astra is described below Installation is described here https://support.kaspersky.ru/KATA/6.0/en-US/243480.htm But, we have some differences here Upload kata-cn-astra-upgrade-6.0.0-200-x86_64_en-ru.tar.gz to /data Then move to *****@*****.tld:~# cd /data Execute tar xvf /data/kata-cn-astra-upgrade-6.0.0-200-x86_64_en-ru.tar.gz -C /data/ Execute cd /data/upgrade/ chmod +x ./install_kata_upgrade.sh source /tmp/upgrade-venv/venv/bin/activate kata-upgrade --data-dir /data/upgrade/ --password <password of the 'admin' user> Mount the iso image of Kaspersky Anti Targeted Attack Platform version 6.0 and restart the server. You have to start server from mounted ISO and select "Upgrade KATA 5.1 server" Proceed That's it, you've upgraded your 5.1 Ubuntu to 6.0 Astra Upgrade procedure from 6.0 to 6.1 is below https://support.kaspersky.com/help/KATA/6.1/en-US/246850.htm It considers upgrade from 6.0 or 6.0.1 directly to 6.0.2 - https://support.kaspersky.com/KATA/6.0/en-US/271957.htm, to 6.0.3, and finally to 6.1 - https://support.kaspersky.com/help/KATA/6.1/en-US/243480.htm 6.0 > 6.0.1 Upload upgrade.tar.gz to /home/admin directory Execute following commands below root@1.srv.node1.node.dyn.kata:~# mv /home/admin/upgrade.tar.gz /data/ root@1.srv.node1.node.dyn.kata:~# tar xvf /data/upgrade.tar.gz -C /data/ upgrade/ upgrade/images.tar.gz upgrade/install_kata_upgrade.sh upgrade/kata_license-1.0-py3-none-any.whl upgrade/kata_upgrade-1.0-py3-none-any.whl upgrade/ubuntu_image_versions.json upgrade/updates/ upgrade/updates/Packages.gz upgrade/updates/glibc_2.35-0ubuntu3.6.debian.tar.xz upgrade/updates/glibc_2.35-0ubuntu3.6.dsc upgrade/updates/glibc_2.35.orig.tar.xz upgrade/updates/glibc_2.35.orig.tar.xz.asc upgrade/updates/libc-bin_2.35-0ubuntu3.6_amd64.deb upgrade/updates/libc-dev-bin_2.35-0ubuntu3.6_amd64.deb upgrade/updates/libc-devtools_2.35-0ubuntu3.6_amd64.deb upgrade/updates/libc6-dev_2.35-0ubuntu3.6_amd64.deb upgrade/updates/libc6_2.35-0ubuntu3.6_amd64.deb root@1.srv.node1.node.dyn.kata:~# cd /data/upgrade/ root@1.srv.node1.node.dyn.kata:/data/upgrade# chmod +x ./install_kata_upgrade.sh root@1.srv.node1.node.dyn.kata:/data/upgrade# ./install_kata_upgrade.sh Processing ./kata_license-1.0-py3-none-any.whl Installing collected packages: kata-license Attempting uninstall: kata-license Found existing installation: kata-license 1.0 Uninstalling kata-license-1.0: Successfully uninstalled kata-license-1.0 Successfully installed kata-license-1.0 WARNING: There was an error checking the latest version of pip. Processing ./kata_upgrade-1.0-py3-none-any.whl Installing collected packages: kata-upgrade Successfully installed kata-upgrade-1.0 WARNING: There was an error checking the latest version of pip. Installation was successful! Then execute and wait until completion kata-upgrade --data-dir /data/upgrade/ --password <password of the 'admin' user> <<<<<<<< use ' ' symbols if special symbols are presented in password ............................................................................................................................................................ 2024-09-10 15:46:02,038.38 [kata_upgrade.context.ssh_execution_context][INFO] manager.cluster.dyn.kata: Closed ssh session 2024-09-10 15:46:02,038.38 [kata_upgrade.tasks.upgrade_base_task][INFO] Upgrade task "Update product stack sizing via management api (UpdateSizing)" completed successfully, elapsed time: 896.77 sec 2024-09-10 15:46:02,039.39 [kata_upgrade.updater.updater][INFO] WARNING: Please close all current user sessions to complete the upgrade process. Patch 6.0.1 is installed, you can check it at web UI 6.0.1 > 6.0.2 Upload kata-cn-upgrade-6.0.2-x86_64_en-ru.tar.gz to /home/admin directory Execute following commands below root@1.srv.node1.node.dyn.kata:/data/upgrade# mv /home/admin/kata-cn-upgrade-6.0.2-x86_64_en-ru.tar.gz /data/ root@1.srv.node1.node.dyn.kata:/data/upgrade# tar xvf /data/kata-cn-upgrade-6.0.2-x86_64_en-ru.tar.gz -C /data/ upgrade/ upgrade/images.tar.gz upgrade/install_kata_upgrade.sh upgrade/kata_license-1.0-py3-none-any.whl upgrade/kata_upgrade-1.0-py3-none-any.whl upgrade/ubuntu_image_versions.json upgrade/updates/ upgrade/updates/Packages.gz upgrade/updates/glibc_2.35-0ubuntu3.6.debian.tar.xz upgrade/updates/glibc_2.35-0ubuntu3.6.dsc upgrade/updates/glibc_2.35.orig.tar.xz upgrade/updates/glibc_2.35.orig.tar.xz.asc upgrade/updates/libc-bin_2.35-0ubuntu3.6_amd64.deb upgrade/updates/libc-dev-bin_2.35-0ubuntu3.6_amd64.deb upgrade/updates/libc-devtools_2.35-0ubuntu3.6_amd64.deb upgrade/updates/libc6-dev_2.35-0ubuntu3.6_amd64.deb upgrade/updates/libc6_2.35-0ubuntu3.6_amd64.deb root@1.srv.node1.node.dyn.kata:/data/upgrade# cd /data/upgrade/ root@1.srv.node1.node.dyn.kata:/data/upgrade# chmod +x ./install_kata_upgrade.sh root@1.srv.node1.node.dyn.kata:/data/upgrade# ./install_kata_upgrade.sh Processing ./kata_license-1.0-py3-none-any.whl Installing collected packages: kata-license Attempting uninstall: kata-license Found existing installation: kata-license 1.0 Uninstalling kata-license-1.0: Successfully uninstalled kata-license-1.0 Successfully installed kata-license-1.0 WARNING: There was an error checking the latest version of pip. Processing ./kata_upgrade-1.0-py3-none-any.whl Installing collected packages: kata-upgrade Attempting uninstall: kata-upgrade Found existing installation: kata-upgrade 1.0 Uninstalling kata-upgrade-1.0: Successfully uninstalled kata-upgrade-1.0 Successfully installed kata-upgrade-1.0 WARNING: There was an error checking the latest version of pip. Installation was successful! Then execute and wait until completion kata-upgrade --data-dir /data/upgrade/ --password <password of the 'admin' user> <<<<<<<< use ' ' symbols if special symbols are presented in password ............................................................................................................................................................ 2024-09-10 16:47:24,839.839 [kata_upgrade.context.ssh_execution_context][INFO] manager.cluster.dyn.kata: Closed ssh session 2024-09-10 16:47:24,839.839 [kata_upgrade.tasks.upgrade_base_task][INFO] Upgrade task "Update product stack sizing via management api (UpdateSizing)" completed successfully, elapsed time: 902.25 sec 2024-09-10 16:47:24,840.840 [kata_upgrade.updater.updater][INFO] WARNING: Please close all current user sessions to complete the upgrade process. Patch 6.0.2 is installed, you can check it at web UI 6.0.2 > 6.0.3 https://support.kaspersky.com/KATA/6.0/en-US/286625.htm Upload kata-cn-upgrade-6.0.3.sh to /home/admin Execute following commands below root@1.srv.node1.node.dyn.kata:/data/upgrade# chmod +x /home/admin/kata-cn-upgrade-6.0.3.sh root@1.srv.node1.node.dyn.kata:/data/upgrade# cd /home/admin/ root@1.srv.node1.node.dyn.kata:/home/admin# sh kata-cn-upgrade-6.0.3.sh Check that there are no errors like this root@1.srv.node1.node.dyn.kata:/home/admin# cat /tmp/ks_check_klava_patch.log before total 1016 -rwxr-xr-x 1 root root 561 Nov 15 2023 check_aapt -rwxr-xr-x 1 root root 306 Nov 16 2023 check_aptfr -rwxr-xr-x 1 root root 1592 Nov 15 2023 check_aptfs -rwxr-xr-x 1 root root 1860 Nov 15 2023 check_aptsn -rwxr-xr-x 1 kluser klusers 1011432 Oct 20 2023 check_hips2 -rwxr-xr-x 1 root root 287 Nov 16 2023 check_ksn -rwxr-xr-x 1 root root 409 Nov 15 2023 dispatcher -rwxr-xr-x 1 root root 1315 Nov 16 2023 validate_ioa_rules after total 1016 -rwxr-xr-x 1 root root 561 Nov 15 2023 check_aapt -rwxr-xr-x 1 root root 306 Nov 16 2023 check_aptfr -rwxr-xr-x 1 root root 1592 Nov 15 2023 check_aptfs -rwxr-xr-x 1 root root 1860 Nov 15 2023 check_aptsn -rwxr-xr-x 1 kluser klusers 1011432 Oct 20 2023 check_hips2 lrwxrwxrwx 1 root root 50 Sep 10 16:56 check_klava -> /opt/kaspersky/apt-scan-server/libexec/check_klava -rwxr-xr-x 1 root root 287 Nov 16 2023 check_ksn -rwxr-xr-x 1 root root 409 Nov 15 2023 dispatcher -rwxr-xr-x 1 root root 1315 Nov 16 2023 validate_ioa_rules Patch 6.0.3 is installed, it doesn't change version of product at web UI 6.0.3 > 6.1 Please follow https://support.kaspersky.com/help/KATA/6.1/en-US/243480.htm Known problem: after upgrade to 6.1 kata-collect is not found This is related not only to kata-collect console utility but also other internal console utilities Solution: $ sudo -i Edit /etc/bash.bashrc file # vi /etc/bash.bashrc Enter edit mode by pressing "i" and insert the following line in the very beginning: source /opt/venv/bin/activate Like so: To save press ESC then :wq! and Enter. After that reconnect to server via SSH. Known problem: no space on / at 6.1 sensor nodes after installation Cause: If you do not select any network interface as SPAN then suricata crashes constantly generating core files. To prevent this select at least one network interface for SPAN on sensor nodes. Solution if the problem already occured: Reinstall. Select at least one network interface for SPAN (Program settings → Configure traffic capture → Setup capture interfaces → Mark at least one network interface) If reinstallation is difficult and / is already full and you cannot get into preprocessor_span container to check its / content then: Select at least one network interface for SPAN. Change dir to docker container MergedDir *****@*****.tldr:~# cd $(docker inspect $(docker ps | grep preprocessor_span | awk '{print $1}') | grep Merged | awk -F\" '{print $4}') *****@*****.tldr:/var/lib/docker/overlay2/c3028dde07229aa8fc6f37b7ac2e04b454765b1b015ec9303ac1a35c38ffda38/merged# Check listing, it should contain a lot of core files *****@*****.tldr:/var/lib/docker/overlay2/c3028dde07229aa8fc6f37b7ac2e04b454765b1b015ec9303ac1a35c38ffda38/merged# ls -la | head -20 total 60596 drwxr-xr-x 2 root root 4096 May 18 09:36 drwxr-xr-x 1 root root 4096 Oct 24 11:12 . drwx--x--- 5 root root 4096 Oct 22 14:21 .. drwxr-xr-x 1 root root 4096 Oct 22 14:58 application lrwxrwxrwx 1 root root 7 Apr 25 2023 bin -> usr/bin drwxr-xr-x 2 root root 4096 Apr 18 2022 boot -rw------- 1 root root 11939840 Oct 24 11:10 core.103983 -rw------- 1 root root 11939840 Oct 24 11:10 core.103985 -rw------- 1 root root 11939840 Oct 24 11:10 core.103987 -rw------- 1 root root 11939840 Oct 24 11:10 core.103989 -rw------- 1 root root 11939840 Oct 24 11:10 core.103991 -rw------- 1 root root 11939840 Oct 24 11:10 core.103993 -rw------- 1 root root 11939840 Oct 24 11:10 core.104001 -rw------- 1 root root 11939840 Oct 24 11:10 core.104008 -rw------- 1 root root 11939840 Oct 24 11:10 core.104010 -rw------- 1 root root 11939840 Oct 24 11:10 core.104017 -rw------- 1 root root 11939840 Oct 24 11:10 core.104025 -rw------- 1 root root 11939840 Oct 24 11:11 core.104027 -rw------- 1 root root 11939840 Oct 24 11:11 core.104033 Remove them like so (make sure no unnecessary spaces are in the rm command) *****@*****.tldr:/var/lib/docker/overlay2/c3028dde07229aa8fc6f37b7ac2e04b454765b1b015ec9303ac1a35c38ffda38/merged# rm -f ./core.[0-9]* Reboot

Additionally : " Should it become necessary, the TFU option is switchable between the two. For example, if we have confirmation that a future update will require mandatory restart."

Вот общие рекомендации https://support.kaspersky.ru/common/error/update/13285 про вашему видео ясно только, что при ручном запуске возникает ошибка, но какая не ясно. Это нужно смотреть в отчете

I have downloaded the latest update provided by dm , now internet connection is working but the tools tab remains invisible as before. it looks to be deliberate from kaspersky rather than a glitch. some people have no tools tab on the internet during tutorials and others have it.

Bienvenido a la Comunidad de Kaspersky. Y sí, Kaspersky se autoactualiza a la última versión, pero no de forma inmediata, liberan la nueva versión de forma progresiva, y puede tardar unas semanas desde que sale oficialmente la nueva versión, hasta que la recibes en auto-update en tu aplicación. La mejor manera de enterarte si hay una nueva versión es consultar esta sección del foro, ahí tenemos un hilo fijo situado en la zona superior (pinned), el cual mantenemos actualizado siempre con las nuevas versiones, cambiando el nombre del hilo y su contenido: En cuanto a la última versión del KPM, esta es la que yo tengo: Ah, el Kaspersky Update: https://support.kaspersky.com/es/kuu4-for-windows/new Lo que permite es descargar las bases de datos, para luego actualizar offline el producto seleccionado. Para el KPM puedes revisar: https://support.kaspersky.com/es/kpm-for-windows/25.0/256490 Saludos.

Hello @Бахтиёр The errors "Update file set is corrupted" and "Not all components were updated" suggest issues with the update distribution or compatibility between KSC 15.1 and KES 12.7 on endpoints. Here’s a detailed approach to troubleshoot and resolve these errors: 1. Verify KSC and KES Compatibility Ensure that KES 12.7 is fully compatible with KSC 15.1. Compatibility mismatches can cause update issues. Refer to Kaspersky's compatibility matrix for confirmation. 2. Update the Network Agent If the Network Agent on endpoints is outdated (e.g., older than 15.1.0.2), it may not properly interact with KSC 15.1 or deliver updates correctly. Action: Upgrade the Network Agent on affected endpoints to the latest version supported by KSC 15.1. 3. Recheck Update Sources Confirm that KSC's update repository is correctly configured and not pulling corrupted or incomplete updates. Action: Go to Administration Server → Update → Update sources. Ensure updates are being downloaded directly from Kaspersky's global update servers. 4. Clear and Rebuild Update Storage You’ve already cleared the storage, but let’s ensure it’s thoroughly rebuilt: On the KSC server: Navigate to C:\ProgramData\KasperskyLab\adminkit\1093\updates (default location; path may vary). Stop the Kaspersky Administration Server service. Delete the updates folder. Start the service and re-download updates via Tasks → Download updates. Redistribute updates to managed devices. 5. Check Endpoint Logs Review the update task logs on endpoints to identify specific files or modules causing the "corruption." Go to KES interface → Reports → Update section. Check which files or components failed. 6. Synchronize Endpoint Policies If policies between KSC and endpoints are inconsistent, it can prevent proper update distribution. Action: Reapply and synchronize the policies: Open Policies → Endpoint policy in KSC. Ensure the update task configuration matches your intended setup. Click Enforce synchronization for affected devices. 7. Test with Alternate Update Sources Temporarily bypass the KSC update repository: Configure affected endpoints to download updates directly from Kaspersky's global servers. In KES Settings, change the update source to Kaspersky Lab's servers and test. 8. Verify Disk Space and Permissions Ensure the endpoints and the KSC server have enough disk space and appropriate permissions for update storage. Check: %ProgramData%\Kaspersky Lab\KES\Temp\ on endpoints. Ensure no other software (e.g., antivirus/firewall) interferes with the update process. 9. Debugging Further Run KSC diagnostics for a sample problematic endpoint: Open the Device Properties in KSC for an affected endpoint. Collect logs using the Support Utility (KES trace logs may help identify the root cause). 10. Escalate if Unresolved If the issue persists, collect the following data and contact Kaspersky Support: Full KSC diagnostic logs (klactool utility). Endpoint logs for update tasks. Details about your environment (KSC version, OS versions, update policies). By following these steps systematically, you should be able to pinpoint and resolve the update errors. Let me know if you need help with specific steps! Thank you

@Flood and Flood's wife And in addition, here's the official response from support team (screenshot). Translation: Question: "Is it true that TFU first attempts to upgrade product several times without reboot, and if it fails for any reason, then starts the update method with an OS reboot?" Answer: "Yes, that's correct."

Understood. Well, the only updates were the automatic Windows Update ones. To keep you posted, the error continues even with the wifi driver disabled. I sent the complete memory dump, GSI report, screen record, and other files to Kaspersky support, but I still haven't received an answer. I had to uninstall the Kaspersky app to keep using my computer. Awful!

Patch "B" voor Kaspersky MR22 (21.22.7.466) wordt momenteel uitgerold. De automatische update wordt geleidelijk aan vrijgegeven.

Same here with few computers. OUTLOOK 2019 WINDOWS 11 KASPERSKY ENDPOINT SECURITY for WINDOWS 12.8.xxx and after update 12.9.xxx. I thought the update 12.9 would fix this problem but unfortunately not the case. This problem doesn't exist ~3-4 months ago. Thanks.

I still need to carefully think before anything in upgrading to Wind.11 24h2 since lately this year have been a bad time to to make the changes since there have been seriously problematic update that are sending user's data into void like August 15th update. Anyway I light try to move when Microsoft pronunce about a reliable fix otherwise a fresh installation may break hours of work in installing the new OS. By the way but can I still find useful information on the support about Kaspersky Standard lifetime cycle when it will stop to function on Operating Systems such as mine or untill when will continue to receive updates? However the issues where KS 21.21.7.384 within few days prior that version there other users like myself include getting a hanging with KS when booting or turning on our machines. Since with compulse will to find workarounds, the only way was to wait for about a minute before entering my Windows user entrance. Within KS 21.22.7.466 that issues still remain. Some of the old reports I've listed in the past months about KS 21.21 like occasionally scans mande where not bring saved in the report page. By far till tonight like rootkit/background schedulled evento scan are no longer having this problem. However I've using my compulsive tricks to monitor whether these scans are bring saved in the report page.

Hello @kK574outrider, Also, don't worry about being paranoid - you're not - when computers do weird crap it always feels as IF aliens have taken over! Kaspersky uses a TFU (Total Force *Silent* Update) {version/patch} policy - what does that *translate* to the average user? Patches & versions are distributed by Kaspersky in a staggered distribution, they arrive on our computers & sit in the background for 7 days / 168hours - at the end of that period if the computer has not been rebooted - normally notifications are sent advising the user an update is available & they should reboot the device *however* the process you've experienced sound *normal* but possibly *new*; we've reached out to Kaspersky to see if there's been changes; please wait for feedback. One note please - when posting screen-prints, please *maximise* the image, select the tiny square box🔲 so the image fills the screen - the background is beautiful but is of no interest/use Thank you🙏 Flood🐳+🐋

Hello @kK574outrider, welcome. I actually see a connection with the MR21->MR22 upgrade. The databases in the installer can be a bit older, otherwise you would have to pack a new installer every hour, for example, check it and sign it digitally. With the default settings, an automatic database update takes place after approx. 15 minutes, which you have brought forward with the manual update. Everything is fine.

@Гокюзу Messages from nvlddmkm with ID 153 also started appearing in the OS log. The black screen only occurred randomly and only lasted a couple of seconds. It started after updating my antivirus to 21.22.7.466(a). A week earlier, I installed a 1070Ti with drivers 581.15, and there were no problems. So far, I've found a solution by installing version 537.58 of the graphics card drivers, after cleaning them with the official NVIDIA CleanupTool utility. I'll continue to monitor the issue and gradually upgrade the drivers. Apparently, this is a conflict between the latest antivirus and the driver versions. After all, the graphics cards are quite old, and it might not make sense to update the drivers to the latest versions.

Do You have enabled Kernel Isolation options in Your W11? Also: 12 Ways to Fix Bad Pool Caller in Windows 10/8/7 Restart your computer Undo recent changes to your computer Uninstall recently installed hardware or software Refresh Windows Update all drivers in Windows Run the Windows Memory Diagnostic Check for and repair hard drive corruption Check for and repair corrupted system files Run the Windows BSOD troubleshooter Restore your computer Reset your PC But to fix that specific issue with K. driver, Your best bet is what You already did, contact to K. Support I guess They requested You the full memory dump generated after the BSOD, to analyze it, the fix may take some time.

Advice and Solutions (Forum Knowledgebase) Disclaimer. Read before using materials. Which task is responsible for downloading third party Application updates? Updates metadata is downloaded by Download Updates to the repository task. Updates themselves are downloaded by Install updates and fix Vulnerability task. What is a source folder containing the third party application updates on the administration server? 3rd party updates are downloaded into the folder C:\ProgramData\KasperskyLab\adminkit\1093\.working\wusfiles, then copied to C:\ProgramData\KasperskyLab\adminkit\1093\.working\FTServer to transfer to the hosts. If I run Install updates and fix Vulnerability for Google Chrome as example, all versions of Chrome will be upgraded to the latest release? Which means after a while of running task I will get one version of Google Chrome on all PCs? It depends on settings specified in the install task. For example, if you choose to install all applicable updates, Google Chrome will be updated on all hosts to the latest version. If I have a Connection Gateway, the devices outside the network and connected to the KSC through Connection Gateway will update through KSC or Connection Gateway? Firstly, updates will be transferred to Connection Gateway, then distributed from Connection Gateway to the hosts. So if host needs update which is already on the Connection Gateway, KSC will not distribute files again. CG will distribute them to the hosts. Is it possible for the PCs outside the network and connected through Connection Gateway to use the internet as an update source for third party application? Indeed. 1. On the host with the KSC server, create the following registry key: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\KasperskyLab\Components\34\1093\1.0.0.0\ServerFlags] "KLSRV_SYSPATCH_DOWNLOAD_PATCHES_LOCALLY"=dword:00000001 2. Recreate the Install updates and fix vulnerabilities task.