Summary
This article discusses how Microsoft Windows Installer auto-repair functionality can be used to have per-user registry data (HKEY_CURRENT_USER) installed for any user that needs to use the installed application.Synopsis
This article discusses how Microsoft Windows Installer auto-repair functionality can be used to have per-user registry data (HKEY_CURRENT_USER) installed for any user that needs to use the installed application.
Discussion
To trigger Windows Installer auto repair, your MSI package needs to use one of the following advertised entry points that Windows Installer provides (see note below under Additional Information section):
- Advertised shortcut to the application executable
- File extension association
- COM CLSID registered using the Class table (using one of the COM extraction methods provided by InstallShield)
The advertised entry point acts as a trigger to have Windows Installer verify the components in the feature the entry point was associated with.
Each component contains a key path that Windows Installer uses to verify the component is correctly installed. Registry entries can be marked as the key path of a component. This allow as a component to contain per-user registry data that uses a registry entry as its key path.
When an advertised entry point is triggered, Windows Installer verifies the key paths of all components associated with the feature the entry point was associated with. When it attempts to verify the component containing the per-user registry data, it notices that the key path is invalid or not present and attempts to reinstall it. This may require access to the original source files and MSI package.
After choosing and adding an advertised entry point to your product, do the following:
- Create a component that contains the per-user registry data.
- Add any per-user registry data needed to this component.
- Right-click one of the registry values and select Set Key Path.
- Build the project.
- Install and test.
When logging on as a different user and triggering the advertised entry point, Windows Installer auto repair should be triggered and install the needed registry data. This process can occur for any user that did not originally install the application.
Related KB Articles
Q105805Additional Information
For more information on the Microsoft Windows Installer auto repair functionality, see the following Microsoft articles:
- Application Resiliency: Unlock the Hidden Features of Windows Installer
- Platform Support of Advertisement
Additional information can be found in Knowledge Base article Q105805, "PRB: Application Continues To Reinstall Itself When Launched".
Related Articles
Windows Update KB3072630 causes Registry permission changes to HKCU to fail 20Number of Views FlexNet Manager Suite application server upgrade may change non-default values in Compliance\CurrentVersion\*Directory reg… 6Number of Views Create an Install Condition Based on Registry Entry using Installshield 3Number of Views NT User Permissions for Installed Directories, Files, and Registry Keys 4Number of Views After new install/upgrade RL files are no longer importing or reports are returning zero data 58Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago