Hello, new poster here... I hope I am in the right area. I have a vendor msi and my custom transform for some additional registry configs. Doing testing, I have found its leaving behind registry keys using the msi uninstall.

 

After some of your feed back ive updated the question info below

 

 I have imported a .reg file into an transform with installshield 2012 spring - its adds some default application settings here HKEY_CURRENT_USER\Software\DameWare Development\Mini Remote Control.

When I run an msiexec /x  to test uninstallation, Its leaving behind that same reg key path, with most of the keys removed - but several are still existing.

And excuse me if this is really easy, I am relatively new to this and cross-training in packaging.

How would I remove the root and all contents of that key , using best practice?

HKEY_CURRENT_USER\Software\DameWare Development\Mini Remote Control

thank you.

 

screenshot http://i46.photobucket.com/albums/f141/surfingcinv/example_zpsbe697eb0.jpg

http://s46.photobucket.com/user/surfingcinv/media/example_zpsbe697eb0.jpg.html

 

 

thank you,

 

Alex

2 Comments   [ + ] Show Comments

Comments

  • what registry? If you could assist us with the location of the same. Is your application very much similar to MSI's from IBM, Adobe, microsoft? if that is so, i dont see any harm if they are remaining behind
  • I have imported a .reg file into an transform with installshield 2012 spring - its adds some default application settings here HKEY_CURRENT_USER\Software\DameWare Development\Mini Remote Control.

    When I run an msiexec /x to test uninstallation, Its leaving behind that same reg key path, with most of the keys removed - but several are still existing.

    And excuse me if this is really easy, I am relatively new to this and cross-training in packaging.

    How would I remove the root and all contents of that key , using best practice?

    HKEY_CURRENT_USER\Software\DameWare Development\Mini Remote Control

    thank you.
Please log in to comment

Community Chosen Answer

3

Use the RemoveRegistry table. It's documented on MSDN, as well as in MSI.CHM which your authoring tool will have included in its installation.

Answered 07/08/2013 by: VBScab
Red Belt

  • The MSDN documentation is difficult to understand without examples. I found a basic example and here is what I have so far. How do I know which component to link this to? IN the screenshot - I basically want to delete everything under the root of "dameware development" thank you
Please log in to comment

Answers

0

I always suggest that you leave the "leftovers" on the machine and don't bother with them.  They exist because the app added/modified the keys during normal use and the MSI (by default, without leveraging the RemoveRegistry table) will only remove exactly what it put down.

They're associated with the app which you just uninstalled, so they won't be conflicting with any other app.  Even if it takes you five minutes to modify the package to remove every trace of itself, there's no "gain" or improvement.  The time & frustration you save by not removing them makes your world a little easier  :)

Answered 08/09/2013 by: vjaneczko
Seventh Degree Black Belt

Please log in to comment
0

Edit Transforms and u can use default key in registry (*) which will remove registry key on uninstall.

if it doesnt work then u can remove it use vbscript to remove (should not remove vendor specific registries which are comman for other packages as well like mentioned in above posts)

Answered 07/08/2013 by: appfreak
Senior Purple Belt

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