disabling the setting while the install runs FIXED the issue. VdmInstUtil: 03/10/20 22:05:11 Exiting custom action VMAddViewLocalHostEntryToHostsFileĬustomAction VM_AddViewLocalHostEntryToHostsFile returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)Īfter investigating further I found that our AV software (Webroot) was blocking applications from editing the HOSTS file. VdmInstUtil: 03/10/20 22:05:11 ERROR: Failed writing to file "C:\WINDOWS\system32\Drivers\etc\hosts". VdmInstUtil: 03/10/20 22:05:11 Appending text to file: "C:\WINDOWS\system32\Drivers\etc\hosts" VdmInstUtil: 03/10/20 22:05:11 Searching for '127.0.0.1 view-localhost # view localhost server' in "C:\WINDOWS\system32\Drivers\etc\hosts" VdmInstUtil: 03/10/20 22:05:11 - VMAddViewLocalHostEntryToHostsFile() : Adding view-localhost entry to the 'etc\hosts' file. VdmInstUtil: 03/10/20 22:05:11 Entering custom action VMAddViewLocalHostEntryToHostsFile The entries below were in the install log file. In my case the issue was because the client installer (Ver 5.3) needed to add an entry to the HOSTS file and did not have permissions to do so. I noticed these same error messages in previous VMWare install logs, but they mean nothing to me. MSI (c) (D8:20) : MainEngineThread is returning 1603 MSI (c) (D8:20) : Cleaning up uninstalled install packages, if any exist MSI (c) (D8:20) : Grabbed execution mutex. Installation success or error status: 1603. MSI (c) (D8:20) : Windows Installer installed the product. MSI (c) (D8:20) : Product: VMware Horizon Client - Installation failed. I used Verbose logging for the MSI install and at the very end of the log file is this:
0 kommentar(er)
