Hi Everyone -
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)
Steps to manually remove the hcmon.sys driver from the server: Right-click My Computer and click Manage. Click Device Manager. Click View Show hidden devices. Double-click Non-Plug and Play Drivers. Right-click VMware hcmon and click Uninstall. Rename the C: windows system32 drivers hcmon.sys file to hcmon.sys.old. Jul 18, 2019 Steps to manually remove the hcmon.sys driver from the server: Right-click My Computer and click Manage. Click Device Manager. Click View Show hidden devices. Double-click Non-Plug and Play Drivers. Right-click VMware hcmon and click Uninstall. Rename the C:windowssystem32drivershcmon.sys file to hcmon.sys.old. 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. Aug 18, 2018 Hcmon on October 2, at 3: If the hcmon troubleshooting steps did not resolve your hcmon. Memtest86 will now be installed on your USB and you are ready to test for the possible source hcon hcmon. Ynk on Hcmon 9, at 2: System File Checker will begin scanning for hcmon. Problem — Failed to install hcmon driver: Even VMware devs are sometimes too. By default, LES blocks the VMWare driver “hcmon” because it disconnects USB devices from the host machine and connects them to Virtual Machines. It does this in a manner that enables the Virtual Machine to bypass the protection provided by LES.
- 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 FilesCommon FilesVMwareDrivershcmonWin7hcmon.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 FilesCommon FilesVMwareDrivershcmonWin7hcmon.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 FilesCommon FilesVMwareDrivershcmonWin7hcmon.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 FilesVMwareUSBx64DIFXAPI.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 FilesCommon FilesVMwareDrivershcmonWin7hcmon.inf failed verification| winerror code 2148204812 (A certificate was explicitly revoked by its issuer.)
Hcmon Driver Vmware Download
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.033-04:00| inst-build-10689111| I1: FindVMwareInSystemTrustedPubStore: didn't find certificate in system trusted publisher store
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_MACHINESystemCurrentControlSetServiceshcmonDeleteFlag| 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 FilesCommon FilesVMwareDrivershcmonWin7hcmon.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 FilesCommon FilesVMwareDrivershcmonWin7hcmon.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 FilesCommon FilesVMwareDrivershcmonWin7hcmon.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
Compatible with Windows 10, 8, 7, Vista, XP and 2000
Optional Offer for WinThruster by Solvusoft | EULA | Privacy Policy | Terms | Uninstall
Overview of Hcmon.sys
What Is Hcmon.sys?
Hcmon.sys is a type of SYS file associated with VM Ware Workstation 3.0 Upgrade developed by VMWare for the Windows Operating System. The latest known version of Hcmon.sys is 1.0.0.0, which was produced for Windows. This SYS file carries a popularity rating of 1 stars and a security rating of 'UNKNOWN'.
What Are SYS Files?
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. Windows).
Hcmon Driver Vmware 10
Other SYS files are critical system files called 'kernel mode device drivers' which are used to power the Windows operating system. Files such as 'CONFIG.SYS' contain configuration settings and specify what device drivers should be loaded by the operating system. Without driver files such as hcmon.sys, you wouldn't be able to do simple tasks such as printing a document.
Why Do I Have SYS Errors?
SYS file errors are typically caused by faulty hardware or corrupt device driver files. Because of the importance of Hcmon.sys in the functionality of VM Ware Workstation 3.0 Upgrade and other Windows functions, any corruption or damage to this file can create critical system errors in the form of a 'blue screen of death' (BSOD). Please see 'Causes of Hcmon.sys Errors' below for more information.
When Do SYS Errors Occur?
SYS errors, such as those associated with hcmon.sys, most often occur during computer startup, program startup, or while trying to use a specific function in your program (eg. printing).
Failed To Install Hcmon Vmware
Common Hcmon.sys Error Messages
The majority of hcmon.sys errors that you encounter will be 'blue screen of death' errors (also know as a 'BSOD' or 'STOP error') that occur in Windows XP, Vista, 7, 8, and 10:
- 'A problem has been detected and Windows has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: Hcmon.sys.'
- ':( Your PC ran into a problem and needs to restart. We’re just collecting some info, and then we’ll restart for you. If you would like to know more, you can search online later for this error: hcmon.sys.'
- 'STOP 0x0000000A: IRQL_NOT_LESS_EQUAL – hcmon.sys'
- 'STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED – hcmon.sys'
- 'STOP 0×00000050: PAGE_FAULT_IN_NONPAGED_AREA – hcmon.sys'
In most cases, you will experience hcmon.sys blue screen errors after you’ve installed new hardware or software. These hcmon.sys blue screens can appear during program installation, while a hcmon.sys-related software program (eg. VM Ware Workstation 3.0 Upgrade) is running, while a VMWare driver is being loaded, or during Windows startup or shutdown. Keeping track of when and where your STOP error occurs is a critical piece of information in troubleshooting the problem.
Comments are closed.