Both can be used to insure that registry settings for the current user are populated.  What do you do in the case where you deploy the application with the user already logged in.  That rules out Active Setup which leaves an Advertised Shortcut.  If the application will most likely be invoked by opening a file associated with the app, that goes around the AS.  How do you deal with this if you need to insure that the proper registry settings are deployed before the application gets lauched?

0 Comments   [ - ] Hide Comments


Please log in to comment

Community Chosen Answer



You can make advertised file associations... If that isn't good enough, make a script CA that sets the settings for every user profile, and the default profile on the system during installation.

Answered 04/30/2013 by: Ifan
Second Degree Green Belt

  • It looks like in order to make advertised file associations I will need to use the Extension and ProgID tables. When doing a validate on the MSI I receive a few warnings that some registry entries are used in an unsupported way and should be in the ProgID table. Is there a simple way to move those reg entries to the ProgID table or am I mixed up here?
  • I was able to use IS to extract the com info and import the populated ProgID and Class tables into my transform. After install if I launch a file associated with this app it is still not initiating self repair unless I launch it using the Start Menu shortcut. I'm wondering if I have something wrong with my Extension table or am I missing something else?
  • This content is currently hidden from public view.
    Reason: Removed by member request
    For more information, visit our FAQ's.
Please log in to comment
Answer this question or Comment on this question for clarity



Just create a advertised package and the selfhealing will be called even if you open the application using an associated file.

Answered 05/16/2013 by: terebent
Second Degree Brown Belt

  • This is a vendor package so it is already created.
    • You can advertise it even is a vendor msi.
  • That is what I'm trying to do but I have been unable to get it to work and I'm not sure what the problem is. I've populated the Class, Extension, MIME, and ProgId tables. The only thing I'm not sure of is my features and components in the different tables. My advertised shortcut is working properly so I know I have my top level feature and feature parent set correctly.
Please log in to comment

Is the feature  to which user registry and extension  associated same ?

Answered 05/03/2013 by: Hussi
Purple Belt

  • Should the component and feature be the same for the extension as the user registry? If I do that I receive a "cannot be advertised because the KeyPath disallows it." error when validating.
  • component needs to be diffrent feature needs to be same
  • So I create a new component for the entry in the Extension table. What is the KeyPath supposed to be?
  • The keypath can be exe or dll which the extension points to
    ...When any advertised entry point is triggered (here File association) it will check for all broken components in that feature so if the HKCU registry are set as keypath for different component in same feature it will trigger self heal.
Please log in to comment