Search the Community

Es scheint wirklich wieder zu funktionieren mit dem neuen Update.

Gibt es irgendwelche Möglichkeit, nach diesem neuem Update, das VPN zu erstellen, ohne den Standort mitzuteilen?

I can confirm that for me the issue seems to be solved, i had an app update on the 16th of November and now i'm at 21.23.6.614, prior to this i had installed back in September the 21.22.7.466 version. I now have 0-1% GPU usage in Idle and no Kaspersky is consuming GPU. @Mohamed, i'd suggest reinstalling the app, do a complete uninstall, i remember back in the days Kaspersky had a removal tool of their own, perhaps that does a more in-depth removal then the Uninstall process from appwiz.cpl, idk, look it up and try. But what i can say from my side, after the update to 21.23 on the 16th of November, the GPU load in Idle is how it should be.

I have reinstalled via the link in the red "update to the latest version" box at the top of the page and it has installed the same version (21.23.6.614-2)

You can install this below version Kaspersky VPN Latest Version This version also solves many issues related to Kaspersky VPN , you can give a try and share the update with us.

Здравствуйте. Я бы пошел по такому пути: 1. Создание резервной копии в 14.2 (базу данных не меняем); 2. Обновление поверх до 15.1 (update 2). Необходимо убедиться заранее, что версия MS SQL не ниже 2016 версии и с последним CU; 3. Создание резервной копии в 15.1 со сменой типа СУБД; 4. Удаление MS SQL, переустановка KSC, создание бустой базы в MySQL 5. Восстановление из резервной копии на шаге 3.

Issue "Databases and modules update task" is configured for hosts with LENA 3.12 installed. Task is executed via KSC. Diagnostics "Activate KEA" task is configured for the hosts with LENA or has been configured and deleted in the past. An update is executed locally, using lenactl works. KLNagent successfully synchronizes with the server. Other installed applications (e.g. KESL) display no synchronization issues. Workaround To fix the issue: Remove the "Activate KEA" task or any other configured KEA tasks except for "Databases and modules update task" for hosts with LENA installed. If necessary, move hosts with LENA to a separate group or configure other desired KEA tasks using a selection for Windows hosts only. Ensure there are no tasks except for "Databases and modules update task" remaining for hosts with LENA installed in KSC. Option A. Reinstall LENA on hosts to get rid of cached activation tasks. Option B. Remove the problematic cached tasks locally: Stop LENA: # systemctl stop epagent Remove the cached tasks: # rm -rf /var/opt/kaspersky/epagent/tasks/* Start LENA # systemctl start epagent Force synchronization with the host, e.g. by calling klnagchk. # /opt/kaspersky/klnagent64/bin/klnagchk Ensure one task is recieved. # ll /var/opt/kaspersky/epagent/tasks/ Execute "Databases and modules update task" on KSC. Ensure it finishes successfully. Double check locally that the bases are updated. RCA LENA connector that receives the product tasks from KLNagent is only configured to accept valid tasks ant halt synchronization if an invalid task is received. Only "Databases and modules update task" is considered to be valid for certified LENA version. "Activate KEA" task is received or cached first. Connector halts synchronization once it is processed. An update task is never received by the product.

The table below contains the criteria for Kaspersky Security for Microsoft Exchange Servers 9.0 MR6 settings health check. Using the settings as specified in the table ensures meeting the recommended security level of the system. № Parameters (settings) to check Check criterion Expected result 1 Anti-Virus protection for the Transport Hub role 1.1. Anti-Virus protection is enabled In the node Server protection → Protection for the Transport Hub role → Anti-Virus scan settings the Enable anti-virus protection for the Hub Transport role option is selected 1.2. The Delete object action has been set for infected objects In the node Server protection → Protection for the Transport Hub role → Anti-Virus scan settings the Delete object option is selected for infected objects 2 Virus scan of mailboxes 2.1. Scan is enabled In the node Server protection → Protection for the Mailbox role → Anti-Virus scan settings the Enable anti-virus protection for the Mailbox role option is selected 2.2. The Delete object action has been set for infected objects In the node Server protection → Protection for the Mailbox role → Anti-Virus scan settings the Delete object is selected for infected objects 2.3. Periodic scan task run has been configured In the node Server protection → Protection for the Mailbox role → Protection for mailboxes all required mailbox storages are selected (Protected mailbox storages) the task schedule has been defined (Background scan → Schedule) 3 General Anti-Virus protection settings 3.1. Interaction with KSN (KPSN) is enabled for the Anti-Virus module In the node Settings → KSN Settings the I accept the KSN Statement option. Use Kaspersky Security Network or Use Kaspersky Private Security Network (KPSN) option is selected In the node Server protection → Advanced Anti-Virus settings the Use Kaspersky Security Network option is selected 3.2. Scanning of archives and containers is enabled In the node Server protection → Advanced Anti-Virus settings the Scan attached containers/archives option is selected the default value (32) is set for the Scan attached containers/archives with nesting level not higher than setting 4 Anti-Spam and Anti-Phishing scan Anti-Spam parameters are configured 4.1. Anti-Spam is enabled In the node Server protection → Protection for the Transport Hub role → Anti-Spam scan settings the Enable anti-spam scanning of messages option is selected 4.2. SCL rating is in use (only if the "Skip" action is selected) In the node Server protection → Protection for the Transport Hub role → Anti-Spam scan settings the Add SCL value option is selected for Spam, Potential spam and Blacklisted If mass mailings need to be put into the spam folder: the Add SCL value option is selected for Mass mailing Anti-Phishing parameters are configured 4.3. Anti-Phishing scan is enabled In the node Server protection → Protection for the Transport Hub role → Anti-Spam scan settings the Enable anti-phishing scanning of messages option is selected 4.4. SCL rating and PCL rating are in use (only if the "Skip" action is selected) In the node Server protection → Protection for the Transport Hub role → Anti-Spam scan settings the Add SCL and PCL rating option is selected for Phishing Parameters for interaction with KSN (KPSN) are configured 4.5. Interaction with KSN (KPSN) for Anti-Spam and Anti-Phishing scans is enabled In the node Settings → KSN Settings the I accept the KSN Statement option. Use Kaspersky Security Network or Use Kaspersky Private Security Network (KPSN) option is selected In the node Server protection → Protection for the Transport Hub role → Anti-Spam scan settings the Use Kaspersky Security Network option is selected 4.6. Reputation Filtering service is enabled (only if there is interaction with KSN) In the node Server protection → Protection for the Transport Hub role → Anti-Spam scan settings the Use Reputation Filtering option is selected 4.7. Enforced Anti-Spam Updates Service is enabled In the node Server protection → Protection for the Transport Hub role → Anti-Spam scan settings the Use Enforced Anti-Spam Updates Service option is selected 5 Database update and network settings 5.1. Automatic update of anti-virus databases is enabled Recommended interval – 1 hour In the node Updates → Update databases of Anti-Virus → Run mode the Periodically value is set to every hour 5.2. Automatic update of Anti-Spam databases is enabled Recommended interval – 5 minutes In the node Updates → Anti-Spam databases update → Run mode the Periodically value is set to every 5 minutes 5.3. Proxy server has been configured for database update (if update sources are accessed through a proxy) In the node Settings → Proxy server settings proxy server settings have been defined In the node Settings → Connection settings the Use proxy server option is selected 5.4. Proxy server has been configured for KSN and the Enforced Anti-Spam Updates Service (if KSN is accessed through a proxy) In the node Settings → Proxy server settings proxy server settings have been defined the Use a proxy server to access KSN, Enforced Anti-Spam Updates Service, and Kaspersky Lab activation servers option is selected 6 Licensing License key is active In the node Settings → Licensing the license key has an active status

Advice and Solutions (Forum Knowledgebase) Disclaimer. Read before using materials. If two different update agents on a PC are assigned in different ways: To an administration group. Based on a network location. Which one will have a higher priority for the PC? Among the update agents assigned to administration groups, the one assigned to the administration group, that is closest to the target host in the group hierarchy, has the higher priority. If the update agents are assigned to the same group, they have an equal priority. The priority of update agents assigned based on the network location is equal to the priority of the nearest update agent in the group hierarchy. If two update agents have the same priority, the one, the route to which is closer in the number of passed routers, is selected. If two update agents have the same priority and the network distance to them is the same, the agent is selected randomly.

KATA 4.0/4.1 is compatible with KSMG 2.0, KSMG 1 and KLMS 8.0.3. Second thing to notice is that KSMG integration has a few bugs on KATA side. Thankfully, all known issues are fixed in a PF, which is recommended for all who integrate KSMG/KLMS and KATA4. KATA4.0 Step-by-step guide Download container with fix. file_name : kata_scanner_35f8753e6d.tar.gz md5 : 2adb09c0bd13dfc03c6a5c8980dde4ff container_name: kata_scanner container_version: kata_scanner:35f8753e6d service_name: kataedr_main_1_kata_scanner Copy file kata_scanner_35f8753e6d.tar.gz to KATA CN check md5: md5sum /var/opt/kaspersky/apt/files/kata_scanner_35f8753e6d.tar.gz MD5 should be 2adb09c0bd13dfc03c6a5c8980dde4ff, after that import the container, no need to decompress: docker load < /var/opt/kaspersky/apt/files/kata_scanner_35f8753e6d.tar.gz If the load is successful, the result would be the the container version, like kaspersky/kata/kata_scanner:35f8753e6d Change container tag in /etc/opt/kaspersky/apt-swarm/image_versions.json to the new version (kata_scanner:bb3be18444 -> kata_scanner:35f8753e6d) "kata_scanner": "kaspersky/kata/kata_scanner:35f8753e6d", Update the image used for service kata_scanner by running the command: docker service update kataedr_main_1_kata_scanner --image "kaspersky/kata/kata_scanner:35f8753e6d" To verify that kata_scanner service runs new container, run: docker service ls | grep kata_scanner Sample output, note container version 4up6sm5yetnj kataedr_main_1_kata_scanner replicated 1/1 kaspersky/kata/kata_scanner:35f8753e6d *:8081-8082->8081-8082/tcp КАТА 4.1 Fixing mail processing Step-by-step guide Download container with fix. file_name : kata_scanner_66e20ed.tar.gz md5 : 288ddb650ed9c08ca1fe57e188c41c67 container_name: kata_scanner container_version: 66e20ed service_name: kataedr_main_1_kata_scanner Step-by-step: kata_scanner Download a container. Copy the file kata_scanner_66e20ed.tar.gz to KATA CN. Check md5: md5sum /var/opt/kaspersky/apt/files/kata_scanner_66e20ed.tar.gz MD5 should be 288ddb650ed9c08ca1fe57e188c41c67. After that, load the container, no need to decompress: docker load < /var/opt/kaspersky/apt/files/kata_scanner_66e20ed.tar.gz If the load is successful, the result would be the container version, like Loaded image: kaspersky/kata/kata_scanner:66e20ed Use it to change the container version in /etc/opt/kaspersky/apt-swarm/image_versions.json. Set the correct version: "kata_scanner": "kaspersky/kata/kata_scanner:66e20ed", Confirm that the changes are correct and are not breaking anything: cat /etc/opt/kaspersky/apt-swarm/image_versions.json | python -m json.tool | grep "kata_scanner:" Update the image used for the kata_scanner service with the new version of the container that we have just added: docker service update kataedr_main_1_kata_scanner --image "kaspersky/kata/kata_scanner:66e20ed" Verify that the kataedr_main_1_kata_scanner service runs the new container by running: docker service ls | grep kata_scanner Confirm the new version tag 66e20ed: Sample output, note container version mtgzlqu3beny kataedr_main_1_kata_scanner replicated 1/1 kaspersky/kata/kata_scanner:66e20ed *:8081-8082->8081-8082/tcp Fixing autoprevention rules for composite objects step-by-step guide Download container with fix. file_name : hunts-fixed-prevs.tar.gz md5 : 604d0918ddcb8b91cac694a15d96d501 container_name: hunts_event_processor container_version: 2610c63 service_name: kataedr_main_1_hunts_event_processor Copy file hunts-fixed-prevs.tar.gz to KATA CN (e.g via scp) check md5: md5sum /var/opt/kaspersky/apt/files/hunts-fixed-prevs.tar.gz MD5 should be 604d0918ddcb8b91cac694a15d96d501, after that import the container, no need to decompress: docker load < /var/opt/kaspersky/apt/files/hunts-fixed-prevs.tar.gz If the load is successful, the result would be the the container version, like kaspersky/kata/hunts_event_processor:2610c63 Change container tag in /etc/opt/kaspersky/apt-swarm/image_versions.json to the new version (hunts_event_processor:0e5fabb -> hunts_event_processor:2610c63) "hunts_event_processor": "kaspersky/kata/hunts_event_processor:2610c63", Check that json is changed and valid (outputs the string from previous step if all is ok): cat /etc/opt/kaspersky/apt-swarm/image_versions.json | python -m json.tool | grep 2610c63 Update the image used for service kata_scanner by running the command: docker service update kataedr_main_1_hunts_event_processor --image "kaspersky/kata/hunts_event_processor:2610c63" Expected output "verify: Service converged" To verify that kata_scanner service runs new container, run: docker service ls | grep hunts_event_processor Sample output, note container version r8m0jcrtkiu0 kataedr_main_1_hunts_event_processor replicated 1/1 kaspersky/kata/hunts_event_processor:2610c63 Fixing dashboards step-by-step guide For dashboards, two containers should be replaced: web_backend and clickhouse_metrics_importer. Service name Container name Download link kataedr_main_1_web_backend kaspersky/kata/management/management_ui/web_backend:4e30ad8 https://box.kaspersky.com/f/d66c6aa3ebe1483c9558/?dl=1 kataedr_main_1_clickhouse_metrics_importer kaspersky/kata/clickhouse_metrics_importer:0e5fabc https://box.kaspersky.com/f/fe0e562798fe4d1e9730/ Please replace them both as per instructions above. This cumulative fix container should be applied to all installations. https://box.kaspersky.com/f/d66c6aa3ebe1483c9558/?dl=1 file_name: web_backend_4e30ad8.tar.gz md5: 9aa87ce646c28cc30f5002f837d10104 container_name: web_backend container_version: "kaspersky/kata/management/management_ui/web_backend:4e30ad8" service_name: kataedr_main_1_web_backend Step-by-step: web_backend Download a container. Check md5: md5sum /var/opt/kaspersky/apt/files/web_backend_4e30ad8.tar.gz MD5 should be 9aa87ce646c28cc30f5002f837d10104. After that, load the container: docker load < /var/opt/kaspersky/apt/files/web_backend_4e30ad8.tar.gz If the load is successful, the result would be the container version, like Loaded image: kaspersky/kata/management/management_ui/web_backend:4e30ad8 Use it to change the container version in /etc/opt/kaspersky/apt-swarm/image_versions.json. Set the correct version: "web_backend": "kaspersky/kata/management/management_ui/web_backend:4e30ad8", Confirm that the changes are correct and are not breaking anything: cat /etc/opt/kaspersky/apt-swarm/image_versions.json | python -m json.tool | grep "web_backend:" Reload the docker service with the new version of the container that we have just added: docker service update kataedr_main_1_web_backend --image "kaspersky/kata/management/management_ui/web_backend:4e30ad8" Verify that the kataedr_main_1_web_backend service runs the new container by running: docker service ls | grep kataedr_main_1_web_backend Confirm the new version tag 4e30ad8: Sample output, note container version 5nb5ghavmtl5 kataedr_main_1_web_backend replicated 1/1 kaspersky/kata/management/management_ui/web_backend:4e30ad8 KSMG You should add vacuum command to the crontab and run it every 6 hours Cron scheduler should be added similar to this (under root): For KSMG 2.0.1 there is no need to add this command to cron. KSMG 2.0 $ sudo -i # crontab -e # Run at minute 0 past every 6th hour: 0 */6 * * * /opt/kaspersky/ksmg/libexec/postgresql/psql -h /var/run/ksmg -U kluser -d kata_quarantine -c 'vacuum full;' KSMG 1.1.2.30 $ sudo -i # crontab -e # Run at minute 0 past every 6th hour: 0 */6 * * * /opt/kaspersky/klms/libexec/postgresql/psql -h /var/run/klms -U kluser -d kata_quarantine -c 'vacuum full;'

I am on the latest Windows update, yes. Technical support will not help because the problem is with the servers/software and not my configuration. I have dealt with tech support. Their modus operadi is to make the user think that the problem lies with them and not the service. I'm not playing that game.

@TAE I understand your dissatisfaction but Kaspersky Technical Support is your best option. I assume that you are on the latest Windows update ?

Hallo @LeuchtBall, willkommen. Kannst Du bitte schildern, welchem Programm Du wie den Internetzugriff gesperrt hast? In Deinem Screenshot scheint es mir nicht das Corel-Hauptprogramm zu sein, sondern ein Hilfsprogramm (Corel Update Helper x32). Kannst Du bitte über das Hauptfenster links "Sicherheit" auswählen, dann rechts etwas nach unten scrollen und "Programmüberwachung->Programme verwalten" anklicken? Im Idealfall haben die Corelkomponenten eine eigene Gruppe, wie in untenstehendem Beispiel Firefox in "Mozilla". Kannst Du dort den "Corel Update Helper x32" finden? Wie sind seine Einstellungen (Doppelklick auf das Programm)? Screenshot?

All of Windows Apps that require Internet, even prompts to login to MS account, failed as they couldn't detect internet connection. This was all of a sudden. I have windows 11 to the last cumulative update. Afeter trying so many things, like desactivate PROXY, change DNS, disable Kaspersky VPN, and suspend Kaspersky protection. Nothing worked. Finally the issue was gone when I uninstalled Kaspersky Security; VPN and password manager. I have time of subscription left still, and I need an antivirus. What could have happened with the Kaspersky apps to cause this, and is there a configuration which avoids this issue? Thanks

Hello Why does Indonesian break after every update? Why do we experience this every time? I've been waiting for you to fix this for 3 days. Don't you test anything before updating? I only use it for Indonesian. But this is really starting to get annoying!!!!

Update your Server 2019 to latest update patch and try reinstalling Netagent or run KVRT before installing Netagent , have you raised ticket on Kaspersky Support , what was their feedback

We use Kaspersky Endpoint Security Cloud and the instructions included installing through Intune. There was no agent to install, they simply suggested pushing out the entire distribution package through intune. This worked out fine, but now there is a new version (12.10.0.466). If I 'prepare the distribution package' it will automatically start updating clients, but this is problematic. Intune is setup to detect the install of version 12.9. Am I supposed to disable this pushed install entirely when we need to update? Is there a way to get this package without pushing it to all users? I would much rather let intune handle this so that future intune devices also get the latest Kaspersky app. The only way around this that I can see is to disable the intune install, push out the new package, immediately download said package and create a new intune install. But what happens? Intune is going to try and install the update at the same time as Kaspersky cloud, which I have to imagine is going to cause all sorts of grief. Is there a better way to handle this? Like an agent I can push through intune that doesn't install the app until the cloud console tells it to? That is how ESET handled things and we never had to worry about it. If anyone else uses Intune please let me know how you handle this

Bin noch auf 24h2. Es könnte gut sein dass sich beim Windows Update was verschluckt hat und ein Darüber installieren von Kaspersky es löst, war bei mir die Lösung damals.

Good day, @Impulse9 and @mokaz, thank you for coming back with an update, and I appreciate you taking the time to explain your perspective so clearly. I understand why this situation is especially disappointing after many years of using the service without issues. When a product becomes part of someone’s daily routine, any major change can feel abrupt and unnecessary. Your feedback regarding transparency, troubleshooting guidance, and expectations management is very valuable, and I will make sure it is passed on to the relevant teams. Even when users decide not to continue with a service, these insights help us identify where we need to improve: not only technically, but also in how we communicate during major changes. I sincerely hope that we’ll be able to earn back your trust in the future, and thank you again for the years you spent with our service and for sharing such thoughtful feedback here. Good day, @Kyrillos.Zak, thank you for your question. I understand the confusion, and I’m happy to clarify. This does not mean that all global issues are fully resolved or that the problem is necessarily limited to your account or your PC. Additional information helps the technical team verify whether the behavior matches known service-side limitations or regional conditions, and check if there are any account or device-specific factors contributing to what you’re experiencing. In some cases, we may be able to provide a workaround or solution even while broader issues are still being addressed.

Advice and Solutions (Forum Knowledgebase) Disclaimer. Read before using materials. This article is about Kaspersky Endpoint Security for Windows (KES for Windows) This informational message does not mean that Self-Defense accuses any process of being under malware attack, it proactively blocks certain operations that could pose a potential threat to processes. The number of events depends on the activity of applications that inhabit the system, especially from their periodic activities, polls on a timer, on emerging events, and so on. The event in the reports is informational - it can be simply disabled it in the settings. It's not expected to react to these events. More specifically, it's usually the update programs and VMWare services try to access application processes. The update programs want to restart all processes when the update is finished so that they don't have to reboot the system. But KES doesn't allow them to restart our processes. The applications causing these events: Microsoft Edge Update Google Installer Windows installer VMware Authorization Service Host Process for Windows Services Client Server Runtime Process It is normal for such a request to fail, and this should not be a concern. These events can be turned off in active KES policy: General settings→Interface→Notifications: informational messages→Self-Defense restricted access to the protected resource.

Bei mir funktioniert Kaspersky Premium VPN seit ende November 2025 nicht mehr: Ich habe ende November vom Kaspersky eine E-mail erhalten: __________________________________________________________________________________________________________________________ Wichtige Informationen über Ihr Kaspersky VPN Sehr geehrter Kunde, bitte beachten Sie, dass wir derzeit Kaspersky VPN auf eine neue Infrastruktur umstellen, um allen Benutzern ein reibungsloses und zuverlässiges Erlebnis zu gewährleisten. Während einer kurzen Übergangszeit können vorübergehende Probleme auftreten. Diese Probleme können Benutzer von Kaspersky VPN Secure Connection, Kaspersky Plus und Kaspersky Premium betreffen. Wir tun unser Bestes, um alle Probleme so schnell wie möglich zu lösen. Die meisten Benutzer erhalten das erforderliche Update automatisch. Sollten dennoch Probleme auftreten, aktualisieren Sie die App bitte auf allen Ihren Geräten auf die neueste Version. Die neueste Version können Sie hier herunterladen: Aktualisierung Wir möchten uns für eventuelle Unannehmlichkeiten entschuldigen und arbeiten mit Hochdruck an deren Lösung, Ihr Kaspersky-Team _______________________________________________________________________________________________________________ Ich habe die neueste Ver. installiert. Nicht nur einmal und auf allen meinen drei Windows Desktop PC. Nichts geht mer mit VPN. Habe support kontaktiert und mehrere Stunden und Tage am PC gesessen um die "Tipps" vom Support (Programme installieren, Aufzeichnungen zurück schicken, das und jenes aus- und einschalten). Auch das hat nichts gebracht. Dann kam eine E-mal: _____________________________________________________________________________________________ Sehr geehrter Kunde, Guten Tag. Vielen Dank für die Rückmeldung. Tut uns wirklich leid für die Unannehmlichkeiten. Als kleines Dankeschön für Ihre Treue, haben wir 14 Tage auf Ihre Lizenz hinzugefügt. Wir haben Ihre Anfrage an unseren Experten weitergeleitet, bitte warten Sie auf unsere Antwort. Für weitere Rückfragen stehen Ihnen unser Kaspersky-Support zur Verfügung. Ich wünsche Ihnen noch einen schönen Tag. ____________________________________________________________________________________________ Paar tage später kam eine weitere E-mail: _________________________________________________________________________________________ Sehr geehrter Kunde, Guten Tag. Wir erhielten die Rückmeldung von unseren Experten. 1. Da es sich hierbei um ein Problem seitens des Internetdienstanbieters handeln könnte, verbinden Sie sich bitte mit einem anderen Netzwerk, beispielsweise über eine mobile Hotspot-Verbindung: a. Android: https://support.google.com/android/answer/9059108?hl=de b. Apple iOS: https://support.apple.com/de-de/HT204023 ............ mit weiteren Punkten (ca. 20) die sich wiederholt haben mit denen, die ich schon frühe durchgegangen bin. _____________________________________________________________________________________ Mein Handy ist sehr alt und kann keine Hotspot-Verbindung herstellen. Apple habe ich nie gehabt. Und das wiederholen der selben procedur ist sinnlos. Ich war mit Kaspersky schon mehrere Jahre sehr zufrieden. Ich habe auch gute Erfahrungen mit Kaspersky VPN gemacht, bis die Umstellung auf die neue Infrastruktur kam. Für mich war VPN wichtig da ich meinem Besuch auch TV Streaming für deren Sprache anbieten konnte. Andersrum, ich habe für ein funktionierendes Paket von Kaspersky Premium bezahlt und jetzt soll ich mehrere Stunden und Tage meines Lebens am PC sitzen um die Probleme zu erörtern? Mein Abo läuft noch fast ein Jahr, trotzdem überlege ich, ob ich Kaspersky kündigen soll. Ich bin kein Informatiker, und ich möchte auch nicht mein PC mit mir vorgeschlagenen Programmen vermüllen. Ich bin sauer und von Kaspersky enttäuscht.

I found this topic whilst searching for a way to make the update window smaller. It seems it can not be done below 1 hour. I just wanted to know the automatic default, so it's indeed every 2 hours? OK so 1 hour is faster than that, I set to 8am every hour and 2 minutes after app start as I don't see the point of the delay with that which defaulted to 15 minutes. Honestly, I would prefer setting the update schedule to every 15 minutes and I think Kaspersky should allow the paranoid user like myself to set it that frequently, as what can it harm? it's not as if it causes any network slowdown or PC performance issues. Nevertheless, I do run an update myself before every manual scan, so that brings another thing. When we right click the K icon in taskbar, I think a very easy option to add and a very useful one would be to have an update shortcut. So we can just right click icon and update. No? Any reason why this would be a bad idea? The way it is now I have to open the interface and navigate to the security tab and click update. It's not the end of the world, just could be really easy with a shortcut in the right click menu. There are so many other things you can do there, like exit, pause protection etc, I think an update option would be great. Edit: Typos

Since the new update it's been pretty chaotic. This update (21.23.6.614-2) introduced WireGuard-based VPN tunneling for improved speed and stability but it also seems to have broken DNS resolution. I have Android and windows devices with this VPN and they all have the same problem. If you are comfortable, you can try changing the DNS with 1.1.1.1 and/or 8.8.8.8 on the Kaspersky VPN WG Nt Adapter Tunnel to test it out. BUT I do not recommend this as a work around as this may leave you vulnerable for data leak. Make sure you let support know by creating a ticket and mention the known issue for version 21.23.6.614-2

One of the latest messages I got... So, they are trying to offer me a downgraded version to use in the territory of the Russian Federation. What about when I'm abroad? Should I buy another VPN just because the one that they offer me now doesn't works abroad? When this problems started on November they patched and the VPN worked well till the next update on December 12th.

Good day, @Kyrillos.Zak, we understand how frustrating this situation can be. To continue the investigation and move it forward, our technical support team needs the additional information previously requested. As soon as we receive these details, we’ll be able to analyze the issue further and provide an update. Thank you for your cooperation, it will help us resolve this faster.