User related registry keys are not populating after launching the Advertised shortcut
i've an advertised shortcut and after launching the shortcut which is advertised i should get some entries under HKCU/Software/... but i'm not getting, when i repair the application i can see those registry keys coming under HKCU...
we should not impplement Active setup again when application has Advertised shortcut, as per best practises
please suggest me... thanks in advance
4 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
SnowLyric
11 years ago
Tukkudu,
Your advertised shortcut may not have been configured correctly. Try this - Create a new feature for your HKCU stuff and make it the parent of the feature containing the advertised shortcut.
Posted by:
piyushnasa
11 years ago
Self-Healing will check all key files of the components in the same feature level and any features/components BELOW in the same feature tree. The starting location of this check is the one which includes the exe the advertised shortcut is launching.
Repair will do a key files check on all components and features installed.
This difference is VERY important when working with Advertised shortcuts. You can even move components and features around to limit the self-heal to ONLY check/repair the components with per user data, which in some cases can significantly shorten the time it takes to self-heal.
Basically ensure the component you are trying to put down in a self-heal is in the same feature as the exe in which the advertise shortcut launches. - dandirk 11 years ago
but i've tried that even.... putting all in the same feature where advertised shortcut is present. but still it is not working.... - tukku 11 years ago
The only other thing I can think to check, is to make sure the key file/reg of the component that includes the user data is "missing" when the self-heal runs. This usually means the key should be per user data itself. - dandirk 11 years ago