macOS 26 (Tahoe) — Kaspersky Password Manager freezes on launch (“com.kaspersky.kpm.bl.resolver” deadlock)

[m_kurzdym]

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:

 

Quote

blocked by turnstile waiting for launchd [1] send port name "com.kaspersky.kpm.bl.resolver"

 

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)

1. Quit the app completely:

    

   Quote

   pkill kpm

    

2. Remove the broken resolver service:

    

   Quote

   launchctl remove com.kaspersky.kpm.bl.resolver

    

3. Delete the sandbox containers:

    

   Quote

   rm -rf ~/Library/Group\ Containers/*kpm* rm -rf ~/Library/Containers/com.kaspersky.kpm*

    

4. In Finder → Go → Go to Folder… → ~/Library/Containers/
   Delete the folder com.kaspersky.kpm.bl.resolver manually, then empty the Trash.

5. 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)