| VMware Horizon Client for Windows 2203 | 05 APR 2022 Check for additions and updates to these release notes. |
Horizon Client for Windows 2203 includes the following new features:
This release supports the ability to give control of screenshares on VDI and RDSH sessions for VMware Horizon Client for Windows. Take control is supported from version 2111 and later. For additional details and dependency, see Configuring Media Optimization for Microsoft Teams.
VMware Horizon Client for Windows now supports full range color and improved color fidelity when using H264 4:4:4 or HEVC 4:4:4.
You can now filter USB redirection by release number in addition to vendor and product IDs.
This release introduces the Enable Keylogger Blocking feature for custom installation of the VMware Horizon Client for Windows. This feature enables anti keylogger.
This release supports a new option for UPD - the VMware Universal XPS Driver.
VMware Horizon Client for Windows now supports Horizon Cloud Service - next-gen.
VMware Horizon Client for Windows now supports the new settings in Unified Access Gateway. You can run the OPSWAT MetaAccess application as an administrator or as a user.
With the VMware Integrated Printing feature, you can add a watermark when printing a document from a remote desktop.
VMware Horizon Client for Windows now has the ability to detect when the viewclient window is minimized to stop encoding screen updates, saving network traffic and CPU usage on both agent and client.
With this release, there are performance improvements for low powered machines (e.g. thin clients) or when using multiple 4K monitors.
For information about new remote desktop features, see the VMware Horizon 8 2203 Release Notes.
The user interface and documentation for Horizon Client are available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, Korean, and Spanish.
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.
Horizon Client for Windows quits when launching a remote desktop
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 the following workarounds:
Limited context menu with Browser Redirection feature
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.
Incorrect event log report
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.
Error when connecting to a remote desktop with the Microsoft RDP display protocol
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.
RDP session ends on the physical machine
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.
Client's "log in as current user" function is not available
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.
Resolution helper tooltip is not available
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
Windows Fax and Scan hangs
On Windows 10, Windows Fax and Scan hangs when using a CardScan 800 device.
Workaround: None.
Desktop window autofit does not work
When you connect 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.
Mouse pointer does not move downward
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.
Horizon Client may stop responding when Automatically Connect at Startup is selected
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 in client side.
Workaround: None.
Bandwidth Limit setting for serial port redirection fails to take effect
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.
Performance of VMware Blast slows down with serial port redirection at high baud rate
With serial port redirection at a high baud rate such as 115200, the performance of VMware Blast slows down, and the connection might sometimes hang.
Workaround: Use a baud rate of 9600.
IPv6 IP mapping for LBP results in issues
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.
White border appears to the right side of the desktop window
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.
Wacom500B cannot be unshared from agent
If you enable Automatically Connect when Inserted for Wacom500B, it is not unshared on the local client after the device is redirected. This is because the arbitrator deletes the device when unsharing it from agent to client but if the device is still plugged in on the client side, it is re-added.
Workaround: None.
