![]() ![]() Thanks for reading and hopefully this helps someone else out. Verify Composer service is still running. Once Guest OS successfully rebooted check the composer service is running. Power Down the Virtual Machine that has the guest OS of Windows Server 2016 you’re trying to install composer on.Tested Virtual Machine Version 13 and 14.I then created a desktop pool and was able to use linked clones successfully! After rebooting, I turned Secure Boot back on and the composer service was still running. After a successful install, I looked at the “vstor2-ufa.sys” and dug into the digital signature which was signed by “VMware Inc” and was issued by “verisign” which is already trusted. After disabling Secure Boot, I was able to successfully install Composer 7.5. Right away I either knew it was one of two things: Secure boot or VBS (Virtual Based Security). The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error.įile Name:\Device\HarddiskVolume4\Program Files (x86)\Common Files\VMware\VMware Universal File Access\vstor2-ufa.sys" Logon Monitoring Unity Touch ClonePrep Rearm Dynamic PCoIP Policies Microsoft FSLogix Why FSLogix FSLogix Installation VMware OS Optimization Tool Additional Optimizations Snapshot Recently Updated Change Log 2023 July 7 Horizon Agent updated for Horizon 2306 (8. “Code integrity determined that the image hash of a file is not valid. I noticed a weird audit failure in security log which was Event ID “5038” and had the following description: So I decided to check the event viewer one more time. ![]() Looking through the logs, I found no errors for ODBC or SSLbind settings. I started verifying the SSLbind and ODBC Connection. So after finding this entry, I started looking at VMware Doc’s and KB articles. “CustomAction InstallVstor2Driver.5ACA97E0_7C64_4970_A763_840E81DAAF0B returned actual error code 1603 ” After doing some digging, I found this in the log: So I started digging into the event viewer and vmmsi.log which is located at (c:\users%username%\Appdata\Local\Temp) I started to notice 1603 setup exit code errors. I would run into the composer installer failing and attempting “Roll Back Action”. When I went to install Composer 7.5 (This also happened with 7.4) on a composer standalone configuration. Recently I have been testing moving Horizon View to Server 2016 since we will be migrating soon from 2012R2 to 2016 in production sometime this year. However, none of the listed conditions are true.So why is VMware Horizon View Composer Failing to Install ? You notice the error message because the Windows Installer service uses the SYSTEM account to install software. The SYSTEM account does not have Full Control permissions on the folder that you are trying to install the Windows Installer package to.The drive that contains the folder that you are trying to install the Windows Installer package to is accessed as a substitute drive.The folder that you are trying to install the Windows Installer package to is encrypted.Windows Installer is attempting to install an app that is already installed on your PC.You may receive this error message if any one of the following conditions is true: I've dug through the user groups and none of the posted solutions fix my problem. I have suspended my antivirus and firewall, I have run as an administrator with minimum installation options selected. The install runs all the way to 100% then reports "Failed." Digging through the logs showed the 1603 error. Check the logs for more details." when attempting to install VMWare Client. All boxes continue to exhibit the same "Installation of component VCSServiceManager failed with error code '1603'. I'm attempting to install VMware Horizon Client for Windows 2203 on both a Windows 11 box and two Windows 10 boxes. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |