check-circle-line exclamation-circle-line close-line

VMware Horizon Client 4.10 for Linux Release Notes

Horizon Client for Linux 4.10 | 13 December 2018

These release notes cover the following topics:

Key Features

VMware Horizon Client for Linux makes it easy to access your remote desktops and published applications from a supported Linux system with the best possible user experience on the Local Area Network (LAN) or across a Wide Area Network (WAN).

  • Support for Ubuntu and Red Hat Enterprise Linux (RHEL) - The Horizon Client installer available from the VMware Downloads site provides support for these operating systems.
  • Unmatched performance - The adaptive capabilities of the VMware Blast and PCoIP display protocols are optimized to deliver the best user experience, even over low-bandwidth and high-latency connections. Your desktop is fast and responsive regardless of where you are.
  • Simple connectivity - Horizon Client for Linux 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. Enhanced certificate checking is performed on the client. Horizon Client for Linux also supports optional RADIUS and RSA SecurID authentication.

Top of Page

What's New in This Release

  • Support for Windows Server 2019
    Microsoft Windows Server 2019 is now supported as a RDS-hosted server for remote desktop and published application sessions.
  • Support for PIV Smart Card  
    PIV smart card authentication and redirection support is now available.
  • TLS 1.0 support discontinued
    Support of TLS 1.0 has been discontinued beginning with this release.
  • Serial port redirection for RDS-hosted desktops in nested mode 
    The serial port redirection feature is now supported in published applications that are launched from Horizon Client inside RDS-hosted desktops (nested sessions). Horizon Agent 7.7 and Horizon Client 4.10 or later must be installed in the RDS-hosted desktops. The number of concurrent users is limited in a nested mode scenario.
  • Support for virtual printing on physical RDS host machine
    Virtual printing is now supported on published desktops and published applications that are deployed on RDS hosts that are physical machines.
  • Multi-session mode support
    You can use multiple instances of the same published application on different client devices when the multi-session mode is enabled for a published application.
  • Logging copy and paste activity 
    You can enable the clipboard audit feature in Horizon Client to record information about clipboard data that is copied from the Horizon Agent machine to the Linux client machine. This feature requires Horizon Agent 7.7.  
  • Support for Workspace ONE Mode
    Beginning with Horizon 7 version 7.2, a Horizon administrator can enable Workspace ONE mode for a Connection Server instance. If you connect to a Workspace ONE mode enabled server in Horizon Client for Linux, you are redirected to the Workspace ONE portal to launch your entitled desktops and applications..

Top of Page


The user interface and documentation for Horizon Client are available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, Korean, and Spanish

Note: To have the client user interface use Simplified Chinese characters, set the client system to use the zh_CN locale. If you set the client system to use the zh_SG locale, the user interface is displayed in English characters.

Top of Page

Before You Begin

Note: The supported systems listed below and in the VMware Horizon Client for Linux Installation and Setup Guide pertain to the Horizon Client for Linux that VMware makes available. In addition, several VMware partners offer thin and zero client devices for Horizon 7 deployments. The features that are available for each thin or zero client device, and the operating systems supported, are determined by the vendor and model, and the configuration that an enterprise chooses to use. For information about the vendors and models for these client devices, see the VMware Compatibility Guide, available on the VMware Web site.

  • The OpenSSL library is updated to version openssl-1.0.2p. For your convenience, the Horizon Client installer provided on the VMware Downloads site downloads and installs the library.
  • Horizon Client for Linux 4.10 has been tested and is supported on the following 32-bit operating systems if you use the installer provided by VMware:
    • Ubuntu 16.04
    • Red Hat Enterprise Linux (RHEL) 6.10
  • Horizon Client for Linux 4.10 has been tested and is supported on the following 64-bit operating systems if you use the installer provided by VMware:
    • Ubuntu x64 16.04 and 18.04
    • Red Hat Enterprise Linux (RHEL) 6.10 and 7.5
  • Horizon Client for Linux 4.10 is supported on Raspberry Pi 3 Model B devices that are installed with ThinLinx Operating System (TLXOS) or Stratodesk NoTouch Operating System. The supported Horizon Client features include Blast Extreme, USB redirection, and H.264 decoding.
  • VMware Horizon Client for Linux is supported with the latest maintenance release of VMware Horizon 6 version 6.2.x and later.
  • To install Horizon Client for Linux, download the installer from the VMware Horizon Client download page.
  • Horizon Client for Linux 4.10 does not ship with the GTK+ library, but it does use the library installed on the host system. Make sure your system is up to date with a version of the library that includes fixes for publicly reported security vulnerabilities. A list of the publicly reported security vulnerabilities, and the versions affected, for GTK+ can be found at

For more system requirements and detailed installation instructions, see VMware Horizon Client for Linux Installation and Setup Guide.

Top of Page

Information for Distribution Partners

The following deployment instructions and information about library dependencies are provided for VMware distribution partners.

Deployment Instructions

  1. Download the vmware-view-client-linux-xxx-yyyy.tar.gz file from the VMware Downloads site and extract the contents of the downloaded tar.gz package to your system, where xxx is the product version and yyyy is the build number. 
  2. Navigate to the folder for your specific platform, i386 or x64. You will find additional tar.gz packages of the individual Horizon Client components. For example, for the x64 folder you will find the following tar.gz packages for Horizon Client.

  3. Use the following deployments instructions for each of the tar.gz packages.
  • Horizon Client for Linux

    The VMware-Horizon-Client-xxx-yyyy-crtbora.PLATFORM.tar.gz and VMware-Horizon-Client-xxx-yyyy.PLATFORM.tar.gz packages contain the VMware Horizon Client binaries. It is recommended that you use the VMware-Horizon-Client-xxx-yyyy-crtbora.PLATFORM.tar.gz package to deploy the Horizon Client for Linux because the original Horizon Client for Linux package, VMware-Horizon-Client-xxx-yyyy.PLATFORM.tar.gz, is planned to be deprecated. Use the following instructions as a guide in configuring the VMware Horizon Client binary files.

    1. Extract the VMware-Horizon-Client-xxx-yyyy-crtbora.PLATFORM.tar.gz package.
    2. Navigate to the extracted folder, VMware-Horizon-Client-xxx-yyyy-crtbora.PLATFORM, and move the contents of the extracted Horizon Client files to the recommended system folders. Depending on your particular Linux environment, you can choose to use folders different from those used below.
      1. Move the contents of the bin folder to the /usr/bin folder.
      2. Move the contents of the lib folder to the /usr/lib folder.
      3. Move the contents of the doc folder to the /usr/share/doc folder.
      4. Move the contents of the share/locale folder to the /usr/share/locale folder.

    The VMware-Horizon-PCoIP-xxx-yyyy.PLATFORM.tar.gz contains the mandatory binaries used by both display protocols, PCoIP and VMware Blast. Use the following instructions as a guide for configuring the Horizon Client display protocol files.

    1. Extract the contents of the VMware-Horizon-PCoIP-xxx-yyyy.PLATFORM.tar.gz package.
    2. Navigate to the extracted folder, VMware-Horizon-PCoIP-xxx-yyyy.PLATFORM, and use the following commands to copy the contents of the extracted Horizon Client PCoIP files to the recommended system folders. Depending on your particular Linux environment, you can choose to use folders different from those used below.
      1. Copy the contents of the bin folder to the /usr/bin folder.
      2. Copy the contents of the lib folder to the /usr/lib folder.
        Note: To keep the attributes intact, use the -a option of the cp command when copying the files from lib folder.
      3. Copy the crtbora files to the /usr/lib/vmware folder, using the following example for the RHEL 6.x based system.
        $ sudo cp -f /usr/lib/vmware/view/crtbora/* /usr/lib/vmware/ 
      4. If you are not using a RHEL 6.x x86-based system, remove the following libraries.
        $ sudo rm /usr/lib/vmware/
        $ sudo rm /usr/lib/vmware/
        $ sudo rm /usr/lib/vmware/
        $ sudo rm /usr/lib/vmware/
        $ sudo rm /usr/lib/vmware/
        $ sudo rm /usr/lib/vmware/ 
  • USB Redirection
    The VMware-Horizon-USB-xxx--yyyy.PLATFORM.tar.gz package contains the binaries used by the USB Redirection feature. 
    1. Extract the contents of the VMware-Horizon-USB-xxx--yyyy.PLATFORM.tar.gz package.
    2. Navigate to where the package was extracted and copy the extracted folders to the recommended system folders.
      1. Copy the contents of the bin folder to the /usr/bin folder.
      2. Copy the contents of the lib folder to the /usr/lib folder.
      3. Copy the contents of the init.d folder to the /etc/init.d folder.
    3. Configure the USB Redirection feature, using the following examples for an Ubuntu system as a guide.
      1. Set up USB arbitrator daemon in the system's auto-startup script using one of the following methods, where # refers to 2, 3, 4, or 5, depending on your system's run level.
        • Create symbolic links using the following command:
          $ sudo ln -s  /etc/init.d/vmware-USBArbitrator /etc/rc#.d/S50vmware-USBArbitrator 
        • Add /etc/init.d/vmware-USBArbitrator start in your system's /etc/rc.local file. Make sure /etc/rc.local has the executable permission.
      2. Automatically stop the USB arbitrator daemon before a system reboot or halt using the following command, where # refers to 0 or 6, depending on your system's run level.
        $ sudo ln -s /etc/init.d/vmware-USBArbitrator /etc/rc#.d/K08vmware-USBArbitrator
      3. Manually start, stop, or restart the USB arbitrator daemon when necessary using the following command:
        $ sudo /etc/init.d/vmware-USBArbitrator [start|stop|restart]
  • Serial Port Redirection
    To install the Serial Port Redirection feature, see the README file included in the VMware-Horizon-serialportClient-XXX.yyyy.tar.gz file,  which is available with the vmware-view-client-linux-xxx-yyyy.tar.gz file that you downloaded earlier from the VMware Downloads site.
  • Printer Redirection Feature
    To install the Printer Redirection feature, see the Printer Redirection README file included in the VMware-Horizon-tpClient-XXX.tar.gz file, which is available for download from the VMware Downloads site.
  • Skype for Business Feature
    To install the Skype for Business feature, see the Skype for Business README file included in the VMware-Horizon-Media-Provider-XXX.tar.gz file, which is available for download from the VMware Downloads site.

Building Dependencies

The following libraries are required for building and running Horizon Client for Linux.

  • libxss1, libxss-dev, libxinerama1, and libxinerama-dev
    Install the libraries using a command similar to the following, which is an example in an Ubuntu-based system.
    sudo apt-get install libxss1 libxss-dev libxinerama1 libxinerama-dev
  • openssl-1.0.2p or later
  • curl-7.61.1 or later
    Create a dynamic link for this library to the openssl-1.0.2p or later library.
  • gcc 6.4 or later
  • glibc 2.11 or later for x86 and x64 systems; glibc 2.17 or later for systems with 32-bit hard-float ARMv7 (armhf) architecture
  • libstdc++ 3.4.22 or later

The following environment variables are required for building Horizon Client for Linux with Seamless Window feature.

export GOBUILD_CRTBORA_ROOT="Path of VMware-Horizon-CRTBORA-xxx-yyyyy"

After you install the Horizon Client components, locate the /bin directory in the Horizon Client package that you extracted earlier. From that bin directory, run the vmware-view-lib-san script, which checks the build dependencies.

Top of Page

Resolved Issues

  • The copy and paste operations do not work between two applications in different farms.

  • Connect your host operating system to more than one monitor and select all the monitors for Full Screen - All Monitors mode in the Settings dialog box of the Horizon Client for Linux. If you switch to Full Screen - This Monitor mode and connect to a remote desktop using the rightmost monitor,  the remote desktop is  connected to more than one monitor. If the DPI synchronization feature is enabled, the remote desktop displays more than one desktop screen within one physical monitor screen.

  • If a user is in more than 200 AD groups, the USB feature for the desktop session will not be available.

  • In a multi-monitor setup, the disconnect popup dialog box appears between the two monitors.

  • When using Seamless Window mode with the --once command-line option, the Horizon Client window does not close after the remote session is disconnected when using the VMware Blast display protocol.

Known Issues

  • A known security issue can affect Horizon Clients. The issue involves a privilege escalation leveraging glibc.This issue was devised by the Project Zero team as described in CVE-2014-5119. To mitigate this issue, partners and customers are advised to update the Linux operating system as follows:
  • If you use Horizon Client to connect to a remote desktop that has client drive redirection disabled, such as through a group policy setting, or if you connect to a remote desktop that has Horizon View Agent 6.1.0 or an earlier version installed, no message is displayed to explain why the client drive redirection feature is not working.

  • In some versions of Linux, including CentOS 6.x, the Numlock LED does not work while in a Horizon desktop.

  • If multiple Horizon clients connect to the same RDS desktop or remote application simultaneously and map to a location-based printer with the same name, the printer appears in the first client session, but not in later client sessions.
    Workaround: For the client sessions in which the printer does not appear, perform a manual refresh. For a remote desktop, press F5 or refresh the Devices and Printers window. For a remote application, close and reopen the application print dialog box. The location-based printer appears in the printer list.

  • Virtual printing might not work if you connect to a remote desktop using RDP, open Horizon Client on the remote desktop,launch a nested application session, and then log off and log back in to the desktop. When you try to print from the nested application, the expected printer list might not appear. This issue only occurs after you log back in to the desktop.
    Workaround: Reset the application on the remote desktop. To avoid having to set applications, use PCoIP for both ends of the session-in-session connection.That is, use PCoIP to connect to the remote desktop and use PCoIP to connect from within the desktop to the nested application. If you are using location-based printing, you can resolve this issue by closing and reopening the application's print dialog box.

  • If you use a FreeRDP connection and specify a monitor configuration that conflicts with the configuration the end user chooses, Horizon Client performance becomes poor and the client might stop responding altogether. For example, the following command for launching Horizon Client would cause problems if the user selected "Full Screen - This Monitor":

    vmware-view --enableNla --rdpclient=xfreerdp--xfreerdpOptions="/sec:nla /cert-ignore /p:password/u:crt\administrator /multimon"

    As a best practice, avoid specifying FreeRDP options for the display, such as /multimon or /workarea. Instead, let Horizon Client control the topology.

  • If your client system is running pcsc-lite version 1.5, smart card removal policy may not work, logging off, shutting down or resetting a Windows remote desktop may result in a black screen, or the Horizon Client menu may become blank for about 10 seconds when a user has smart card sessions to multiple desktops and the user disconnects from one desktop.
    Workaround: Upgrade to pcsc-lite 1.7.4 or later.

  • If you use a PulseAudio sound system, you might hear static when setting the volume using guest system volume slider.
    Workaround: Use the Linux client system's volume slider or use ALSA audio by adding sound.backendType = alsa to either the ~/.vmware/config or the /etc/vmware/config configuration file.

  • If you connect to a remote desktop with FreeRDP and configure the desktop to connect to a separate disk, if the disk name includes non-ASCII characters, the disk name cannot be displayed correctly in the remote desktop. For example, if you use non-ASCII characters in the disk name and then launch Horizon Client with command line option
    '--rdpclient=xfreerdp' and '--xfreerdpOptions="/drive: , /home/user"'
    the disk name does not appear correctly in the remote desktop.

  • Users cannot use rdesktop 1.8.x to connect to Horizon 7 Windows desktops. This is because Horizon 7 does not support TLSv1.0 by default and rdesktop 1.8.x supports only TLSv1.0.
    Workaround: Enable TLSv1.0 on the desktop by setting the following registry key:
    Be aware that TLSv1.0 is considered insufficiently secure. For Windows 7 desktops, Microsoft KB must also be installed.

  • On RHEL 6.x, with two monitors at the maximum resolution of 2560 x 1600, if you change the order of the monitors (the main monitor becomes the secondary and the secondary becomes the main), and then run Horizon Client and connect to a desktop using PCoIP and setting FullScreen - All Monitors, after the remote desktop is displayed, the menu options File > Disconnect from Server and File> Return to Desktop and Application List do not work.

  • Some video files might not play properly on a remote desktop when MMR is enabled.
    Solution: Make sure that the video format is supported and the proper decoder plug-in for the video is installed on the client.

  • On a Windows 7 remote desktop, while playing video on Internet Explorer and then you open a new tab, the MMR video frame overlays in the new tab.
    Workaround: Do not open a new tab or switch to a different tab while video is playing.

  • Videos do not play smoothly in remote desktops and sound disappears when MMR is enabled and the network delay is more than 75 ms.
    Workaround: Disable MMR when the network delay is more than 75 ms.

  • In certain circumstances, opening a local file with File> Open in a remote desktop or remote application causes the guest operating system on the Horizon Agent machine to encounter a STOP error (blue screen) or to stop responding (hang) when client drive redirection (CDR) is used. For more information, see VMware Knowledge Base (KB) article 2149417: Agent machine gets STOP error or stops responding when you open a local file shared with CDR.

  • On some HP thin clients that have HP ThinPro 5.2.0 (T6X52011) operating system, Horizon Client for Linux might display a black screen or crash when user is playing some video on a remote desktop and pressing the fast-rewind button on Windows Media Player.
    Workaround: Upgrade the OS to HP ThinPro 6.1.0 (T7X61007) or the latest version.

  • The System Tray redirection functionality is not supported and so you can not  exit a remote application session using the system tray.
    Workaround:  Use the remote application's UI to end the application session. For example, to exit a Skype session, select the Settings icon  and then select File > Exit.

  • You can not  start an application from the Application Launcher because the launcher is unsupported.
    Workaround: Start the remote application via the Linux client's UI.

  • Mouse does not work inside the Blast session when the keyboard layout is switched to Secondary Keyboard Layout
    Workaround: Manually add the following configuration option in the /etc/vmware/config file:
            RemoteDisplay.allowVMPointerEvent2 = FALSE

  • If there are identical shortcuts with differing functions on the client Linux operating system and a remote Windows operating system, the shortcut for the Windows operating system will not work when a seamless window application is active. Only the shortcut for the Linux operating system takes effect. For example, by default, pressing Alt opens a Search dialog window on an Ubuntu operating system and it shows the application's menu on a Windows operating system. When a seamless window application is active, pressing Alt displays the Ubuntu operating system's Search menu, but does not show the application's menu.

    Workaround: Change the shortcut in the host Linux operating system or in the remote Windows operating system so that the shortcuts in the two operating systems do not conflict.

  • Because Horizon Client for Linux uses the Linux operating system's GNOME theme, the Horizon Client for Linux authentication domain list, the desktop/application protocol list, and display list appear black on some of the Linux operating systems, making it difficult to read any of these lists.

    Workaround: Change the GNOME theme used by the Linux operating system. For example, in Ubuntu 16.04.4 operating system, install gnome-tweak-tool if it is not yet installed, run gnome-tweak-tool, and change the GTK+ theme from Ambiance to Radiance.

  • You might run into a mouse or keyboard issue when you use the H.264 High Color Accuracy feature for a resolution that is higher than 2560x1600.

    Workaround: Manually add the following configuration option in the /etc/vmware/config file.

  • Hardware H.264 decoding using Video Acceleration API (VAAPI) v2 is currently not supported.

    Workaround: None.

  • On a RHEL 6.x system, if you try to use the PCoIP display protocol to set up a session using more than two monitors, the PCoIP session might not get set up successfully.

    Workaround: Disable the ASLR (Address Space Layout Randomize) for the client operating system.