Horizon Client for Windows 2111 | 30 November 2021
These release notes cover the following topics:
VMware Horizon Client for Windows makes it easy to access your remote desktops and published applications with the best possible user experience on the Local Area Network (LAN) or across a Wide Area Network (WAN).
- Support for Windows 11, Windows 10 (64-bit), Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019
- Unmatched performance - The adaptive capabilities of the PCoIP display protocol and the VMware Blast display protocol are optimized to deliver the best user experience, even over low-bandwidth and high-latency connections. Your remote desktops and published applications are fast and responsive, regardless of where you are.
- Simple connectivity - Horizon Client for Windows is tightly integrated with VMware Horizon for simple setup and connectivity.
- Secure from any location - At your desk or away from the office, your data is delivered securely to you wherever you are. SSL/TLS encryption is always used to protect user credentials, and enhanced certificate checking is performed on the client device. Horizon Client supports optional RADIUS and RSA SecurID authentication. You can also install Horizon Client so that it runs in FIPS mode.
What's New in This Release
Horizon Client for Windows 2111 includes the following new features:
- Enhanced default printing behavior
This release introduces the following enhancements to the VMware Integrated Printing feature. A new toolbar offers updated page icons and the ability to scroll with the mouse wheel. The preview displays pages immediately. Previously, you had to wait for all pages to process before a preview was rendered.
- The system tray displays a counter for new items
For seamless applications, the item counter was missing from the application icon in the Windows system tray of the Horizon client. In this release, the application icon includes a counter. This counter indicates the arrival of new items. In the event of a disconnection, the counter updates after reconnecting and a new item arrives.
- Enhanced Alt-Tab behavior – Previously, focus might return to a window’s title bar and not the application after using Alt-Tab. In this release, the focus returns to the application as expected.
- Increased integration with assistive technologies
These accessibility enhancements include improved interoperability with screen readers such as Narrator.
- Additional language support for Input Method Editor (IME)
Horizon Client for Windows supports Traditional Chinese for IME with Remote Desktops and right-click options for Japanese.
- Risk score assessment
The Horizon Client for Windows supports risk score assessment from Workspace ONE Intelligent Hub.
- Windows 11 and Windows 10 version 21H2 support
You can install Horizon Client for Windows 2111 on a Windows system that is running Windows 11 or 10 version 21H2.
- Client Hardware Acceleration support for Real Time Audio Video (RTAV)
The Horizon Client for Windows supports registry keys for hardware acceleration.
For information about new remote desktop features, see the VMware Horizon 8 2111 Release Notes.
The user interface and documentation for Horizon Client are available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, Korean, and Spanish.
Before You Begin
- For the Windows operating systems that this release of Horizon Client for Windows supports, see the VMware Horizon Client for Windows Installation and Setup Guide document.
- Horizon Client for Windows is supported with the latest maintenance release of VMware Horizon 7 version 7.13 and later.
- To install Horizon Client for Windows, download the installer from the VMware Horizon Client download page.
- For installation instructions, see the VMware Horizon Client for Windows Installation and Setup Guide document.
- For information about the features that are supported in nested mode, see VMware Knowledge Base article 67248, "VMware Horizon Guidelines for Nested Mode."
- The Horizon Client for Windows installer requires .NET Framework version 4.5 or later. For more information, see VMware Knowledge Base article 65142, "Horizon Client 4.10 installer requires .NET Framework version 4.5 or later".
- Beginning with Horizon Client for Windows 2006, Virtual Printing (also known as ThinPrint) is not supported. Use VMware Integrated Printing instead.
After disconnecting and reconnecting multiple remote desktops, you saw an error message. This error message no longer appears; Enhancements to the USB user interface resolved this issue.
If you select Connect USB Device > Automatically Connect at Startup for a camera in nested mode, Horizon Client may stop responding when you reconnect the the second hop agent but the USB audio devices removed immediately in client side.
The serial port redirection group policy setting Bandwidth Limit does not set a limit on the bandwidth.
Workaround: Use third-party software to limit the bandwidth.
If you connect multiple USB devices to the client system, select Automatically connect at startup in Horizon Client, and then connect, disconnect, and quickly reconnect to a remote desktop, not all of the USB devices are redirected to the remote desktop after you reconnect.
Workaround: Wait for the USB devices to be redirected back to the client machine (for example, wait for the devices to appear in the device manager) and then reconnect to the remote deskop. Alternatively, you can manually redirect any unredirected USB devices to the remote desktop.
With serial port redirection, at a high baud rate such as 115200, the performance of VMware Blast is significantly worse than PCoIP, and the connection might sometimes hang.
Workaround: Use a baud rate of 9600.
In an IPv6 environment, if you configure IP address mapping for location-based printing, users might encounter a problem accessing the printer because the client can have multiple IPv6 addresses. Anytime the client connects, it can use any one of the addresses.
Workaround: Use the location-based printing group policy setting IP Range to include the multiple addresses. However, the printing problem might still occur because the client might use a temporary address, which is not in the specified range.
- If you use a touch-enabled screen on your client system to work in a remote desktop, do not use the Enable Relative Mouse feature. This feature provides improved mouse performance for 3D and CAD applications, but for touch-enabled screens and tablets, the mouse coordinates are not translated properly, even in 3D and CAD applications.
If you have multiple monitors with different screen resolutions and expand Horizon Client to all monitors and then select the Enable Relative Mouse feature, occasionally, the mouse pointer might not be able to move downward beyond a certain position.
Workaround: Press Ctrl+Alt.
When a user connects to a desktop using PCoIP shortly after the desktop is powered on, autofit of the desktop window might not work. This issue happens most often if the desktop or network is under stress shortly after power-on (to start multiple applications or to map network drives, for example).
Workaround: Double-click the desktop window's title to go into window mode and double-click the title bar to go into all-monitor mode.
On Windows 10, Windows Fax and Scan hangs when using a CardScan 800 device.
If LockedGuestSize is set to 640x480 on the client machine and you launch a remote desktop in Window - Small mode, the resolution helper tooltip does not appear when you drag the window edge.
If you install Horizon Agent and then install Horizon Client on the same Windows machine (a nested mode installation), and you later uninstall Horizon Agent, the client's "log in as current user" function is lost after Horizon Agent is uninstalled. This problem occurs because the wsnotify.dll file is removed after Horizon Agent is uninstalled.
Workaround: Reinstall Horizon Agent or Horizon Client to bring back the "log in as current user" function.
If you use the RDP protocol to connect to a published desktop from a physical machine, and then you try to connect to the same published desktop from a zero client, the RDP session ends on the physical machine and the zero client cannot connect.
Workaround: Relaunch the same desktop pool with RDP from the physical machine, select Options > Disconnect and logoff in the launched RDP session, and then reconnect to the same desktop pool from the zero client.
A “Pending session expired” error might occur when you try to connect to a remote desktop with the Microsoft RDP display protocol. This problem only occurs in large-scale environments where a Unified Access Gateway appliance is used and virtual printing is enabled.
Workaround: Establish a connection to the remote desktop without using a Unified Access Gateway appliance, or disable virtual printing and establish a connection using RDP.
With the clipboard audit feature, the event log reports one byte more than the actual length of the data that was copied from the agent machine to the client machine. For example, if you copy 10 bytes of data from a remote desktop to the client machine, the event log reports "XXX copy 11 bytes CPFORMAT_TEXT data from Horizon Agent to Horizon Client XXX with clipboard." Also, if "\r\n" is in the copied text, the event log records only the length of "\r." For example, if you copy the following text, the audit message records the length as 12 bytes:
With the Browser Redirection feature, the context menu options on right click are limited to open link in new tab, open link in new window, back, and forward.
Horizon Client for Windows might quit unexpectedly when launching a remote desktop with multiple monitors at a high resolution.
Workaround: Check the supported multiple monitor configurations in the documentation to resolve this issue. If you still encounter this issue, consider following workarounds:
- Align your monitors in a regular layout and limit the total height (pixels) and stacks of the monitors.
- Try not to launch multiple desktops with multiple monitors in one client instance, but start a new client instance to launch another remote desktop.
- Use the VMware Blast protocol to start the remote desktop.
- On a Windows 11 client machine, a white border is displayed to the right side of the desktop window
When you launch a desktop in All Monitors mode and then quit the All Monitors mode and maximize the desktop, a white border is displayed to the right side of the desktop window.
Workaround: This is a Microsoft Windows 11 issue. Until Microsoft fixes this issue, launch the desktop directly in large mode.
- On a Windows 11 client machine, the title bar and borders of the remote desktop keep flickering after you share the desktop using Microsoft Teams.
This issue can occur when you use Horizon Client 2106 or later on a Windows 11 machine and Media Optimization for Microsoft Teams is enabled on the agent. If you launch a remote desktop without using Fullscreen - All Monitors or Fullscreen - Single Monitor display mode and share the desktop using Microsoft Teams, the title bar and borders of the remote desktop start flickering.
Workaround: This is a Microsoft Windows 11 issue. Until Microsoft fixes this issue, use Fullscreen - All Monitors or Fullscreen - Single Monitor display mode before sharing a desktop using Microsoft Teams.
- Microsoft Teams status shows incorrect status
Microsoft Teams status is displayed as disconnected if the network switch PortID name has a non-utf8 character. This issue occurs only the E911 feature is enabled.