/build/static/layout/Breadcrumb_cap_w.png

Application is Hidden from Add/Remove Programs

I packaged and application that uses an MST file and after the installation is completed, the application does not show up in Add/Remove Programs. I looked for the ARPSYSTEMCOMPONENT or ARNOREMOVE properties but could not find it. Does anyone know what I should be looking for?

Thanks

0 Comments   [ + ] Show comments

Answers (9)

Posted by: reds4eva 15 years ago
Second Degree Blue Belt
0
ARPSYSTEMCOMPONENT is the property that hides the app from Add/Remove programs.
You could also populate HKLM\software\microsoft\windows\currentversion\uninstall\[productcode]
Posted by: anonymous_9363 15 years ago
Red Belt
0
IIRC, it is the use of ARPSYSTEMCOMPONENT which triggers the WI engine to not write the 'Uninstall\[ProductCode]' registry key.

Anyway, to the actual problem...my guess would be that the package itself is removing that key, either via a Custom Action or via the RemoveRegistry table.
Posted by: AngelD 15 years ago
Red Belt
0
ORIGINAL: VBScab

IIRC, it is the use of ARPSYSTEMCOMPONENT which triggers the WI engine to not write the 'Uninstall\[ProdictCode]' registry key.

Almost, if the property is defined WI will write the SystemComponent (DWORD) reg entry with a value of 1 to hide the ARP entry and not prevent the Uninstall\<{ProductCode}> reg key.

Could the package be a InstallShield based one?
Search under the Uninstall key for the product name (ProductName property value)
Posted by: InterneToughGuy 15 years ago
Senior Purple Belt
0
This package is an Installshied package. Should I convert it to a Wise package?
Posted by: anonymous_9363 15 years ago
Red Belt
0
This package is an Installshied package. Should I convert it to a Wise package? Why would you want to do that? What difference would it make? As I mentioned, the package is likely to be removing the uninstall registry key via a Custom Action, or it could be dynamically setting the ARPSYSTEMCOMPONENT property. As it's an MSI you should be able to run it through the Wise debugger and set up ProcMon to watch the HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\[ProductCode] tree (substituting your package's Product Code, obviously) with ProcMon, and/or watch the ARPSYSTEMCOMPONENT. Step through each action and wait for the uninstall key to be changed/removed. The offending action will be th eone previous to the currently-highlighted action.

Alternatively, set ARPSYSTEMCOMPONENT in your transform and then log th einstall. The log will show where the property was changed.
Posted by: varun.appdeploy 15 years ago
Yellow Belt
0
i got an exe which is extract msi in temp, msi(msi is created in Advanced Installer) will not show any entry in ARP during uninstallation one window will come saying that "action is valid only for products that are currently installed"
ARPSYSTEMCOMPONENT property is not there in msi
i tried creating mst and added ARPSYSTEMCOMPONENT=0 , but still it is not showing in ARP
some custom actions are there in msi like :
set property AI_ExractLzma to [AI_SETUPEXEPATH]
set property AI_ExractRLzma to [AI_SETUPEXEPATH]
6 more custom actions are there which are setting property that starts with AI_

Please help me out
thanks in advance.......
Posted by: jmcfadyen 15 years ago
5th Degree Black Belt
0
sounds like your initial install was done as PER USER and your trying to uninstall with another account.
Posted by: varun.appdeploy 15 years ago
Yellow Belt
0
No my initial install is per machine and i am uninstalling in the same account ...

but still this problem persists ..
Posted by: AngelD 15 years ago
Red Belt
0
varun,

Is the RegisterProduct action present and executed during install?
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ