VMware Horizon Client for Windows 2111.1 Release Notes

VMware Horizon Client for Windows 2111.1 | 10 MAR 2022

Check for additions and updates to these release notes.

What's New

Horizon Client for Windows 2111.1 fixes the keyboard issue that caused repeating keystokes.

For information about new remote desktop features, see the VMware Horizon 8 2111 Release Notes.

Internationalization

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.

Resolved Issues

E911 For Microsoft Teams Optimization issue : Teams status shows as disconnected if network switch PortID name has non-utf8 character and E911 is enabled.
While using Horizon Client for Windows 2103, 2106, and 2111, the keystrokes get repeated intermittently.

Known Issues

Issues with the Automatically Connect at Startup feature for a camera in nested mode

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 second hop agent but the USB audio devices are removed immediately on the client side.

Workaround: None.
Serial port redirection group policy setting does not work

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.
VMware Blast performance issues

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.
Printer access issues in an IPv6 environment

In an IPv6 environment, if you configure IP address mapping for location-based printing, users might face 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.
Enable Relative Mouse feature does not work on touch-enabled screen

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.

Workaround: None.
Enable Relative Mouse feature sometimes has issues when used in a multi-monitor setup

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.
Desktop window does not autofit

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.
Windows Fax and Scan hangs

On Windows 10, Windows Fax and Scan hangs when using a CardScan 800 device.

Workaround: None.
Resolution helper tooltip does not appear on client machine

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.

Workaround: None
Client's "log in as current user" function does not work

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.
RDP session ends on physical machine

f 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.
Pending session expired error might displayed when connecting to a remote desktop

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.
Event log reports one byte more than actual length of data
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:
```
"aaa
bbb
ccc"
```
Workaround: None.
Context menu options are limited

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.

Workaround: None.
Horizon Client for Windows quits when launching a remote desktop with multiple monitors

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.
White border appears on Windows 11 client machine

On a Windows 11 client machine, a white border appears 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.
Title bar and borders of remote desktop flicker on Windows 11 client machine

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.