Software Deployment

Hi Xink:

The registry that you are trying to create or modifying has key path assigned to it, that's why whenever you are trying to execute the product its initiating Self-Healing process since its not able to find the original registry key value. To over come this problem try to create a transform for the product by downloading the installshield Tuner for the product.

Thanks for the reply.
It only repairs for 1 time, that's good.
But what i mean is, at the info it says version is 7.0 instead of 7.0.3 because a repair has been triggered for the first time.
I need to know or the update is still applied or not?

Seems like your "disable update hkcu entries" triggers a repair, because the are the keypath of some component! Consult the eventviewer to find out which component causes the repair! If you would like to include custom hkcu settings in your package you have to create a top level feature(let's call it complete) and place the hkcu component into it, otherwise you'll get a feature level repair (in case of the Adobe Reader the ReaderProgramFiles) feature which will delete all updates applied later . If also tried to include some hkcu settings in our package but it just didn't work. Everytime another user launched the program adobe reader repaired itsself(just once, like in your case) then the settings were there but the updates were gone!

Solution: Utilize active setup to work around this problem!

Hi Xink:

The updates that u applied to this application do not go off by a triggered self-healing , self-healing is a just triggered to restore the modified registry that you tried to modify. I hope this would answer your question. one more thing self-healing will not revoke any particualr update or patch applied on a particular application.