VMware Workstation

 View Only

 VMInstallHcmon Install error

medicnick83's profile image
medicnick83 posted May 30, 2024 05:19 PM

Hi all,

I've googled, Youtube'd the **** outta this error and I can't find a resolution so I'm going to ask it here.

I recently downloaded VMware-workstation-full-17.5.2-23775571 and tried to install it - it gets nice and far and then just sits and doesn't move.

It installs nicely till I get to to a point where the Virtual Network Editor pops up and immediately goes (Not Responding) and if you leave it, it (the installation) eventually fails.

If you force close the VNE window - installation fails with the following error:

And then the inevitable image appears
Can someone please guide me on how to fix this - all the searches are old and nothing works and we are now mid way through 2024 and I don't see how this can't be fixed.
I'm running Windows 11 23H2 and always do updates as soon as they come out so my 11 is as updated as it can be as of this post.
Dhairya Tomar's profile image
Broadcom Employee Dhairya Tomar

@medicnick83Request you to share vminst and vmmsi logs from %temp% folder

medicnick83's profile image
medicnick83

Logs link: https://uploadnow.io/f/zNvrxhg

Dhairya Tomar's profile image
Broadcom Employee Dhairya Tomar

@medicnick83Thanks for the sharing the requested info, ticket has been raised internally, relevant team will look into the same.

medicnick83's profile image
medicnick83

Thank you Dhairya.

Dhairya Tomar's profile image
Broadcom Employee Dhairya Tomar

@medicnick83 Please try below steps and let us know if issue still persists-

1. Clean Uninstall Workstation Pro using below-

Uninstall WS Pro/Player.
Go to this location - C:\ProgramData\VMware and delete the folders for VMware Workstation and VMware Player.
Go to this location - C:\Users\dtomar\AppData\Roaming\VMware and delete all the files inside
Go to this location - C:\Program Files (x86)\VMware and delete the folders for VMware Workstation and VMware Player.

2. Please stop related services if any by "sc stop serviceName" in cmd with administrative with priviledge

sc stop VMUSBArbService

sc stop hcmon

sc stop vmusb

3. Remove drivers:

del C:\Windows\System32\drivers\hcmon.sys

del C:\Windows\System32\drivers\vmusb.sys

remove hcmon, vmusb from here C:\Windows\System32\DRVSTORE

4. Remove registry related to WS Pro:

reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc." /f

reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc." /f

5.

     a.Stop 'VMware USB Arbitration service' from services.msc if running.

     b.Delete below registry entries for

         i."VMUSBArbService from "Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VMUSBArbService"

         ii."Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmusb"

     c.Delete same entries from CurrentControlSet001 if any.

6. Delete usb folders from "C:\Program Files (x86)\Common Files\VMware\USB"

7. Delete hcmon and vmusb from  C:\Program Files\Common Files\VMware\Drivers\hcmon & C:\Program Files\Common

        Files\VMware\Drivers\vmusb

8. Reboot your system and install WS Pro.

Dhairya Tomar's profile image
Broadcom Employee Dhairya Tomar

@medicnick83 Please let us know if the clean installation steps shared worked for you or NOT.

Also you can try upgrading to WS 17.6 and let us know if the issue is resolved.

Dhairya Tomar's profile image
Broadcom Employee Dhairya Tomar

@medicnick83 Please let us know if with the steps provided, issue got resolved or NOT.

Also requesting yoo to upgrade to WS 17.6.1 and update.

medicnick83's profile image
medicnick83

Hi all,

So, as you requested, I downloaded and installed VMware-workstation-full-17.6.1-24319023.exe and it does the same thing.

Dhairya Tomar's profile image
Broadcom Employee Dhairya Tomar

medicnick83 By any chance you tried the clean install steps I have shared in previous comment?

Dhairya Tomar's profile image
Broadcom Employee Dhairya Tomar

medicnick83 Requesting you to try clean uninstall of WS and try to upgrade to WS 17.6.3 and let us know if the issue still persists.