I have common ISM template. I have created 3 MSI using same ISM template but with different ProductName and ProductVersion and ComponentName. The component files are dynamic. The registry key path contains the ComponentName in the path (which is obviously different for all MSI) but get created under same <CompanyName>. The registry key can be considered as shared under <CompanyName>.
All 3 MSI installation went fine with proper file and registry entries. but when I uninstall any of the MSI, the registry key associated with it is not getting removed. The registry key is getting removed only for the last uninstalled MSI, for first 2 uninstalled MSI it is not getting deleted.
E.g.
MSI1: HKEY_LOCAL_MACHINE\SOFTWARE\<CompanyName>\ABC\Component1
MSI2: HKEY_LOCAL_MACHINE\SOFTWARE\<CompanyName>\ABC\Component2
MSI3: HKEY_LOCAL_MACHINE\SOFTWARE\<CompanyName>\ABC\Component3
MSI1 uninstall, registry key Component1 not removed.
MSI2 uninstall, registry key Component2 not removed.
MSI3 uninstall, registry key Component3 removed..
Irrespective of order, the registry key is removed only for last uninstall. Changing registry install behavior "install if absent, uninstall if present" not helped.
Is there any way, or only CustomAction is the solution?
All 3 MSI installation went fine with proper file and registry entries. but when I uninstall any of the MSI, the registry key associated with it is not getting removed. The registry key is getting removed only for the last uninstalled MSI, for first 2 uninstalled MSI it is not getting deleted.
E.g.
MSI1: HKEY_LOCAL_MACHINE\SOFTWARE\<CompanyName>\ABC\Component1
MSI2: HKEY_LOCAL_MACHINE\SOFTWARE\<CompanyName>\ABC\Component2
MSI3: HKEY_LOCAL_MACHINE\SOFTWARE\<CompanyName>\ABC\Component3
MSI1 uninstall, registry key Component1 not removed.
MSI2 uninstall, registry key Component2 not removed.
MSI3 uninstall, registry key Component3 removed..
Irrespective of order, the registry key is removed only for last uninstall. Changing registry install behavior "install if absent, uninstall if present" not helped.
Is there any way, or only CustomAction is the solution?