Simply right click it and select update driver and then choose “let Windows find the best driver”, wait until the process finishes and then close the dialog. In most cases this will correct the issue if you had an outdated driver left behind if you upgraded Vmware Workstation or player. Unable to install the virtual network adapter in VMWare workstation 15 and Virtual box 6 - Windows 10 Hello Experts, I am unable to install virtual Ethernet adapter (host only and bridge) on both VM Ware workstation pro 15 and Virtual box 6. Upgrading Windows Server 2016 Domain Controller DC to Windows Server 2019 20th February 2019 Delete all MAILER-DAEMON notifications from Postfix queue: 18th January 2019 michael@michaelfoster82.co.uk. Solution 3: Remove the hcmon.sys driver. The HCMON driver might be installed. One possible solution is to remove the hcmon.sys driver. Follow these steps: 1) Go to Device Manager. 2) Click View Show hidden devices. 3) Double-click Non-Plug and Play Drivers. 4) Right-click hcmon and click Uninstall. 6) Delete the C: Windows system32 drivers.
The VMware Workstation and Fusion team is excited to announce the release of our 20H2 Technology Previewfeaturing the first drop of our DirectX 11 support!
Quick download links:
Workstation Pro for Windows
Workstation Pro for Linux
To get started with DX11, VMware Tools needs to be upgraded, and the Virtual Hardware Compatibility version must be set to v18. Existing VMs can be upgraded by adjusting the virtual hardware compatibility while the VM is powered off. After power-on, you can then upgrade VMware tools as you normally would. With new VMs you may need to manually set the virtual hardware version to v18 before installing, so double check.
Committed to our users, we’ve been working hard on this feature for many years, and so we welcome your feedback!
Let us know your experience! Does your favourite game work? Glitchy? Looks perfect? Help us improve by sharing in our Workstation Tech Preview Community Forum!
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?
This article will :
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. *
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.
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.
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.
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.