• Vmware Remote Console Failed To Install Hcmon Driver Windows 10 Dell
• Vmware Remote Console Failed To Install Hcmon Driver Windows 10 32 Bit
• Vmware Remote Console Failed To Install Hcmon Driver Windows 10 Asus

What's in the Release Notes

Jan 15, 2016 Launch Windows PowerShell as Administrator; Change directory to the folder where the VMware-VMRC-xxx.msi is located; Execute.

These release notes cover the following topics.

• This happens because Configuration Manager does not have drivers for a VMware Virtual Machine. A lot of people get stuck here because they forget to import VMXnet3 drivers to their boot image. Unlike Dell, VMware doesn’t provide the driver package file in.cab format. You have to import VMware drivers into your WinPE boot image.
• Hi, I can't install Vmware player on my laptop. I tried a lot of things but nothing worked. It was working fine but after reinstalling windows 10 I can't install any kind of Vmware product. It says 'failed to install hcmon' every time. I wasted 2 days on the internet to find a solution and tried a lot of things but nothing worked.

What's New

Vmware Remote Console Failed To Install Hcmon Driver Windows 10 Dell

VMware Remote Console 10.0.2 includes the following changes.

• Support for Windows Server 2016 and macOS 10.13
• The Windows installer changed from .msi to .exe format.
• The VMware Remote Console project now uploads its corresponding Open Source Disclosure Package (ODP) as part the release process.
• The zlib compression library is updated from 1.2.8 to 1.2.11.
• The libcurl data transfer library is updated from 7.51.0 to 7.56.1.
• OpenSSL is updated from 1.0.2k to 1.0.2m.
• There are additional fixes as described in Fixed Issues.

Compatibility and Installation

You can install this release on the following host operating systems.

64-bit and 32-bit Windows

• Windows Server 2016
• Windows Server 2012 R2
• Windows Server 2012
• Windows Server 2008 R2 SP1
• Windows Server 2008 R2
• Windows 10
• Windows 8.1
• Windows 8
• Windows 7

Mac

• macOS 10.13
• macOS 10.12
• Apple OS X 10.11
• Apple OS X 10.10

Linux

• VMware Remote Console generally runs on the same Linux offerings as VMware Workstation versions that are released around the same time.

  For more information, see the VMware Compatibility Guide.

Documentation

See the following guides for information about installing and using VMware Remote Console.

VMware Remote Console for vSphere
VMware Remote Console for vRealize Automation

Fixed Issues

The following issues are fixed in this release.

Windows

• Corrects a USB driver from VMware Remote Console 10.0.0 and 10.0.1 that had not been signed by Microsoft.
• Allows the Windows USB arbitrator service to start after VMware Remote Console is installed.

  The issue only occurred on 64-bit Windows 8 without a certain runtime environment. The runtime environment is not part of Windows 8 by default but might or might not be present depending on other applications.

Mac

• Corrects issues that prevented the Mac installer from completing and required you to launch the application again to finish.

Known Issues

The following issues are known to affect this release.

General Issues

• Cannot connect to virtual machines hosted on ESXi 5.1

  ESXi 5.1 does not support TLS versions greater than 1.0. The following error occurs.
  Unable to connect to the MKS: Could not connect to pipe . pipevmware-authdpipe within retry period.
  Workaround: Configure VMware Remote Console to use TLS 1.0.

  1. Open the VMware Remote Console configuration file in a text editor.
     Windows
     C:ProgramDataVMwareVMware Remote Consoleconfig.ini
     Linux
     /etc/vmware/config
     Mac
     /Library/Preferences/VMware Remote Console/config
     
  2. Add or edit the TLS protocols entry. Include TLS 1.0.
     tls.protocols=tls1.0,tls1.1,tls1.2
  3. Save and close the configuration file.
• NIC disconnects from vSphere Distributed Switch (vDS) portgroup

  You try to edit virtual machine network settings by connecting through VMware Remote Console, and your receive an Invalid device network adapter error.
  Workaround: Follow the guidelines in Knowledge Base Article 2151096.

• VMware Remote Console URL message

  Starting VMware Remote Console from a Windows or Linux terminal session causes the following message to appear:
  This application must be launched from a vmrc URL
  The message appears when you omit the URL in the command. By design, you start VMware Remote Console from a client such as vSphere or vRealize Automation, or with a vmrc:// URL.
  For help with the VMware Remote Console command line, enter:
  Windows
  vmrc.exe -?
  Linux
  vmrc --help
  Mac
  not available
  

Windows

• Keyboard hook timeout message

  When connecting to a virtual machine, VMware Remote Console might display the following message:
  The keyboard hook timeout value is not set to the value recommended by VMware Remote Console
  By design, you click OK to update the timeout value, then log out of Windows to ensure that the update takes effect.

• HCmon driver error

  Installing VMware Remote Console on a system where other VMware applications have been installed might result in the following error:
  Failed to install the HCmon driver
  Workaround: Go to Task Manager, Services tab, and stop the VMUSBArbService. Then, proceed with installation.
  Alternatively, launch the .exe installer from a command prompt window that you opened with Administrator privileges.

Mac

• VMware Remote Console does not launch on macOS 10.13

  The Mac displays a System Extension Blocked message when you attempt to launch VMware Remote Console on macOS 10.13.
  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.

• Device options

  There are device-related options that are not available when running VMware Remote Console on a Mac. For example, you cannot add new devices, or display sound card settings. Unavailable Mac options are noted where applicable in the documentation.

Linux

• Updates do not download and install

  You click a vmrc:// link to launch VMware Remote Console from the browser. When you try to download and install VMware Remote Console updates, you receive the following error during download.
  An error occurred while reading/writing files. Try again later and if the problem persists, contact your system administrator
  Workaround: Do one of the following.

  • Launch VMware Remote Console from the command line, with a minimum syntactically viable URL. For example:
    sudo vmrc vmrc://x/?moid=x
    
  • Download the update from https://www.vmware.com/go/download-vmrc and apply it manually.

  After using one of the workarounds, the update installs, but VMware Remote Console displays the following error:
  Install of VMware Remote Console failed. Contact VMware Support or your system administrator.
  Close and relaunch VMware Remote Console. Go to Help > About VMware Remote Console to verify that the update installed.

• VMware Remote Console on Debian 8.7.1 does not open remote virtual machines

  You successfully install VMware Remote Console on Debian 8.7.1, but it does not launch. When run from the console, the following message appears:
  Loop on signal 11.
  In addition, the log file under /tmp/vmware-$USER/ contains a panic and backtrace.
  Workaround: Use VMware Remote Console 9.0.

• VMware Remote Console on Ubuntu 17.04 does not display certificates for viewing

  You use VMware Remote Console on Ubuntu 17.04 to connect to an ESXi host that has an invalid or untrusted security certificate, and a certificate warning appears. When you click to view the certificate for inspection, an empty dialog appears, and you can only close the dialog.
  Workaround: None

• 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.
  Workaround: None

• Help link does not resolve

  You click the Help option from within VMware Remote Console and receive a file not found error.
  Workaround: Open a browser directly to www.vmware.com/support/pubs/vmrc_pubs.html

• Virtual machines automatically power on

  VMware Remote Console automatically powers on virtual machines when connecting to virtual machines that are powered off.
  Workaround: None

• VMware Remote Console automatically closes

  VMware Remote Console automatically closes when the remote virtual machine shuts down.
  Workaround: None

• VMware Workstation or VMware Workstation Player

  VMware Remote Console cannot simultaneously be installed on the same machine as VMware Workstation or VMware Workstation Player.
  Workaround: None

I tried the install the most recent version of VMRC which can be found here and I got this error message during the installation:

Vmware Remote Console Failed To Install Hcmon Driver Windows 10 32 Bit

I found the KB2130850 which mentioned that I should uninstall all vSphere Client instances, install VMRC and reinstall all vSphere Client instances. Unfortunately this was not the solution. I have then uninstalled the Horizon View Client too to be on the safe side. Again this was also not the solution.

I have then checked the vminst.log which can be found in the %TEMP% folder and saw the following error messages:

VNLCopyFileToSystemDir: Copying ‘C:Program Files (x86)Common FilesVMwareUSBhcmon.sys’ to ‘C:Windowssystem32drivershcmon.sys’
VNLGetLocalizedString: Failed to allocate a localized string 0x00000020: 317
VNLCopyFileToSystemDir: Failed to copy file: “C:Windowssystem32drivershcmon.sys”. (null) [32]
VNL_InstallHcmon: Failed to create service for hcmon driver.

This looked like that there are not sufficient permissions to copy the hcmon.sys to the destination folder, although the installer told me that he is using elevated permissions:

Because you haven’t “Run as Administrator” for msi packages I used an elevated cmd prompt to start the msi with Administrator permissions and lo and behold VMRC was installed without problems. There are 2 possibilities from my point of view why this happened.

1. The elevation process of setups was little bit changed in Windows 10
2. The hcmon.sys file was already there and the elevated permission was to less to replace it.

I did a quick check about these possibilities and it was 2. When there is an existing hcmon.sys (from vSphere Client), VMRC installer can’t replace it even if the installer gets elevated for installation. The only possibility was to start the installer as Administrator to get the hcmon.sys in the C:WindowsSystem32 directory replaced.

Vmware Remote Console Failed To Install Hcmon Driver Windows 10 Asus