Omnissa Horizon Client for Windows Release Notes

Horizon Client for Windows 2606 | 24 AUG 2026
With Horizon® Client™ for Windows 2606, you can access remote desktops and published applications from your Windows computer with the best possible user experience on the Local Area Network (LAN) or across a Wide Area Network (WAN).
IMPORTANT NOTICE: Changes to Support Lifecycle Dates
Effective with Horizon Client version 2606, the End of Availability (EOA), End of General Support (EOGS), and End of Technical Guidance (EOTG) milestones for this client changed from the previous policy to the policy shown below.
Note: The support policy for versions before 2606 remains unchanged.
Milestone
----------
EOA / EOGS
EOTG
What’s New

• True SSO unlock now supports any third-party SAML Identity Provider, in addition to Workspace ONE Access. The Identity Provider must support SP-initiated SSO using the HTTP POST binding for AuthnRequests.
• Horizon components have been updated to use OpenSSL 3.5, replacing the previous OpenSSL 3.0.x libraries which are approaching end of life. This includes the Blast Secure Gateway (BSG) for both Connection Server and Unified Access Gateway (UAG). Before You Begin
• For the Windows operating systems that this release of Horizon Client for Windows supports, see the Horizon Client for Windows Guide.
• Horizon Client for Windows is supported with the latest maintenance release of the following deployment types:
  • Omnissa Horizon 8 version 2006 and later
  • Omnissa Horizon Cloud Service - Next-Gen
  • Horizon Cloud in Microsoft Azure
• To use Horizon Client in FIPS mode, you must use Connection Server version 2309 or later; if using Unified Access Gateway, you must also use Unified Access Gateway 2309 or later. For more information, see Omnissa Knowledge Base (KB) article 95144.
• To install Horizon Client for Windows, download the installer from the Horizon Clients download page.
• For installation instructions, see the Horizon Client for Windows Guide.
• For information about the features that are supported in nested mode, see Omnissa Knowledge Base article 80509, “Horizon Guidelines for Nested Mode.” Resolved Issues The following issues are resolved in this release. There are no resolved issues in this release. Known Issues
• Jumplist, URI, and Shortcuts may not work for Horizon Client Next. Workaround: Rename horizon-client-next to horizon-client. You can also rename the existing horizon-client binary to any name of your choice to avoid conflicts. Documentation Horizon Client for Windows documentation is in the Omnissa Product Documentation. Localized Content for Omnissa Docs For details on Omnissa’s localization strategy, see Announcing Omnissa Localization Support. Support Contact Information To receive support and to learn more about support policies, see Omnissa Customer Connect. For information on filing a support request in Customer Connect and via Cloud Services Portal, see Omnissa Knowledge Base article 6000005.