@Гризли, напишите, пожалуйста, в поддержку через https://support.kaspersky.ru/b2c и пришлите мне в личные сообщения номер инцидента.

ну у меня по прежнему ничего и никуда не подключает. А те сервера которые подключает (самый быстрый) - ничего не грузит. Никакой сайт.

Я ж сказал, сразу всё тут описали и обмусолили до нельзя. Конечно сейчас программа работает уже не так как раньше, нет много возможностей,ютуба, но тем не менее работает по крайней мере

Hello dggbg, the described situation is a known problem with KSC Linux 16.0. Web console checks for available space in /tmp (but does not utilize it). As per system requirements, Web Console should only utilize /var/opt/kaspersky. This known issue should be fixed in KSC 16.1. Unfortunately i do not have a time frame Workarounds: - Add 10GB disk space in /tmp mount point (this may require 10GB RAM in systems where tmp is mounted as tmpfs) OR - Disable separate /tmp mount point Hope that helps for now Best Regards

заработало что-ли? Так какая причина была?

Hello, sounds like Bitlocker is already in use. Cloud Version only use Bitlocker. If it was enabled by others before you have to decrypt it before using Bitlocker settings from Cloud Console. Use command manage-bde -status to check the drive and manage-bde -off to decrypt it. Make sure the client has a connection to the cloud server when activating encryption in cloud console

Мне всё сделали оказывается сегодня, спасибо поддержке по емэйлу. Ну так и есть - причину на форуме сразу выявили.

1. Yes. I sent them a very similar message to the one I posted to start this forum post. I told them that the current web based support page still lists 13+ and then linked them to that page. I also mentioned that the appstore page now contradicts that and states 14+ and will not allow a download to start on a MacBook with an OS under 14. 2. PureVPN specifically? I couldn't possibly say. I believe I mentioned that most other VPNs on the appstore still work with MacOS13. 3.INC000017945215 Thanks for the help, but I am probably going to leave it here. The small amount of money I would've saved by getting the VPN working again isn't worth me spending anymore time on this issue, but maybe this thread can help out someone else with a similar use issue.