Released: Feb 26, 2026

Launcher 2025.3.32.0 での更新項目

機能

• Added Devolutions Gateway support to SSH PAM providers.
• Improved double-click behavior in "all vaults" and advanced search to both navigate to folder and launch entries by default.
• Improved how CyberArk session expiration is handled.

不具合の修正

• Fixed 'Mandatory on JIT elavation' issues on a PAM SSH account's checkout.
• Fixed 'Unable to connect to your data source' prompting after losing connection even when you switched to another data source.
• Fixed $SESSION_ID$ returning wrong ID when PowerShell macro is executed from RDP session's context menu.
• Fixed ALT + ASCII code combinations not producing any characters in SSH terminal.
• Fixed connection loss that could occur when refreshing access requests.
• Fixed empty credential names in Passbolt when using encrypted metadata.
• Fixed error in Hub data source when starting an entry from the favorites tab while not in the vault of the entry.
• Fixed error when creating new containers in Azure Blob Storage file explorers.
• Fixed error when opening Teamviewer with a bad ID.
• Fixed host variable resolution issue in website connections when using custom ports.
• Fixed issue where a force refresh is needed to be able to see a PAM provisioner account's password in Hub data source.
• Fixed issue where external RDP connections could fail due to missing a temp folder.
• Fixed issues with SSPI module for SSH entry.
• Fixed Jump sessions failing to launch.
• Fixed loss of connection with the data source triggering resizing issues.
• Fixed missing access rights when working in the User Vault.
• Fixed remote services failing to load.
• Fixed SSH account checkout not working correctly with JIT elevation.
• Fixed SSH Key credentials stored in the User Vault not working correctly when used through inheritance.
• Fixed SSH timeout of 300 seconds not being respected when the connection is really long to establish.
• Fixed the Bitwarden synchronizer creating shortcuts on data sources that do not support them.
• Fixed UPN username format not being applied correctly when using PAM credential entries.
• Fixed VPN auto-close not correctly updating the connection's opened state.