VMware Horizon Community
inetwings
Contributor
Contributor

Windows 7 VMWare Horizon Client 4.9 Install Failed

I was trying to install VMware Horizon Client 4.9 on my Windows7 PC.

I found the following lines from log that could have been the cause of error.

MSI (s) (F0:F0) [16:58:16:512]: Product: VMware Horizon Client -- Error 1904. Module D:\Software\VMware\VMware Horizon View Client\vmwHorizonClientController64.dll failed to register.  HRESULT -2147024703.  Contact your support personnel.

Error 1904. Module D:\Software\VMware\VMware Horizon View Client\vmwHorizonClientController64.dll failed to register.  HRESULT -2147024703.  Contact your support personnel.

Please help on how to get in installed.

VMware-Horizon-Client-4.9.0-9539668.exe

Windows7 HomePremium SP1

I had disabled Firewall and Avast AV and still the error occurs.

Regards,

16 Replies
mwyman
Enthusiast
Enthusiast

I think it's a problem on VMware's side with this. I cannot get it to install on anything.

Reply
0 Kudos
nzdude
Enthusiast
Enthusiast

I have the same problem on one Windows Server 2008 R2 (64-bit) machine.  Other machines running the same OS are fine.  Reinstalling 4.7.0 works.

This is the relevant part of the verbose installation log:

MSI (s) (8C:74) [11:23:19:586]: Executing op: RegSelfReg(File=vmwHorizonClientController.dll,FileID=vmwHorizonClientController.dll)

MSI (s) (8C:74) [11:23:20:592]: Executing op: RegSelfReg(File=vmwHorizonClientController64.dll,FileID=vmwHorizonClientController64.dll) CustomAction +vmwHorizonClientController64.dll returned actual error code -2147024703 (note this may not be 100% accurate if translation happened inside sandbox)

MSI (s) (8C:74) [11:23:20:738]: Note: 1: 2205 2:  3: Error

MSI (s) (8C:74) [11:23:20:738]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1904

MSI (s) (8C:74) [11:25:31:244]: Note: 1: 2205 2:  3: Error

MSI (s) (8C:74) [11:25:31:244]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709

MSI (s) (8C:74) [11:25:31:244]: Product: VMware Horizon Client -- Error 1904. Module C:\Program Files (x86)\VMware\VMware Horizon View Client\vmwHorizonClientController64.dll failed to register.  HRESULT -2147024703.  Contact your support personnel. CustomAction +vmwHorizonClientController64.dll returned actual error code -2147024703 (note this may not be 100% accurate if translation happened inside sandbox)

MSI (s) (8C:74) [11:25:33:076]: Note: 1: 2205 2:  3: Error

MSI (s) (8C:74) [11:25:33:076]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1602 Action ended 11:25:34: InstallFinalize. Return value 3.

MSI (s) (8C:74) [11:25:34:353]: User policy value 'DisableRollback' is 0

MSI (s) (8C:74) [11:25:34:353]: Machine policy value 'DisableRollback' is 0

Reply
0 Kudos
serinfbco
Enthusiast
Enthusiast

I was not able to install the horizon client 4.9.

Hcmon.inf installation failed (windows couldn't verify if it was signed).

I had to install Net Framework 4.6.1 and the cumulative update from Windows Update (like kb4343900 or kb4457144)

Reply
0 Kudos
BenFB
Virtuoso
Virtuoso

That's a prior known issue when other VMware productions are installed on the same machine since hcmon.inf is shared across multiple products. Do you have anything else installed from VMware?

Reply
0 Kudos
mwyman
Enthusiast
Enthusiast

Other then the previous build of the Client...no. It's supposed to be a rip and replace.

Reply
0 Kudos
serinfbco
Enthusiast
Enthusiast

Windows was installed with only Vmware Horizon View Client. No more software from Vmware.

Version 4.7.0 installed fine, but not 4.9

Reply
0 Kudos
mwyman
Enthusiast
Enthusiast

There is a fix for this. Horizon Client 4.9 has a requirement for Microsoft .Net 4.7. Install that and the installer will work as expected.

Reply
0 Kudos
nzdudeinsydney
Contributor
Contributor

Unfortunately that didn't work.  I installed 4.7.2, rebooted and tried again.

Capture.JPG

Reply
0 Kudos
trockenasche
Contributor
Contributor

I had the same issue.

But I found the reason by looking at the dependencies for the vmwHorizonClientController64.dll and noticing that the Microsoft Visual C++ 2017 Runtimes (x64) are missing.

Strange is that the Visual C++ 2017 packet is included in the setup file, but some how it doesn't get triggered.

nzdude
Enthusiast
Enthusiast

Thanks Trockenasche - after installation of VC++2017 (which supercedes and uninstalls 2015), I was able to successfully install Horizon Client 4.9.0.

VC++ 2017 available here:

https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

PuviarasuEswara
Contributor
Contributor

Guys,

Try installing this again by un-checking HTML5 Multimedia Redirection Support as shown below . It worked for me like Charm!!!...

pastedImage_1.png

sanders85012
Contributor
Contributor

The VC++2017 was the ticket to win for us.  We're Win 10, btw.

Reply
0 Kudos
NelsonCandela
Enthusiast
Enthusiast

Dear PuviarasuEswaramoorthi,

for both versions 4.10 and 5.0 the Client installation failed and aborted very close to the end, where I noticed it just mentioned something with HTML5 blabla.

After removing the checkbox for HTML5 Multimedia Redirection Support, as shown in your screenshot, the issue has been resolved - sort of ...

BR

NC

Reply
0 Kudos
Kishoreg5674
Enthusiast
Enthusiast

Horizon client installation is failing as it couldn't register the dll vmwHorizonClientController64.dll.

Confirm HKCR\CLSID\{8987B676-630A-4711-A9C7-025064F7B2C6} exists, and manually unregister the dll in cmdline:

Run cmd as admin, go to D:\Software\VMware\VMware Horizon View Client\, and run regsvr32 /u vmwHorizonClientController.dll, check whether installation succeeds(and confirm HKCR\CLSID\{8987B676-630A-4711-A9C7-025064F7B2C6} doesn't exist).

If you want to register it back, run regsvr32 vmwHorizonClientController.dll.

Reply
0 Kudos
MasonLivingston
Contributor
Contributor

ran into this with 5.5.0 on Windows 10 - ver 2004.  uninstalled the c++ 2015-2019 components, then reinstalled VMware horizon successfully.  -Cdecelles

Reply
0 Kudos
bbolokofsky
Contributor
Contributor

Thanks, Mason. This fixed it for me on Windows 10 1909 when none of the other solutions had worked.

Reply
0 Kudos