Written by Ronald Vonk  

Description:
This will post an error if a component installed under the user's profile does not specify a HKCU registry key.

Additional Information:

ICE38 occurs during validation when a current user file in a component does not have a current user key as keypath. This could result in repairing undefinely since files are traced on the first location of installation, which is usually an admin account. After repair, the file cannot be found as the user is not given rights for this location, even he has put it on the correct spot. The result is: repair continues to restart.  

If there is a component with files included in the user profile and at the same time, there is no current user registry key, the way to solve this error is as follows:

Create a registry key in the current user registry under the (first) component where the error occurs. Create this key as follows:

HKCUSoftwareKeyfix=1.

next, create from this key the keypath of the specific component.

If multiple components need to be repaired with ICE38, go to the registry table and copy the recently created key for the number of components sharing the same error. Adjust the registry key by placing numbers:

HKCUSoftwareKeyfix=1
HKCUSoftwareKeyfix1=1
HKCUSoftwareKeyfix2=1

Next, select for each row each component sharing the same error in the component column of the registry table. 

remarks:

In practice, sometimes it happens that validation thinks that there are current user files located in een component while this is not the case. For instance, files which always end up in the ALL USER profile and sometimes also with shortcuts. In order to resolve this you may be able to transfer the contents of the component to another component which does have current user key als keypath. Pat attention that folders are linked to components, not to files. Transferring files is only allowed if the other component is referring to the same folder.