Search the Community

Hello @DigitFish, Welcome! Please share the *full* Win11 25H2 *version & build* information, in Windows *Search* type WINVER, open the WINVER app, post back the information shown in the WINVER popup please? In the troubleshooting & problem determination/steps to resolve - has the computer ever been SHUTDOWN - using the *Shutdown* option - not Restart, a time delay of at least five minutes - then the computer restarted by pressing the power button ON & logging in? For *our* clarity, when (you) say: "Actually when I use Kaspersky Internet Security, sometimes this problem appeared. " - does that mean the red-icon issue pre-existed the install of Kaspersky Standard? Has Kaspersky Standard been fully *uninstalled* using Windows - Add & remove programs, the computer shutdown, using SHUTDOWN - not Restart, powered ON by pressed the power button, logged into & a *new* Kaspersky Standard downloaded & installed from (your) MyKaspersky account? IF 'no', please do this procedure, after installing the *new* Kaspersky Standard, make sure: The Kaspersky Standard is signed into so it synchronises with (your) MyKaspersky account. A Full scan is run. Run a manual Database update -> -> when these steps are complete - shutdown the computer *again*, using SHUTDOWN - not Restart, then power ON by pressed the power button, login, recheck the red-icon? IF the red-icon persists OR returns within the next 48hours & is not related to an app or module-update, log a support request, on the Kaspersky Customer Service page: https://support.kaspersky.com/b2c/global#contacts, select Email & fill in the template as shown; provide a *detailed-history* *Note: do not select the AI-bot to log the case* Please share the outcome with the Community, when it's available? Thank you🙏 Flood🐳+🐋

Configuring KEA update task is of crucial importance. Updated KATA telemetry filters, exclusions and performance optimizations are delivered via bases. However, KEA has no transparent means to check bases version locally. The solution to this demand is to check bases version locally via CLI. KEA for Windows bases date From Elevated Command Prompt, execute: type "C:\ProgramData\Kaspersky Lab\Endpoint Agent\4.0\Bases\Current\aptem.stt" The example output is as follows, ;202209190911 Format is ;YYYYMMDDHHMM KEA for Linux (LENA) bases date Fresh installation For a fresh LENA installation that has never been updated, the bases "aptem.stt" file might be missing. From root or using sudo: sudo cat /var/opt/kaspersky/epagent/update/bases/aptem.stt Output format is the same, ;YYYYMMDDHHMM. Using built-in tools, we can easily make it in a proper way: sudo cat /var/opt/kaspersky/epagent/update/bases/aptem.stt | sed -E 's/\;([0-9]{8})([0-9]{2})([0-9]{2})/\1 \2:\3/g' | xargs -0 date -d Bonus: LENA's Last update date Lena's Last update date is stored in epoch format in /opt/kaspersky/epagent/update/last_update. Using built-in tools, we can make it human-readable: sudo cat /var/opt/kaspersky/epagent/update/last_update | xargs -0 -I% date -d \@% It is also worth mentioning that "Last update date" is relevant but it is still entirely different value than bases date. In case the bases in repository are outdated, Last Update date may be 5 minutes ago, yet bases will remain old.

Hallo . Vor kurzen musste ich meine Windows 21H2 auf 25H2 Version aktualisieren . Dafür musste ich in BIOS TPM2.0 aktivieren . Aktualisierung hat gut geklappt . Aber, so lange ich Kaspersky installiere kommen ständige PC Abstürze wenn Windows neu Update bekommt und versucht die zu installieren . Selbst abschalten vom Antivirusschutz hilft nicht . Nur wenn Kaspersky vollständig deinstalliert wird kann man in Ruhe kommende Update installieren und darnach wieder Kaspersky drauf machen . Dabei kommt von Antivirus die Meldung, das nicht alle Optionen jetzt bei Kaspersky genutzt werden können . Kann mir jemand dabei helfen ?

Update: Heute kam aus der App heraus der Hinweis nach Aktualisierung. Stand heute: Version 11.129.4.15102 Herrlich 🙂

I have been running Kaspersky Endpoint 11.4.0 for Linux on Linux Mint 22.1 and have been telling Kaspersky for two years that they should package their Endpoint for Linux for home users - and after downloading the Kaspersky for Linux install kit and installing it have to say that it looks like that is what they have done. Installation looks almost the same and module names are the same. Not yet having a license I don't know what the Kaspersky for Linux GUI looks like. I attached a picture of the Endpoint window so perhaps someone can say if it's similar. Kaspersky support in late December told me that Kaspersky for Linux is available in the following countries: Australia South Africa Hong Kong Philippines Singapore Azerbaijan Kazakhstan Belarus If you are interested in Kaspersky Endpoint for Linux a license can be purchased from Laptops with Linux in the EU. I don't have the Kaspersky Endpoint kit download links at hand right now to post. [Found it: here] Since I do not live in the EU in order to activate it I had to VPN into the EU - after activation no problem as long as it can access the Kaspersky update servers.

@ooZooN Welcome. Here is the official satement : " Hello, This is due to an update of the VPN infrastructure. All VPN users will see a new agreement in the app which they need to accept. The number of available VPN servers will change from ~105 to ~85, most common servers will remain. The router feature, protocol selection and dual VPN options will disappear. We’re continuing to expand coverage and add new features in upcoming updates. "

Weitere Info: selbst auf meinem Tablet von Xiaomi gibt es Probleme mit dem Update. Es gelingt einfach nicht - so wie auf dem Google Pixel. Lade ich die APK von Kaspersky herunter und installiere diese - nach Anleitung, verbleibt Version 11.129.4.14969. Komische Sache 😕

Huhu Ich bekomme den Hinweis auf ein notwendiges VPN Update im Programm Kaspersky Premium angezeigt, oben in Form eines Briefumschlags. Von dort habe ich nach Anleitung die APK heruntergeladen. Versionssprung, wie gesagt, von 11.129.4.14969-1 auf 11.129.4.14969-2 🙂

So, wie durch ein Wunder bin ich nach wiederholtem herunterladen der APK auf Version Version: 11.129.4.14969-2 (vorher 1!) gelandet. Leider wird mir trotzdem wiederholt angezeigt, dass ein wichtiges App-Update für VPN vorliegt. Nervig 🙂 Ist nun die Frage, ob ich die aktuelle Version für mein Telefon habe oder nicht (auch das VPN betreffend). Wie bereits gesagt, in den Stores von Xiaomi und Samsung wird Version: 11.129.4.15102 angeboten.

Hello @User23837, Thank you for update! You've been an incredibly *proactive* user, personally we wish more subscribers were like you - however - you also need to email thru (your) observations - changes - to the support team - so the data can be recorded in (your) incident request; the 'devs' don't have time to do that, and with the complexities of the VPN transition they've barely had time to scratch-their-ar*es*. The current status for the DNS leak, as advised by Kaspersky is "sorry for any delays, still being worked on". We're delighted to read Fastest-server is fixed by the update. Regarding TLS, please submit that to the Kaspersky Customer Service team, they may ask for data; we *know* raising incidents can be a pain but they're essential for Kaspersky's problem management process -> please post back the INC0000? Thank again🙏 Flood🐳+🐋

Gib es schon Neuigkeiten zu dem VPN Problem? Vielleicht ein Update seitens Kaspersky? Seit Ende November habe ich immer noch kein VPN. Ich kann mich mit keinem Server verbinden und das an allen meinen Rechnern. Habe schon mehrmals beide VPN Programm Versionen ausprobiert: 21.23.6.614-1(a) und 21.23.6.614-2(a) Mein Microsoft Edge und Google Chrome Browser meldet immer noch: ERR_TIMED_OUT Gruß Jan

Thank you for the detailed feedback. Our downloadable Windows tool is also EV code-signed, so if an older unsigned build was involved in the initial detection, it has now been replaced with the clean, signed version. I rescanned the site and the current homepage HTML (SHA-256: 8bc821aca2333a7f3687b2c97aa43cfe63606208570e4e58a4ace734e8ec1f6a) shows 0/61 detections. Could Kaspersky Virus Lab please re-analyse the current version of https://metehanreset.com/ and update the classification if it is now clean? This is a small commercial site for printer maintenance tools and the “Botnet C&C / malware” label is seriously affecting my business. Thank you in advance.

Hello @Clark Welcome back! Correct for both. We submitted a request to update the documentation to reflect Kaspersky Free significant changes - Kaspersky refused stating the product is no longer supported. 🙄 Thank you🙏 Flood🐳+🐋

Hallo, nach dem Update sind alle Favoritenserver weg, nur noch 86 da, kein DOUBLE VPN mehr und auch die anderen Funktionen wie privater DNS, Trackingschutz etc. sind weg, dazu ist die Downloadgeschwindigkeit auf die Hälfte reduziert, über das Update hatte ich schon im englischen Forum gerade gelesen, ist für mich eine Frechheit. Soll das so bleiben ???????????????, dann mal frohe Weihnacht, dann kann man ja gleich zur Freeware greifen. Wird wohl bei Nichtänderung ein neuer Provider gesucht. Da gibt es ja genug.

Hello if your remaining activation code expire. than what will likely to happen: Kaspersky software is highly unlikely to auto renew your activation time. so you cannot perform a databases update after activation expire. and antivirus function stop working. you cannot use the program anymore. you can only choose to uninstall it or buy a subscription.

Just like MH38918 i have the same problem since last update and just like G68 i have the same problem when it connects. I don't know who decided that update but it's really awful and made me think about renewing my subscription with Kaspersky hugely.

Update + Patience + Wait = Success Backup Recovery *for files less than 1TB

Hallo @Benjel, ohne Versionsnummer im Name kann KL stets den selben Downloadlink verwenden und Du landest automatisch bei der letzten verfügbaren Version. Machen wir hier im Forum auch. Wichtig in Deinem Fall ist der erste Teil der Versionsnummer: 11.129. Der Rest ist nicht ganz so wichtig. Die Androidversionen melden sich seit der 126, wenn es ein neues Update gibt und bieten die Installation an.

Thanks for reply. Just now, my Windows prompted me to update. After the update, the quick scan returned to normal. Thank you very much. Could you explain what caused this?

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;'

Having this same issue. I raised a ticket and sent them the necessary info. Waiting on some reply. The connections are all really inconsistent and slow (I get like 200+ ping on a VPN from my home country! wut?). This update definitely broke plenty of things, they're probably aware of it but I haven't seen any official communication on the issues. I recall someone mentioned here even DNS servers are borked, so I guess this update was just rushed and broke so many things. Hopefully something comes up, since this used to be such a reliable and fast VPN compared to so many on the market for me.

I just update it to 11.129.4.146969-1 everything works fine. I thought it just updating by itself