I have a package that installs fine , but leaves registry keys behind after uninstall. Does anyone know of a solution to remove the registry keys using wise package studio 5.1?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Is the component(s) that these registry keys belong to set to 'Leave behind on Uninstall' ?
Answered 08/21/2007 by: michaelnowell
Second Degree Blue Belt

Please log in to comment
0
where would I be able to see if "leave behind on Uninstall" is checked?
Answered 08/21/2007 by: justinSingh
Blue Belt

Please log in to comment
0
Go to Setup Editor and select the Components Tab. Right click the component and select Details. There should be option in there to Leave installed on Uninstall.
Answered 08/21/2007 by: michaelnowell
Second Degree Blue Belt

Please log in to comment
0
If the registry keys isn't present in the MSI (Registry table or advertise related tables) then they will not be removed during an uninstall.
So if you've done a capture make sure that the application doesn't create any other registry entries when you launch it which are not part of the package, if so then add them too.
Answered 08/21/2007 by: AngelD
Red Belt

Please log in to comment
0
These are probably entries created by your application as it runs. As such, they may not appear in the MSI.

This is a good lesson for you: always run the app BEFORE you complete the capture. Many, many apps will add REAMS of stuff, either to the registry or to INI/XML/CFG/DAT files which may not be in the vendor's MSI or set up the installer if it's not MSI-based.

Either re-do the capture if that's possible/feasible and run the app before completing it or add a new component to remove the entries:

- Click 'Components' tab
- Right-click 'Components' and select 'New/Component'
- Type in a name for your component ('RegRemove', or whatever you want)
- Select 'Registry Key Path' in 'Key Path Type'
- Click 'OK'
- Right-click your new component and select 'New/Remove Registry'
WPS bizarrely now creates a list of registry folders, when it ough to do what it does after the next step.
- Right-click your new component and select 'New/Remove Registry'. Again.
- NOW you can select a hive and enter the key and values you want removed.

There's a quicker way to do this by directly using the RemoveRegistry table but I figure you'd appreciate a GUI-based answer for now.
Answered 08/22/2007 by: VBScab
Red Belt

Please log in to comment
0
I usually do not run the application as part of the capture process, it will often give you alot of HKCU entries that would not get removed if you install/uninstall the packages as another user, ex. using SMS in the System context or per-machine with AD/GPO. However, for troubleshooting that is a nice way of finding out more about the application.
You could create a second capture using the .WSI as a base when capturing into a transform instead. In this way it will be easier to find out what the capture added using ORCA as it will display any changes from the transform as green entries.

If you are using WPS Pro, then use "Test Expert" to provide you with files/registy entries left behind after uninstalling the package.
Answered 08/22/2007 by: AngelD
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity