Does anyone have a procedure for clearing the errors shown below?
I have successfully cleared them but it is mostly "hit & miss"

Component <File Name> has non-advertised shortcuts.
It should use a registry key under HKCU as its KeyPath, not a file. ICE43

Component <File Name> has both per-user and per-machine data with a per-machine KeyPath. ICE57
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


ICE43: If installed as per-machine then I don't think there is a way to resolve this.
ICE57: Separate the user-related files/registry entries to its own component.
Answered 09/16/2008 by: AngelD
Red Belt

Please log in to comment
ICE 43




Component “…” has non-advertised shortcuts. It Should use a registry key under HKCU as its KeyPath, not a file.

Put one Current_User registry key under the mentioned component and set that registry key as the keypath or Create a dummy regkey with a value of 1 for HKCU. Change the attributes in the component table to 4, add the new dummy key as the key path for this component. Add the component in the registry table as the component


Reg Entry “…” is not of type REG_SZ on Windows 95 Systems. Make sure the component is conditionalized to never be installed on Win95 machines.

In the Component where Reg Entry “…” resides set the condition to “NOT Version9x”.

ICE 57




Component 'ShortcutsComponent' has both per-user data and a keypath that can be either per-user or per-machine. http://dartools/iceman/ice57.html Component Component ShortcutsComponent'
“ShortcutsComponent” used as example

Create a new component holding the HKCU registry part, add that new component to an existing feature. Change the keypath for the Shortcutscomponent to another resource (noneuserprofile file or HKLM registry entry).
In the Registry table find the registry entry and change the component column to the name of the component you created.


Component has both per user and per machine data with a per machine keypath

Create a new component (with a new GUID), move all of the per user data from the component that kicks up the error to the new one. Set one of the files/reg keys as it’s keypath. If you use a registry key as the keypath for the new component you’ll need to set the attribute on that component to 4 to avoid new ICE errors.
Answered 09/17/2008 by: Tillu
Senior Yellow Belt

Please log in to comment
I created this document some time ago, of course with the help of many and posted it on juice.

Answered 10/21/2008 by: gizsha
Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity