Storage Foundation for Windows High Availablity installation fails at 59% while on the VRTSvcs.msi package.
|Article:TECH185798|||||Created: 2012-04-04|||||Updated: 2012-04-04|||||Article URL http://www.symantec.com/docs/TECH185798|
Storage Foundation for Windows High Availablity (SFW HA) fails at 59% while installing VRTSvcs.msi.
VRTSvcs.msi.log shows the following error:
DIFXAPP: ERROR: Signature verification failed while checking integrity of driver package 'llt.inf' ('C:\Program Files\Veritas\comms\lltinf\llt.inf'). (Error code 0xE0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.)
DIFXAPP: ERROR encountered while installing driver package C:\Program Files\Veritas\comms\lltinf\llt.inf
DIFXAPP: InstallDriverPackages failed with error 0xE0000244
DIFXAPP: RETURN: InstallDriverPackages() 3758096964 (0xE0000244)
Action ended 21:20:52: InstallFinalize. Return value 3.
# for hex 0xe0000244 / decimal -536870332 :
# 1 matches found for "0xE0000244"
Storage Foundation for Windows High Availablity (SFW-HA)
This appears to be caused by a legacy policy for "Unsigned non-driver installation behavior" that is set in the registry. This looks to be a Windows 2000 that was deprecated by the "Enable Trusted Publisher Lockdown" policy in Windows 2003. In observed cases, the "Enable Trusted Publisher Lockdown" policy is not configured, but the legacy (Windows 2000) registry value is configured.
Symantec is currently investigating this issue for a permanent solution.
The following workaround has been reported to resolve the issue:
Note: The following steps describe editing the Windows registry. It is strongly recommended you make a backup of the registry before proceeding.
- Open the registry using regedit.
- Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Non-Driver Signing
- Set the Policy value to 0
- Install SFW HA
Article URL http://www.symantec.com/docs/TECH185798