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)

[Flood and Flood's wife]

14 hours ago, m_kurzdym said:

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.

Hello @m_kurzdym, 

Welcome!

Please read: KPM for Mac, Hardware and software requirements.

Thank you🙏
Flood🐳+🐋

[m_kurzdym]

Hello,

 

Thank You for Your reply.

 

The article You’ve shared refers only to hardware and software requirements for macOS versions up to 15, while this report concerns a confirmed reproducible issue on macOS 26.0.1 (Tahoe, build 25A362).

 

After detailed analysis, I’ve identified the exact cause — the new XPC handling in macOS 26 interferes with the com.kaspersky.kpm.bl.resolver endpoint. This results in Kaspersky Password Manager freezing immediately after launch.

 

Removing or resetting that endpoint restores full functionality and stability.

 

I would kindly ask You to forward this finding to the macOS development team so that it can be validated and patched in an upcoming release. Including this fix or a related note in the official documentation could also help other users who may experience the same issue.

[Flood and Flood's wife]

29 minutes ago, m_kurzdym said:

The article You’ve shared refers only to hardware and software requirements for macOS versions up to 15, while this report concerns a confirmed reproducible issue on macOS 26.0.1 (Tahoe, build 25A362).

Hello @m_kurzdym, 

You're most welcome!

Thank you for posting back!

Correct, Kaspersky's documentation is for macOS currently supported by Kaspersky, macOS 26.0.1 (Tahoe) is not yet supported. 

To set *your* expectations, Kaspersky Community/Forum members don't action *escalation* requests on behalf of other users - IF the support team need to ask questions & OR interrogate data/logs etc - the Kaspersky Community/Forum member(s) will not be able to assist - as *you* are the source (of the information); (you're) more than welcome to raise the issue with Kaspersky Customer Service, https://support.kaspersky.com/b2c#contacts -> select Email, fill in the template as shown; provide a *detailed-history*, the support team will engage & assist:

Please share the outcome, with the Community, when it's available. 

Thank you🙏
Flood🐳+🐋

Edited 1 hour ago by Flood and Flood's wife
pn

[m_kurzdym]

Thank You for the clarification.

I understand that macOS 26.0.1 (Tahoe) is not yet officially listed as supported, but since the underlying issue affects Kaspersky’s background XPC resolver, it may become relevant once official compatibility is declared.

I’ll follow up with the Customer Service team directly and provide all technical details and reproduction logs for their review.

Thank You again for Your time and assistance.