So you are installing VMRC, PowerCli or vSphere client and getting that really annoying HCMON driver failed to install error, but have no idea where to start?
- When you install VMware Tools, a virtual SVGA driver replaces the default VGA driver, which allows for only 640 X 480 resolution and 16-color graphics. On Windows guest operating systems whose operating system is Windows Vista or later, the VMware SVGA 3D (Microsoft - WDDM) driver is installed.
- اگر در زمان نصب برنامه VMWare Remote Console، با ارور Failed to install the hcmon driver روبرو شده اید، راه حل های ساده این ارور را با هم در این پست خواهیم دید.
- VMware Remote Console on Windows 10 gives ‘Failed to install the hcmon driver’ 2016-08-08 by Jason Trying to install the VMware Remote Console software on a new Windows 10 computer consistently resulted in the error message ‘Failed to install the hcmon driver.’.
This article will :
Failed To Install Hcmon Driver Windows 10 Vmware Iso
- outline what causes the HCMON driver error
- provide top 3 solutions to this annoying problem.
What causes the HCMON driver error
SYS files such as hcmon.sys are third-party (eg.VMWare) device drivers or critical system files that come as part of the Windows operating system. Most SYS files allow internal PC hardware or attached hardware, such as a printer, to communicate with third-party software programs (eg. Web browsers, word processors, VM Ware Workstation 3.0 Upgrade) and the operating system (eg.
The HCMON drive is a virtual USB driver HCMon is a virtual USB driver to allow the connection of your physical USB ports to virtual machines. When your installing the your VMware product of choice, HCMON is installed as a hardware driver, which is the problem. Windows interprets this as a user adding hardware to the PC and in many environments that is something your operating system security or administrator may not automatically allow.
*Note: Several of the following recommendations will reduce the security level of your machine, make sure you understand the implications of doing so. *
Solution 1 - Install “as adminstrator”
If you have administrator access to the PC you are installing on, the first thing to try is to simply right click what you are trying to install and select Run as Administrator. If you don’t have access you’ll have to consult your administrators.
You probably already did this though right? Next…
Failed To Install Hcmon Driver Windows 10 Vmware Windows 10
Solution 2 - Set Lumension Endpoint Security to allow the HCMON driver
LES is a really popular product among organisation s that want to have granular control of what information can be introduced and removed from their environment. Think disallowing or restricting USB access. You could just disable or uninstall LES, but that kind of defeats the purpose of what it’s trying to achieve. Good news, there is a reg setting that LES uses to allow HCMON to be used.
Note you'll need access to the registry and the ability to edit it to do this.
- Enable HCMON by creating a EnableHCMON registry value (DWORD type, Data 1) in HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesSKParameters.
- Reboot if required.
- Install VMWare Client/PowerCli.
- Disable HCMON by removing the EnableHCMON registry value.
- Reboot the endpoint again.
Ensure you have the right version of the .NET framework for the product you are installing
Vmware Client Failed To Install Hcmon Driver Windows 10
Different products need different .NET versions for example as per KB-2053281 vSphere 5.1 client requires Microsoft .NET Framework 3.5.1. Make sure you are using the right version, I usually don’t find this to be a problem most products will check for dependencies and either announce it’s not there or go ahead and install it for you.
Beware of an intermittent known feature issue in vSphere 6
Thought I have never had this issue it is important to know about the issue outlined in KB-2130850. Apparently when attempting to install the VMRC for vSphere 6 on a PC which already has some versions of the vSphere client the install will fail. The recommended fix is to uninstall all versions of the vSphere client, reboot, install the VMRC client and then reinstall the vSphere Client (does anyone still use the old vSphere Client?
I hope you have my luck and never have to do this either, as it sounds messy.
So now you know what the HCMON driver is, why sometimes it causes issues, and how to get around the more commonly known ones.
Hope this was of some help.
Let me know if you encounter anything different or if this helped you out.
VMware Remote Console | 08 December 2015 | Build 3250412 Check for additions and updates to these release notes. Last Document Update: 10 February 2016 |
What's in the Release Notes
The release notes cover the following topics:What's New
VMware Remote Console 8.0 provides complete functionality on virtual machine operations and settings to vSphere administrators, but only limited functionality is available on virtual machine operations such as console, mouse and keyboard operations to vRealize Automation users.
VMware Remote Console 8.0 supports:
- vRealize Automation 6.2.3 with console proxy
- Smart cards
- Auto Update for Windows
- 32-bit Windows
Compatibility and Installation
VMware Remote Console and host OS version compatibility
VMware Remote Console is compatible with the following 64-bit and 32-bit Windows host operating systems:
- 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
VMware Remote Console is also compatible with the following Mac host operating systems:
- Apple OS X 10.8 (Mountain Lion)
- Apple OS X 10.9 (Mavericks)
- Apple OS X 10.10 (Yosemite)
- Apple OS X 10.11 (El Capitan)
Installation Notes for This Release
Read the following documentation for guidance about installing and using VMRC:
Known Issues
This release has the following known issues for Windows OS:
Running VMRC without a URL will fail.
Workaround: Open a URL of the form: vmrc://[<user>|(<ticket-type>:<ticket>)@]<host>[:<port>]/?moid=<VM-id>.VMRC displays an empty, black console when connecting to a virtual machine.
Workaround: None- VMRC might prompt The keyboard hook timeout value is not set to the value recommended by VMware Remote Console when connected to a virtual machine.
Workaround: Click OK to update the value and log out of Windows to ensure the update takes effect. - Installing VMRC client on Windows 10 might fail with an error Failed to install the HCmon driver.
Workaround: Run the elevated command prompt as an Administrator.
This release has the following known issues for Apple OS X:
- VMRC might not add new devices such as DVD and CD-ROM drives or an existing virtual hard disk to a virtual machine.
Workaround: None - VMRC does not display sound card settings.
Workaround: None