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

VMware Remote Console 11.0 | 05 DEC 2019

Build 15201582 | Mac App Store Build 15201581

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

This release of VMware Remote Console includes the following changes:

  • VMware Remote Console can be installed from the Mac App Store. Installation from the App Store is recommended on machines running macOS 10.15 or later.
  • The VMware Remote Console Linux client has been rewritten to support GTK+ 3.
  • VMware Remote Console can connect to remote virtual machines through proxy servers that require authentication. You can specify a user name and password for your proxy server and authenticate over HTTP.
  • The VMware Remote Console Windows client supports Control Flow Guard (CFG) for enhanced security.
  • Security enhancements have been implemented for the automatic upgrade process on macOS.
  • Open-source components have been updated, including Python (2.7.16), cURL (7.66), and libgcrypt (1.8.5).
  • VMware Remote Console participates in VMware's Customer Experience Improvement Program (CEIP), which provides VMware with technical information that is used to improve the quality, reliability, and functionality of VMware products and services. The information does not personally identify any individual. Details regarding the data collected through CEIP and the purposes for which it is used by VMware are set forth at the Trust & Assurance Center.


You can use VMware Remote Console 11.0 to connect to virtual machines in vSphere, vRealize Automation, and vCloud Director.


  • VMware Remote Console 11.0 requires direct access to port 443 on ESXi hosts. For more information, see KB 76672.
  • vRealize Automation 8.0 is not compatible with any version of VMware Remote Console. 

You can install VMware Remote Console 11.0 on the following host operating systems:

Windows (64-bit)

  • Windows Server 2019
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2012
  • Windows 10
  • Windows 8
  • Windows 7

Windows (32-bit)

  • Windows 10
  • Windows 7


  • macOS 10.15
  • macOS 10.14
  • macOS 10.13


  • CentOS 8.0
  • CentOS 7.7
  • Fedora 31
  • Fedora 30
  • Fedora 29
  • Linux Mint 19
  • Red Hat Enterprise Linux 8.0
  • SUSE Linux Enterprise Server 15 SP1
  • SUSE Linux Enterprise Server 15
  • Ubuntu 19.10
  • Ubuntu 19.04
  • Ubuntu 18.04
  • Ubuntu 16.04

Resolved Issues

The resolved issues are grouped as follows.

  • The screen size of the guest operating system for vRealize Automation or vCloud Director virtual machines does not match the VMware Remote Console screen size.

    When you use the VMware Remote Console Windows or Linux client to access a virtual machine in vRealize Automation or vCloud Director, changing the size of the VMware Remote Console window does not change the resolution of the guest operating system, even if the virtual machine has VMware Tools installed.

    This issue has been resolved in this release.

  • In some environments, operations on vSphere virtual machines respond slowly or do not finish.

    If VMware Remote Console has connected to vSphere machines in certain environments, operations such as powering those virtual machines on and off may be performed slowly or fail to complete.

    This issue has been resolved in this release.

  • On newer Linux distributions, terminal-based installation or online upgrade may fail.

    Version 5 of the ncurses library is required to install VMware Remote Console. However, newer versions of some Linux distributions, such as Fedora 28, Ubuntu 19.04, and SUSE Linux Enterprise Server 15, include only version 6 by default. This may cause the online upgrade process and terminal-based installation process to fail.

    This issue has been resolved in this release.

  • The Wayland protocol is not supported.

    VMware Remote Console requires Xorg and does not install or run under Wayland sessions. Installation errors occur on newer operating systems that use Wayland, such as Fedora 25.

    This issue has been resolved in this release.

Known Issues

The known issues are grouped as follows.

  • The VMware Remote Console macOS App Store client may react slowly when performing passthrough on a mass storage device.

    When a mounted mass storage device is passed through to a remote virtual machine, the VMware Remote Console macOS client may freeze for several seconds.

    Workaround: Manually unmount the mass storage device from the host operating system before initiating passthrough in VMware Remote Console.

  • VMware Remote Console does not launch on macOS 10.13 or later.

    The Mac displays a System Extension Blocked message when you attempt to launch VMware Remote Console on macOS 10.13 or later versions.

    Workaround: As a user with administrator privileges, go to System Preferences > Security > Privacy. Under the General tab, near the bottom, you see a message about VMware software being blocked. Click Allow. For more information, see Knowledge Base Article 2151770.

  • Some device operations are not supported on macOS.

    When you access virtual machines using the VMware Remote Console macOS client, you cannot perform certain device operations. For example, you cannot add new devices or display sound card settings. The specific operations are noted in the documentation.

    Workaround: None.

  • VMware Remote Console and VMware Workstation cannot be installed on the same computer.

    Because certain components are shared between VMware Remote Console and VMware Workstation, these products cannot both be installed on the same Linux machine.

    Workaround: None.

  • VMware Remote Console automatically closes when the virtual machine is powered off.

    When you power off a virtual machine that is being accessed by the VMware Remote Console Linux client, the client automatically closes. You cannot perform operations on the powered-off virtual machine through VMware Remote Console.

    Workaround: None.

  • Virtual machines automatically power on.

    When you access a powered-off virtual machine with VMware Remote Console, the virtual machine is automatically powered on.

    Workaround: None. If you need to perform operations on a powered-off virtual machine through VMware Remote Console, power off the virtual machine after accessing it.