Summary

Symptoms

ICE38 occurs only during validation and is displayed in the following formats:

• Component <COMP> installs to user profile. It must use a registry key under HKCU as its key path, not a file.

• Component <COMP> installs to a user profile. It must use a registry key under HKCU as its key path. The KeyPath is currently NULL.

• Component <COMP> installs to user profile. Its key path registry key must fall under HKCU.

• The KeyPath registry entry for component <COMP> does not exist.

• The Registry Entry <REG> is set as the KeyPath for component <COMP>, but that registry entry doesn't belong to <COMP>.

<COMP> is the name of the component causing the validation error. <REG> is the primary key of the row in the Registry table causing the validation error.

Cause

A component's destination is set to a per-user folder, such as AppDataFolder, and one of its files is set as the key file.

A component's destination is set to a per-user folder, such as AppDataFolder, but no key path is set for the component in the files or registry section.

A component's destination is set to a per-user folder, such as AppDataFolder, and the path registry key is set, but the key is located under a hive other than HKEY_CURRENT_USER.

A component has a key path registry entry key, but this key path is not listed in the Registry table. This scenario does not occur under normal circumstances. It only occurs if the Registry or Component table has been manually edited via the Direct Editor. Following is an example of table entries that would cause this validation error.

This is an entry in the Component table:

This is an entry in the Registry table. Notice that there is only one entry, and the Registry column says Reg5. However, in the Component table entry above, Component1 is looking for entry Reg4 in the Registry table:

A component has a key path registry entry key, but the key is associated with another component. This scenario does not occur under normal circumstances. It only occurs if the Registry or Component table has been manually edited via the Direct Editor. Following is an example of table entries that would cause this validation error.

This is an entry in the Component table:

This is an entry in the Registry table. Notice that there is only one entry, and the Component column says Component2. However, in the Component table entry above the Component column says Component1. However, both the KeyPath column above and the Registry column below have Reg4 listed:

Resolution

1. Find the component mentioned in the error via the Components or Setup Design view.
2. Expand the component and click Files.
3. Right-click the key file and choose Clear Key File. The key file will have a key icon displayed to its left.
4. Click Registry Data.
5. Right-click the HKEY_CURRENT_USER hive under the Destination computer's Registry view and choose New > Key.
6. Right-click the new key and choose New > Default Value.
7. Right-click the new default value under Destination computer's registry data and choose Set Key Path.
8. Rebuild the release and revalidate the MSI from the Build Menu option.

1. Find the component mentioned in the error via the Components or Setup Design view of the IDE.
2. Expand the component and click Registry Data.
3. Right-click the HKEY_CURRENT_USER hive under the Destination computer's Registry view and choose New > Key.
4. Right-click the new key and choose New > Default Value.
5. Right-click the default value under the Destination computer's registry data and choose Set Key Path.
6. Rebuild the release and revalidate the MSI from the Build Menu option.

1. Find the component mentioned in the error via the Components or Setup Design view of the IDE.
2. Expand the component and click Registry Data.
3. Right-click the key that is set as the key path and choose Clear Key Path. The current key path will be listed under a hive other than HKEY_CURRENT_USER. The key will have a key icon displayed to its left.
4. Right-click the HKEY_CURRENT_USER hive under the Destination computer's Registry view and choose New > Key.
5. Right-click the new key and choose New > Default Value.
6. Right-click the new default value under Destination computer's registry data and choose Set Key Path.
7. Rebuild the release and revalidate the MSI from the Build Menu option.

1. Find the component mentioned in the error via the Components or Setup Design view of the IDE.
2. Expand the component and click Registry Data.
3. Right-click the HKEY_CURRENT_USER hive under the Destination computer's Registry view and choose New > Key.
4. Right-click the new key and choose New > Default Value.
5. Right-click the new default value under Destination computer's registry data and choose Set Key Path.
6. Rebuild the release and revalidate the MSI from the Build Menu option.

1. Find the component mentioned in the error via the Components or Setup Design view of the IDE.
2. Expand the component and click Registry Data.
3. Right-click the HKEY_CURRENT_USER hive under the Destination computer's registry view and choose New > Key.
4. Right-click the new key and choose New > Default value. By recreating the key and value, the key will be associated with the correct component.
5. Right-click the new default value under Destination computer's registry data and choose Set Key Path.
6. Rebuild the release and revalidate the MSI from the Build Menu option.

Additional Information

The Registry table is documented in the Windows Installer Help Library topic Registry Table.

The Component table is documented in the Windows Installer Help Library topic Component Table.

Related KB Articles