VMware Horizon Community
arnoldveenema
Contributor
Contributor

Horizon View Composer Installation Failed (1603)

Hi,

We are struggling with an upgrade of Horizon View Composer with any version higher than 7.0.3.

E.g. the upgrade or fresh install of VMware Horizon Composer 7.3.2-71161120 fails on Windows 2016.

Error logs shows:

VIEINSTUTIL: InstallDriver: params = vstor2-ufa, Vstor2 UFA Virtual Storage Driver, C:\Program Files (x86)\Common Files\VMware\VMware Universal File Access\vstor2-ufa.sys, 2, 1, (no load order), 1

VIEINSTUTIL: Opened Service Control Manager

VIEINSTUTIL: Created service vstor2-ufa for C:\Program Files (x86)\Common Files\VMware\VMware Universal File Access\vstor2-ufa.sys

VIEINSTUTIL: Failed to start service (0x241)

VIEINSTUTIL: Finish install

CustomAction InstallVstor2Driver.5ACA97E0_7C64_4970_A763_840E81DAAF0B returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Action ended 14:13:17: InstallFinalize. Return value 3.

After a bit of digging I found that Windows will not start the service because it does not trust the driver vstor2-ufa.sys

Eventlog shows

Log Name:      Security

Source:        Microsoft-Windows-Security-Auditing

Date:          11/30/2017 2:13:17 PM

Event ID:      5038

Task Category: System Integrity

Level:         Information

Keywords:      Audit Failure

User:          N/A

Computer:      computername.domain.local

Description:

Code integrity determined that the image hash of a file is not valid.  The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error.

File Name: \Device\HarddiskVolume3\Program Files (x86)\Common Files\VMware\VMware Universal File Access\vstor2-ufa.sys

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />

    <EventID>5038</EventID>

    <Version>0</Version>

    <Level>0</Level>

    <Task>12290</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8010000000000000</Keywords>

    <TimeCreated SystemTime="2017-11-30T13:13:17.388333900Z" />

    <EventRecordID>23131752</EventRecordID>

    <Correlation />

    <Execution ProcessID="4" ThreadID="172" />

    <Channel>Security</Channel>

    <Computer>computername.domain.local</Computer>

    <Security />

  </System>

  <EventData>

    <Data Name="param1">\Device\HarddiskVolume3\Program Files (x86)\Common Files\VMware\VMware Universal File Access\vstor2-ufa.sys</Data>

  </EventData>

</Event>

Any idea how to solve this? Is it possible to correct this or manually add a trusted source of something?

Kind regards,

Arnold Veenema

Tags (2)
Reply
0 Kudos
3 Replies
mhampto
VMware Employee
VMware Employee

Check If you have SSLbind information left over from previous instance. If so, remove these from the registry and try installing.

Reply
0 Kudos
davonnedeschain
Contributor
Contributor

I'm having the same issue with 7.5 Error 1603 on Windows Server 2016 Standard

It verified my ODBC connection, but the Installation starts, and than says rolling back.

Steps I have tried

I have tried running as Local Admin

Installing as Admin with no success.

I am going to try running msiexec silently and see if that works.

Will let you know.

Any ideas?

Reply
0 Kudos
sumann7
Contributor
Contributor

Hi Arnoldveenema,

This can be fixed by disabling the secure boot from BIOS.

OR you may try the below steps

  1. lick Start > Run, type regedit, and click OK. The Registry Editor window opens.
  2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.
  3. Delete the stcp2v30 key.
  4. Delete the vstor2-p2v30 key.
  5. Delete all vmware-ufad-p2v-XXXXX keys.
  6. Delete all courier-XXXXX keys.
  7. Reboot.
  8. Under the %SystemRoot%\system32 folder, remove all vmware-ufad-p2v-XXXXX subdirectories.

Note: If you do a search on windows registry, you may still find vmware-ufad keys in HKEY_LOCAL_MACHINE\SYSTEM\ControlSet00x. You can ignore this because, after the next reboot, the registry hive in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet is saved as ControlSetx.