cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

self-repair problem

I have created mst for vendor's msi (with InstallShield 11 - AdminStudio Edition). MST adds only one thing - a registry entry to HKCU\Software via new Feature. When you install msi+mst for the first time everything is Ok - registry key is successfully added to currently logged on user HKCU hive.
But when other users log on and launch the application, self-repair is not triggered and needed registry entry (which is set as Key Path in MST) doesn't appear under HKCU.
What could be the reason?

I've tried to make an advertized shortcut for the application and launch the app via that shortcut, but it did not help, self-repair was not triggered...
(3) Replies
A quick search found this thread.
The registry entry for HKCU is applied via MST which creates separate feature with needed registry entry. This entry is marked as Key Path and is in the Components table. The problem is that self-repair is not triggered when application is launched, Appplication Log does not contain any events re this... 😞
Move the component with the registry settings to the feature with the shortcut; that should work. Remember that one of the registry entries must be a key path.