Выглядит как некорректно записанный образ. Возможно CD с битыми секторами. Или был сбой записи.

Welcome to Kaspersky Community. Yes, for now it is only available for Russia and other eastern countries.

My kaspersky VPN connection is failing. I have full license. it is working on my another laptop but not in my this laptop. both are hp and running windows 11. I have recorded my problem. but can not attach here.

我是创想三维的程序，发布新版本后发现出现个别用户被卡巴斯基拦截的情况。但提交卡巴斯基opentip验证的时候程序是通过的，且本地也复现不了相关拦截问题。图片提供了用户报错，用户版本，软件审核的一些信息。以下是我方程序的下载路径https://cdn.creality.com/ow/official/8ba70475-d5f1-4a3e-8956-c5d50c5b2c3b.exe。

经常玩传奇类私服游戏，但是这类网页经常被劫持，很难清除就选了卡巴优选版试试，结果发现完全扫描不到，不知道怎么解决

@Fon Stephen Cho Also disconnect your W10 device and connect your W11 device in your account.

Hello @Fon Stephen Cho, Welcome! The Kaspersky Plus subscription should be in (your) MyKaspersky account, select the Subscriptions tab: https://my.kaspersky.com/MyLicenses#/portal/pages/licenses - have (you) signed into the account to download & install a new Kaspersky Plus? Read: How to install the application. Thank you🙏 Flood🐳+🐋

Hello everyone, I would like to report a reproducible issue with Kaspersky Password Manager (App Store version 10.3.1) on macOS 26.0.1 (Tahoe, build 25A362). The application freezes immediately upon launch, showing no UI response until forcibly terminated. Observed behaviour After launching, the process kpm_app becomes stuck waiting for a blocked XPC port: This indicates that the app is trying to connect to an unresponsive or missing XPC helper service (com.kaspersky.kpm.bl.resolver), which never responds — resulting in a total freeze. Technical background The App Store build registers an internal XPC service com.kaspersky.kpm.bl.resolver. In macOS 26 (Tahoe), Apple introduced persistent sandbox XPC restoration: even after an uninstall or container cleanup, launchd automatically recreates the service entry on reboot. When that restored service doesn’t respond, kpm_app waits indefinitely on an XPC handshake during initialisation. Workaround (confirmed functional) Quit the app completely: Remove the broken resolver service: Delete the sandbox containers: In Finder → Go → Go to Folder… → ~/Library/Containers/ Delete the folder com.kaspersky.kpm.bl.resolver manually, then empty the Trash. Relaunch Kaspersky Password Manager. The app now starts and synchronises correctly. (Optional: create an empty file /Library/LaunchDaemons/com.kaspersky.kpm.bl.resolver.plist with zero permissions to prevent macOS from resurrecting the broken helper on next boot.) Expected behaviour The application should initialise its XPC connection dynamically during launch instead of relying on a persistent launchd registration that can become invalid in new macOS sandbox environments. Environment Component Version macOS 26.0.1 (Tahoe, build 25A362) Hardware MacBook Pro 16,1 – Intel i9 Password Manager 10.3.1 (App Store build) Distribution Mac App Store Reproducible Always, especially after restart Summary This appears to be a compatibility issue between the App Store sandbox and macOS 26’s updated XPC system. Removing or resetting the com.kaspersky.kpm.bl.resolver endpoint resolves the problem entirely. Please forward this to the macOS development team for validation and patching in the next release. Best regards, M. Kurzdym, PhD (UK)