Failed to install the hcmon driver vmware как исправить

Обновлено: 07.07.2024


What is the HCMON driver?

HCMON driver is a virtual USB driver. It allows your physical USB ports to connect to the virtual machines.

How to fix this error?

The error occurs can be due to different issues. We post the top 5 solutions in this article. You can fix this error with one of these solutions. You may not have to try them all. Just work your way down until you find the one that works for you.

Solution 1: Install the product as an administrator

1) Right-click on the downloaded setup file.


Solution 2: Update the drivers

Corrupted drivers especially graphics drivers can cause this error. To fix the problem, try to update the drivers.

Driver Easy will automatically recognize your system and find the correct drivers for it. You don’t need to know exactly what system your computer is running, you don’t need to risk downloading and installing the wrong driver, and you don’t need to worry about making a mistake when installing.

You can update your drivers automatically with either the FREE or the Pro version of Driver Easy. But with the Pro version it takes just 2 clicks (and you get full support and a 30-day money back guarantee):

1) Download and install Driver Easy.

2) Run Driver Easy and click Scan Now. Driver Easy will then scan your computer and detect any problem drivers.


3) Click the Update button next to the flagged drivers to automatically download and install the correct version of their driver (you can do this with the FREE version). Or click Update All to automatically download and install the correct version of all the drivers that are missing or out of date on your system (this requires the Pro version – you’ll be prompted to upgrade when you click Update All).


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\hcmon.sys file.

7) Restart the computer.

Solution 4: Install the product using PowerShell

Try to install the product in PowerShell. Follow steps below:


2) Go to the location where you saved the setup file. This is to get the msi name.

3) Type .\xxxx.msi in PowerShell command prompt and press Enter on your keyboard. XXXX means the name of msi file. Replace it with your msi file name.




Что такое драйвер HCMON?

Решение 1. Установите продукт от имени администратора.

Когда вы устанавливаете продукт, вам необходимо установить драйвер hcmon. Windows может видеть это как пользователь, добавляющий оборудование к ПК. Но у этого пользователя нет разрешения на это. В этом случае эта ошибка может возникнуть. Попробуйте установить продукт от имени администратора:

1) Щелкните правой кнопкой мыши на загруженном установочном файле.

2) Нажмите Запустить от имени администратора. Если вы не видите опцию «Запуск от имени администратора», это решение не применимо к вам. Пропустите и перейдите к другим решениям.


Решение 2. Обновите драйверы

Поврежденные драйверы, особенно графические драйверы, могут вызвать эту ошибку. Чтобы устранить проблему, попробуйте обновить драйверы.

Если у вас нет времени, терпения или навыков работы с компьютером для обновления драйверов вручную, вы можете сделать это автоматически с Водитель Легко.

Driver Easy автоматически распознает вашу систему и найдет для нее правильные драйверы. Вам не нужно точно знать, на какой системе работает ваш компьютер, вам не нужно рисковать загрузкой и установкой неправильного драйвера, и вам не нужно беспокоиться об ошибках при установке.

Вы можете автоматически обновить драйверы с помощью БЕСПЛАТНОЙ или Профессиональной версии Driver Easy. Но в версии Pro это займет всего 2 клика (и вы получите полную поддержку и 30-дневную гарантию возврата денег):

2) Запустите Driver Easy и нажмите Сканировать сейчас. Driver Easy проверит ваш компьютер и обнаружит проблемы с драйверами.



Решение 3. Удалите драйвер hcmon.sys

Возможно, драйвер HCMON установлен. Одним из возможных решений является удаление драйвера hcmon.sys. Следуй этим шагам:

1) Перейти к Диспетчер устройств.

2) Нажмите Посмотреть > Показать скрытые устройства.


3) Двойной щелчок Драйверы без Plug and Play.

4) Щелкните правой кнопкой мыши hcmon и нажмите Удалить.

6) Удалить C: \ Windows \ system32 \ Drivers \ hcmon.sys файл.

7) Перезагрузите компьютер.

Решение 4. Установите продукт с помощью PowerShell

Попробуйте установить продукт в PowerShell. Следуйте инструкциям ниже:

1) Введите «powershell» в поле поиска. Щелкните правой кнопкой мыши Windows PowerShell (Имя может отличаться в зависимости от используемой версии Windows.) И нажмите Запустить от имени администратора.


2) Перейдите в место, где вы сохранили установочный файл. Это чтобы получить имя MSI.

3) Тип .\ xxxx.msi в командной строке PowerShell и нажмите Войти на вашей клавиатуре. XXXX означает имя файла MSI. Замените его своим именем файла MSI.

В моем случае мой файл «VMware-VMRC-10.0.1-5898794»:


Поэтому я набрал «. \ VMware-VMRC-10.0.1-5898794.msi»:



The solution that resolved the error for me was to run the installer with elevated privileges.

24 thoughts on “VMware VMRC: Failed to install hcmon driver”

Thanks! That was my problem

That’s sorted it for me too, thanks. Even VMware devs are sometimes too lazy to check their work. Installer should request elevated privileges itself.

Great, it helped me too

Worked for me! Thanks!

Another thanks, this fixed my issue.

Perfect! It’s work!

Worked for me. Thank you very much!

Worked great!! Thanks

This problem was so annoying and these steps were so simple and worked very well! Thanks so much!

Dude, you are a life saver. I have been struggling with it for the past few days.
thanks

no it is not working for me

Thanks, it worked !

why don’t you use rught click on MSI file and choose “run as administrator”? isn’t it thw same?

for me it didn’t work neither through command line no through context menu

MSI’s don’t give you the option to run as administrator on the context menu. You can add the functionality using steps similar to the below however I normal just do it via a administrator CMD.

If you get the MSI installer to create a log file does it show anything interesting

msiexec /i “C:\Path\Installer.msi” /L*V “C:\log\example.log”

Thank you Man solved my Issue

tnks …solution is very good …

Your solution solve my hard problem in few minutes. Without this part in my vm didn`t work bridget connection, and I can`t finished my job in time. Thank you!

i am getting the same error

Nice. Worked for me. Thank you.

Hello,
it did not worked for me on windows 10 build 1607
it may help someone else :
my user is in administrator group and as a workaround i switched user (ctrl-alt del -> switch user and choosed administrator)
and then i ran the msi as administrator and it installed properly.
i did not had to uninstall anything (except vmware integration client 6.0 but i am not sure if it is relevant to this issue)

Leave a Comment Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.


Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
  • VMware Technology Network
  • :
  • Desktop Hypervisor
  • :
  • VMware Workstation
  • :
  • VMware Workstation Pro Discussions
  • :
  • vminstallhcmon failed to install the hcmon driver .
hexatriene
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Email to a Friend
vminstallhcmon failed to install the hcmon driver error - certificate was explicitly revoked by its issuer

Today I got notice that the 15.0.3 update had been released. In the process of installing it - I got the dreaded vminstallhcmon failed to install the hcmon driver error.

Scouring the web - I tried the suggestions:

- running installer as admin (though this shouldn't matter because the .msi automatically prompts for UAC elevation to admin)

- running install from elevated command prompt

- confirming that hcmon.inf nor hcmon.sys was not cashed in DRVSTORE or elsewhere on disk

- no devices in Device Manager in "Non Plug'n Play devices" - in fact the section doesn't exist (even after displaying hidden items)

from the vminst.log - it seems like the issue might be a revoked certificate on the hcmon.inf file?

2019-03-19T11:59:14.049-04:00| inst-build-10689111| I1: BaseDriverManager::DifxApiLogCallback: hcmon (Difx): hcmon.inf: checking signature with catalog 'C:\Program Files\Common Files\VMware\Drivers\hcmon\Win7\hcmon.cat ' .

2019-03-19T11:59:14.049-04:00| inst-build-10689111| E1: BaseDriverManager::DifxApiLogCallback: hcmon: Signature verification failed while checking integrity of driver package 'hcmon.inf' ('C:\Program Files\Common Files\VMware\Drivers\hcmon\Win7\hcmon.inf').| winerror code 2148204812 (A certificate was explicitly revoked by its issuer.)

At this point I can't install even the previously available 15.0.2 - I get the same error

larger log section:

2019-03-19T11:59:13.635-04:00| inst-build-10689111| I1: VNLInstallLegacyInf: driverId:hcmon cmd:install hcmoninf args:5;Win7

2019-03-19T11:59:13.635-04:00| inst-build-10689111| I1: launching process for: install hcmoninf 5;Win7

2019-03-19T11:59:13.682-04:00| inst-build-10689111| I1: VNLSpawn64BitVnetlibTask: launched process: pid 7472 tid 4328

2019-03-19T11:59:13.682-04:00| inst-build-10689111| I1: VNLSpawn64BitVnetlibTask: Waiting for process, 0 loops

2019-03-19T11:59:13.901-04:00| inst-build-10689111| I1: VNLInstallLegacyInf: driverId:hcmon cmd:install hcmoninf args:5;Win7

2019-03-19T11:59:13.971-04:00| inst-build-10689111| E2: GetSpecificProductInstallPath: could not find product registry key

2019-03-19T11:59:13.971-04:00| inst-build-10689111| E2: GetSpecificProductInstallPath: could not find product registry key. Try the WoW path.

2019-03-19T11:59:13.971-04:00| inst-build-10689111| I2: Util_FileExistsW: Found "C:\Program Files\Common Files\VMware\Drivers\hcmon\Win7\hcmon.inf"

2019-03-19T11:59:13.971-04:00| inst-build-10689111| I1: LegacyDriverManager::InstallDriver: Determining whether to install the hcmon driver

2019-03-19T11:59:13.986-04:00| inst-build-10689111| I2: LoadSupportFiles: Successfully loaded C:\Program Files (x86)\Common Files\VMware\USB\x64\DIFXAPI.dll

2019-03-19T11:59:13.986-04:00| inst-build-10689111| I2: LoadSupportFiles: Incremented refcount for module DIFXAPI.dll

2019-03-19T11:59:13.986-04:00| inst-build-10689111| I1: DriverVersionInfo::ReadFromRegistry: Did not find info for hcmon driver

2019-03-19T11:59:13.986-04:00| inst-build-10689111| I1: DInfo_GetDriverInfoFromInf: Got provider for inf: VMware, Inc.

2019-03-19T11:59:13.986-04:00| inst-build-10689111| I2: DInfo_GetDriverInfoFromInf: Got catalog file for inf: hcmon.cat

2019-03-19T11:59:13.986-04:00| inst-build-10689111| I2: DInfo_GetDriverInfoFromInf: Got class name for inf: USB

2019-03-19T11:59:13.986-04:00| inst-build-10689111| I2: DInfo_GetDriverInfoFromInf: Got date/version for inf: 08/28/2018,8.11.6.0

2019-03-19T11:59:14.033-04:00| inst-build-10689111| E1: DInfo_GetDriverInfoFromInf: driver C:\Program Files\Common Files\VMware\Drivers\hcmon\Win7\hcmon.inf failed verification| winerror code 2148204812 (A certificate was explicitly revoked by its issuer.)

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: DriverVersionInfo::IsSameAs: File versions don't match or older

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: BaseDriverManager::IsSameDriverAndPresent: Driver file versions don't match

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: LegacyDriverManager::EvalUpdateNeeded: Determined that hcmon has changed

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: LegacyDriverManager::EvalUpdateNeeded: Prior hcmon info:

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: DriverVersionInfo::Print: Driver version (invalid) 0.0.0.0 is not WHQL (ca ver 0) inf ""

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: LegacyDriverManager::EvalUpdateNeeded: New hcmon info:

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: DriverVersionInfo::Print: Driver version (valid) 8.11.6.0 is not WHQL (ca ver 4998961) inf ""

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I2: UnloadSupportFiles: Decremented refcount for module DIFXAPI.dll

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: LegacyDriverManager::InstallDriver: Uninstalling a prior version hcmon driver

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I2: LoadSupportFiles: Incremented refcount for module DIFXAPI.dll

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: LegacyDriverManager::UninstallDriverImpl: Uninstalling the hcmon driver

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: DriverVersionInfo::ReadFromRegistry: Did not find info for hcmon driver

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: DriverBaseInfo::ReadMultiszFromRegistry: No registry value vwdk.installers

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: DriverInstallerInfo::SetMsiInstallerPresent: Set Msi installer: present

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: LegacyDriverManager::UninstallDriverImpl: Query if old style hcmon legacy driver is installed

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I2: Inst_QueryServiceRunningStatus: Attempting to query service: hcmon

2019-03-19T11:59:14.033-04:00| inst-build-10689111| E1: Inst_QueryServiceRunningStatus: Service could not be opened: ERROR_SERVICE_DOES_NOT_EXIST

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I2: UnloadSupportFiles: Decremented refcount for module DIFXAPI.dll

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: LegacyDriverManager::InstallDriverImpl: Installing new version of the hcmon driver

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: DriverBaseInfo::ReadMultiszFromRegistry: No registry value vwdk.installers

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: DriverBaseInfo::DeleteFromRegistry: No info for driver hcmon to delete

2019-03-19T11:59:14.049-04:00| inst-build-10689111| I2: Util_IsTestSigningEnabled: TestSigning not enabled (no TESTSIGNING token)

2019-03-19T11:59:14.049-04:00| inst-build-10689111| I1: DriverMgmt_TryAddVMwareCerts: Automated cert installation requires test-signing mode

2019-03-19T11:59:14.049-04:00| inst-build-10689111| I1: Util_GetKeyValueDWORD: Cannot query key value HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\hcmon\DeleteFlag| winerror code 2 (The system cannot find the file specified.)

2019-03-19T11:59:14.049-04:00| inst-build-10689111| I1: BaseDriverManager::DifxApiLogCallback: hcmon (Difx): ENTER: DriverPackageInstallW

2019-03-19T11:59:14.049-04:00| inst-build-10689111| I1: BaseDriverManager::DifxApiLogCallback: hcmon (Difx): hcmon.inf: checking signature with catalog 'C:\Program Files\Common Files\VMware\Drivers\hcmon\Win7\hcmon.cat' .

2019-03-19T11:59:14.049-04:00| inst-build-10689111| E1: BaseDriverManager::DifxApiLogCallback: hcmon: Signature verification failed while checking integrity of driver package 'hcmon.inf' ('C:\Program Files\Common Files\VMware\Drivers\hcmon\Win7\hcmon.inf').| winerror code 2148204812 (A certificate was explicitly revoked by its issuer.)

2019-03-19T11:59:14.049-04:00| inst-build-10689111| I1: BaseDriverManager::DifxApiLogCallback: hcmon (Difx): RETURN: DriverPackageInstallW (0x800B0100)

2019-03-19T11:59:14.049-04:00| inst-build-10689111| E1: LegacyDriverManager::InstallDriverImpl: Install of hcmon failed with| winerror code 2148204800 (No signature was present in the subject.)

2019-03-19T11:59:14.049-04:00| inst-build-10689111| E1: LegacyDriverManager::InstallDriverImpl: Cannot locate installed INF location for hcmon of C:\Program Files\Common Files\VMware\Drivers\hcmon\Win7\hcmon.inf| winerror code 3758097154

2019-03-19T11:59:14.049-04:00| inst-build-10689111| I2: UnloadSupportFiles: Closed module handle for DIFXAPI.dll

2019-03-19T11:59:14.049-04:00| inst-build-10689111| I2: UnloadSupportFiles: Module DIFXAPI.dll wasn't unloaded

2019-03-19T11:59:14.064-04:00| inst-build-10689111| I1: ParseCommand: operation: successful

2019-03-19T11:59:14.064-04:00| inst-build-10689111| I1: VNLSpawn64BitVnetlibTask: Done waiting for process, code 0

2019-03-19T11:59:14.064-04:00| inst-build-10689111| I2: VNLSpawn64BitVnetlibTask: process exit code 4

2019-03-19T11:59:14.064-04:00| inst-build-10689111| I1: VNLSpawn64BitVnetlibTask: process was not successful

2019-03-19T11:59:14.064-04:00| inst-build-10689111| I1: VNLInstallLegacyInf: Launched 64-bit process, result FALSE

2019-03-19T11:59:14.064-04:00| USBDeviceInstUtil-build-10689111| I0: Reboot not required

2019-03-19T11:59:14.064-04:00| USBDeviceInstUtil-build-10689111| I0: ERROR: Failed calling VNL_InstallHcmonInf() for service hcmon

2019-03-19T11:59:14.064-04:00| USBDeviceInstUtil-build-10689111| I1: Util_FreeLibrary: Freeing library: 1453785088

2019-03-19T11:59:14.064-04:00| USBDeviceInstUtil-build-10689111| I0: ERROR: Failed to install hcmon

Читайте также: