Horizon Client ‘Install Failed’

KB ID 0001594


When attempting to install the VMware Horizon client you see;

Horizon Client Install Failed

Well that’s very descriptive and helpful?


Firstly make sure you  are NOT trying to install the client software on a Horizon Connection Server, or a Horizon Security Server! If you are not, then the easiest way to get it to install, is to ‘extract’ the .msi installation files, and manually run them. 

In PowerShell navigate to the folder that you download the client .exe file to, and extract its contents with the following command;

.\VMware-Horizon-Client-{version-and-build-number}.exe /x

Horizon Client Install Extract MSI

It looks like nothing has happened, but the files get put in the ‘Temp‘ folder in YOUR user profile, Navigate to C:\Users\{Your-Username}\AppData\Local\Temp

In this location you will find a folder containing the individual install files you require.

Horizon Client InstallInstall from msi

From here you can launch the one you want, In my case (VMware Horizon View Client (x64).msi).

Related Articles, References, Credits, or External Links


Author: PeteLong

Share This Post On


  1. GUI installer gets to the very end then fails.

    Tried unpacking as recommended and running the single MSI.
    Tried the default installation. Installation proceeds, then it says “rolling back installation no changes made” and fails

    Tried selecting options.

    Tried the default installation. Installation proceeds, then it says “rolling back installation no changes made” and fails

    I noticed it said FIPS142 encryption not available on this machine, not sure why

    Post a Reply
  2. Hi All,

    I have the same exact experience as Robert.

    PS C:\Users\Strahinov\Downloads> [System.Environment]::OSVersion.Version

    Major Minor Build Revision
    —– —– —– ——–
    10 0 18363 0

    Please advise,

    Yordan Strahinov

    Post a Reply
  3. Hello @ll,

    I tried EVERY tipp, from here to eternity, and still get this f…..g yellow triangle on my hostcomputer, WIN 10 1909.

    On my laptop with WIN 10 1903 the installation was absolutely no problem and the client runs fine.
    (I can´t go back to 1903 on my host ´coz the update ran more than 10 days ago.)

    Now, before setting up WIN 10 new, what I want to avoid actually, maybe someone has the final, golden idea to solve this issue.


    Have anice day and stay healthy

    Post a Reply
  4. Got the same issue was previous comments. Running Win 10 Pro Version 10.0.18363.778.

    Starting “VMware Horizon View Client (x64).msi” goes through the motion and then say “VMware Horizon Clietn Setup Ziward ended prematurely”. A log is being created in the temp directory, with a filename VMware_Horizon_Client_YYYYMMDDHHMMSS.log but the only information it provides about the failure is:

    [1E94:2E00][2020-04-16T13:31:52]e000: Error 0x80070643: Failed to install MSI package.

    No explanation as of why…

    Post a Reply
  5. Failed for me. [Version 10.0.18362.778]
    Tried x64, x86
    The installer window indicates the setup Wizard ended prematurely.

    So frustrating

    Post a Reply
  6. This one was weird. I’ve heard some people contend that disabling their host file write protections allowed the installer to finish its task. For me, what seemed to work was running in compatibility mode.

    Post a Reply
  7. We use Webroot antivirus. The last step in the install is modifying the local hosts file. Webroot blocked this. So the install failed and it would roll back changes. I had to allow the application to run and modify what it needed.

    Check antivirus. Make sure that it is not blocking changes to c:\windows\system32\drivers\etc\hosts.

    Post a Reply
    • Disabling Webroot AV, installing Horizon Client, then re-enabling Webroot was the ticket! Thank you, Geoff!

      Post a Reply
  8. I can’t extract the contents of the exe-file; the parameter /x is not accepted (‘unexpected token “x”):
    “(…)\VMWare\Horizon-Client\VMware-Horizon-Client-5.4.3-16346110-2.exe” /x

    Unerwartetes Token “x” in Ausdruck oder Anweisung.
    + CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : ExpectedValueExpression

    But when running the exe itself as administrator I seem to have the same problems as some mentioned above when using the msi (rollback after some time).

    I am using Windows 10 x64 pro v2004.



    Post a Reply
  9. Parameter does not work with PowerShell under Win 10 x64 v2004 (PS 6) but in the old commandline.

    Post a Reply
  10. I used the tip to disable Webroot (security software), and installation went from stopping with “Failed” to completed and installed. Thank you!

    Post a Reply
  11. Same for Symantec Endpoint Protection. Disabled, and boom install succeeded!

    Post a Reply
  12. Solution:
    Go to c:\windows\system32\drivers\etc\hosts
    temporary change the security privileges for applications packages to full control and voila.

    Post a Reply
  13. Solution for using Webroot:

    Go to Advanced -> Protection.
    Un-check the option “Prevent application’s changing HOST file”.

    Simply disabling webroot didn’t work for me.

    Post a Reply
    • THank you for this solution. I have been trying all day to figure this out. Uncheckin the option finally gave me a success.

      Post a Reply

Submit a Comment

Your email address will not be published. Required fields are marked *