Omnissa Horizon Client for Windows Release Notes

With Horizon® Client™ for Windows 2609, 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.

What's New

• The MS Teams media optimization integration in Horizon VDI has been upgraded to WebRTC m150, improving real-time audio and video performance and compatibility.

• Intercepted applications in remote desktops can now use Windows Hello for Business (WHfB) certificates for authentication, with fixes to IPC listener transport configuration and SignHash padding/algorithm handling (PSS/PKCS1, SHA384/512) to restore certificate forwarding into the VM.

• Zoom VDI plugin management is now integrated directly into the Windows Horizon Client, bundling the Zoom automatic plugin management installer to simplify plugin deployment and updates without separate installation steps.

• The Horizon Client installer now offers a choice between Horizon Client Classic and Horizon Client Next at install time on Windows, Mac, and Linux, with upgrade and auto-upgrade paths that retain the previously installed client type. Only the selected client is installed, and the installation choice is logged.

• Administrators can now whitelist specific applications to bypass Screen-capture Blocking via GPO, allowing trusted apps (e.g., Zoom) to continue screen sharing while blocking all other applications from taking screenshots or recordings of Horizon VDI and published application sessions. The GPO can be applied at both user and machine level on Windows and Mac clients.

• Support for multiple certificates on a single YubiKey is now available across Windows, Linux, and Mac Horizon Clients, enabling users to store and use multiple smart card certificates on one hardware token for authentication.

• Horizon now supports a separate recording playback port, allowing administrators to use different ports for session recording and playback (previously both used port 9443), enabling tighter firewall policies in security-sensitive environments where recording servers must be isolated from playback access.

• Process Manager for Horizon Client for Windows - Process Manager provides end users with a single place to view and manage all their active virtual desktop and published application sessions.

  It allows you to bring a desktop or application to the foreground, copy a session ID to share with your help desk, or disconnect or log off a session without affecting your other sessions. Open Process Manager from the More Actions menu in the desktop and application selector or from the Horizon Client system tray. See the Horizon Client for Windows Guide for availability requirements and usage details.

• The Horizon Client for Windows has been upgraded from .NET Core 8 to .NET 10, ahead of .NET Core 8's end-of-life in November 2026, bringing improved performance and continued framework support.

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 Omnissa Horizon 8 version 2006 and later.

• 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

There are no major issue resolutions to report 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.