Omnissa Horizon Client for Windows Release Notes
Horizon Client for Windows 2512 | 16 DEC 2025
Horizon Client for Windows 2512.1 | 25 FEB 2026
With Horizon® Client™ for Windows 2512, 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).
What’s New - 2512.1
Horizon® Client™ for Windows 2512.1 includes bug fixes and:
- Improvements to remote desktop connectivity and graphics performance
- Improved Teams 1.0 audio echo cancellation
- Updated open-source components
What’s New - 2512
Horizon® Client™ for Windows 2512 includes the following new features:
- Video Rendering
Horizon Client for Windows now handles video rendering with improved Direct3D 11 (D3D11) hardware acceleration support. This setting allows you to configure the client’s video rendering path.
- On-Demand Clipboard Rendering
The clipboard redirection size limit has now been increased to 4GBs, with support for all Windows data formats for copy-paste between the virtual desktop and the local endpoint machine.
- Broker Management
The new Horizon Client Restrictions option blocks or warns users from connecting to administrator-specified Horizon Client versions.
- Multiple Monitor Nested Mode
Nested mode is now supported for multiple monitors.
- Public IP telemetry reporting
The Horizon Client for Windows DEEM plug-in now collects the client device’s public IP address from the DEEM agent when a user connects to a remote session.
- RDP Session Detection Policy
This release adds an agent-configurable policy that allows Horizon to detect active RDP sessions on a Windows device running the Horizon Windows Client. This new capability adds to session awareness and supports sites that need to control or track Horizon usage that is started from RDP connections.
- FIDO2 / WebAuthn Redirection Support for UWP and Win32 Applications
The Horizon Windows Client now supports FIDO2 (WebAuthn) redirection for both UWP applications and traditional Win32/Desktop applications running inside the remote session. This enhances end-user authentication scenarios, such as signing into the new Outlook for Windows (UWP) and Microsoft Teams, by enabling secure and seamless FIDO2 device usage directly inside the virtual desktop.
- Updated proxy authentication to use SPNEGO/Kerberos
The Windows client now establishes proxy connections using SPNEGO with Kerberos. This aligns Microsoft’s security guidance and leverages authentication flows already supported by modern browsers like Edge and Chrome.
Resolved Issues - 2512.1
- HV2-194136: Agent DCT Log Collection failed with error code 1073740791.
- AST-11539: AHV ClonePrep pool stuck on “Hybrid Domain Join In Progress”
- VCART-10219: The installer UI did not display a dialog box indicating that a machine is already registered.
- VCART-10257, HZN-7777: When attempting to create a pool within Nutanix using FIPS mode, the agent fails customization.
Resolved Issues - 2512
The following issues are resolved in this release.
- Spaces are input in published applications during keyboard input instead of complete text strings.
- Black box flickering appears briefly in the user interface before interface elements were loaded in published applications.
- Monitor selection changes don’t apply correctly in multi-monitor environments.
- The display freezes when moving applications between monitors in multi-monitor RDP sessions deployed as RDSH applications.
- Horizon Client freezes during VDI connections due to a thread deadlock.
- Audio issues with Teams virtualization during call including transfers.
- USB device is unexpectedly treated as redirected under SDR.
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.
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.”
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.
