- Windows Server; Contact; Fix: VMRC Installation Windows 10 Pro error: failed to install the hcmon driver Published by Tyler Woods on January 31.
- I am sticking this in vSphere forum so eyeballs see it. I am sorry, I blame VMWare for making reporting this problem difficult. I previously successfully signed in to the forum using “Google Chrome, Version 84.0.4147.105 (Official Build) (64-bit)” on Windows 10.
Fix: VMRC Installation Windows 10 Pro error: failed to install the hcmon driver. Failed to install the hcmon driver and then the installer would exit. To get around this, I launched an elevated command prompt and executed the installer through the shell. How to install Synology NFS VAAI VIB on vSphere.
Device drivers improve sound, graphics, networking, and storage performance. If you perform a custom VMware Tools installation or reinstallation, you can choose which drivers to install.
The set of drivers that are installed when you install VMware Tools depends on the guest operating system and the VMware product. For detailed information about the features or functionality that these drivers enable, including configuration requirements, best practices, and performance, see the documentation for your VMware product. The following device drivers can be included with VMware Tools.
On Windows guest operating systems whose operating system is Windows Vista or later, the VMware SVGA 3D (Microsoft - WDDM) driver is installed. This driver provides the same base functionality as the SVGA driver, and it adds Windows Aero support.
For example, Windows Server 2008 defaults to LSI Logic SAS, which provides the best performance for that operating system. In this case, the LSI Logic SAS driver provided by the operating system is used.
VMware supplies a special SCSI driver for virtual machines that are configured to use the BusLogic virtual SCSI adapter. Virtual machines do not need this driver if they do not need to access any SCSI devices or if they are configured to use the LSI Logic virtual SCSI adapter.
The driver is included as part of the VMware Tools package or comes bundled with VMware ESX/ ESXi. It is available on the host as a floppy image at /vmimages/floppies/vmscsi.flp. The driver can be used in Windows XP, Windows Server 2003, or Windows 2000.
When you install VMware Tools, a VMXNET NIC driver replaces the default vlance driver.
- File Introspection Driver: The File Introspection driver uses the hypervisor to perform antivirus scans without a bulky agent. This strategy avoids resource bottlenecks and optimizes memory use.
- Network Introspection Driver: The Network Introspection driver supports NSX for vSphere Activity Monitoring.
Do not delete or replace existing inbox drivers for Linux that are distributed by your OS vendors. Deleting or replacing these drivers might cause conflict with future updates to the drivers. Contact your OS vendor or OS community for availability of specific updates to drivers.
See http://kb.vmware.com/kb/2073804 for information about availability, maintenance, and support policy for inbox drivers for Linux.
If you use Workstation or Fusion, you can install the Shared Folders component. With Shared Folders, you can easily share files among virtual machines and the host computer. The VMHGFS driver is a file system redirector that allows file system redirection from the guest operating system to the host file system. This driver is the client component of the Shared Folders feature and provides an easy to use alternative to NFS and CIFS file sharing that does not rely on the network. For Linux distributions with kernel version 3.10 and later, a new FUSE based Shared Folders client is used as a replacement for the kernel mode client.
VMware Tools installation include the VMware AppDefense, a security management and monitoring solution. AppDefense agent can be installed on the guest virtual machine using the VMware Tools installer. However, VMware Tools cannot install the AppDefense component automatically. You need to install the component manually.
VMware Remote Console | 1 June 2017 | Build 5606693 Check back for additions and updates to these release notes. Last Document Update: 1 June 2017 |
What's in the Release Notes
Vsphere Client Failed To Install Hcmon Driver Windows 10 64-bit
These release notes cover the following topics.
What's New
VMware Remote Console 10.0 includes the following new features.
- There are security updates to several libraries.
- The Linux client is now localized.
NOTE: The Linux installer has not been localized. - The Linux client is now updated to use GTK 3.
Compatibility and Installation
You can install this release on the following host operating systems.
64-bit and 32-bit Windows
- Windows Server 2012 R2
- Windows Server 2012
- Windows Server 2008 R2 SP1
- Windows Server 2008 R2
- Windows 7
- Windows 8.1
- Windows 8
- Windows 10
Mac
- Apple OS X 10.10
- Apple OS X 10.11
- macOS 10.12
Vsphere Client Failed To Install Hcmon Driver Windows 10 Bootable
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.
Vsphere Client Failed To Install Hcmon Driver Windows 10 32-bit
VMware Remote Console for vSphere
VMware Remote Console for vRealize Automation
Fixed Issues
The following known issues are fixed in this release.
Windows
- Remote Console displayed an empty, black console when connecting to a virtual machine.
Known Issues
Vsphere Client Failed To Install Hcmon Driver Windows 10 Pro
The following issues are known to affect this release.
General Issues
- Starting VMware Remote Console from a terminal session might result in the following message:
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:
vmrc.exe -?
Windows
- When connected 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. - 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 .msi installer from a command prompt window that you opened with Administrator privileges.
Mac
- 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
- 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: None - 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 - The Help link does not resolve.
Workaround: Open a browser directly to www.vmware.com/support/pubs/vmrc_pubs.html - Remote Console automatically powers on virtual machines when connecting to virtual machines that are powered off.
Workaround: None - Remote Console automatically closes when a remote virtual machine shuts down.
Workaround: None - Remote Console cannot be installed on the same virtual machine as VMware Workstation or VMware Workstation Player.
Workaround: None