VMware Horizon Client for Windows 2203 | 05 APR 2022

Check for additions and updates to these release notes.

What's New

Horizon Client for Windows 2203 includes the following new features:

  • Give and Take screen control for Microsoft Teams

    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.

  • Support for full range color and improved color fidelity

    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. 

  • Disable USB Redirection for Specific Devices

    You can now filter USB redirection by release number in addition to vendor and product IDs.

  • Anti keylogger support

    This release introduces the Enable Keylogger Blocking feature for custom installation of the VMware Horizon Client for Windows. This feature enables anti keylogger.

  • Universal Printer Driver now includes the VMware Universal XPS Driver option

    This release supports a new option for UPD - the VMware Universal XPS Driver.

  • Support for Horizon Cloud Service - next-gen

    VMware Horizon Client for Windows now supports Horizon Cloud Service - next-gen.

  • Support for new settings in Unified Access Gateway

    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.

  • VMware Integrated Printing supports watermark

    With the VMware Integrated Printing feature, you can add a watermark when printing a document from a remote desktop.

  • Support to stop screen updates when window is minimized

    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.

  • Improved performance for GPU accelerated decoding of H264 and HEVC

    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.

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

  • On a Windows 11 client machine, the title bar and borders of the remote desktop used to flicker after you share the desktop using Microsoft Teams. Microsoft has resolved this issue.

Known Issues

  • 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:

    • Configure your monitor layout so that it’s not very wide or very tall (for example, use a tile/matrix layout instead of using single row/column of 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.

  • 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:


    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.

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

  • Windows PC hangs after restart

    On some physical PCs, performing a Windows Restart from within the VMware Horizon session causes the PC to hang on the Windows Restarting screen.

    Workaround: Add the following registry key:

    1. Launch regedit.exe.
    2. Locate the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.
    3. Add a new DWORD Value named verbosestatus.
    4. Modify the value of verbosestatus to 1.
check-circle-line exclamation-circle-line close-line
Scroll to top icon