This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Deleting value from HKCU registry hive in a minor upgrade
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 16, 2008
02:07 PM
Deleting value from HKCU registry hive in a minor upgrade
Is it possible to safely remove a registry key from HKCU\Software\DeLorme\ in a patch or minor upgrade?
Basically the update that I am being asked to make needs to remove user settings created by the application. I know I can author items in the removeregistry table but can I do it in such a way that the user is not prompted to insert the original install media?
Thanks.
Basically the update that I am being asked to make needs to remove user settings created by the application. I know I can author items in the removeregistry table but can I do it in such a way that the user is not prompted to insert the original install media?
Thanks.
(6) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 17, 2008
08:06 AM
** BUMP ** Anyone out there 🙂
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 17, 2008
10:41 AM
If you perform a minor upgrade using the 'v' parameter and author the RemoveRegistry table properly, this seems to work in a quick test I performed.
Also, forgot to mention, if the registry entry is the keypath, you probably don't want to do this as it would be a component rule violation. Can't change the keypath of a component during a minor/small update.
Also, forgot to mention, if the registry entry is the keypath, you probably don't want to do this as it would be a component rule violation. Can't change the keypath of a component during a minor/small update.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 17, 2008
11:27 AM
by command line I am assuming that you mean the Patch Design Advanced Argument for REINSTALLMODE=vomus REINSTALL=ALL. Is this correct?
Thanks.
Thanks.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 18, 2008
07:53 AM
While I got this working for the current user, I could not get this to work in a multiuser environment. Hmm, as I type this perhaps I need to set something in the component as a key file in HKCU? Just a thought for me to try.
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 22, 2008
10:21 AM
To clarify, I meant in a full minor upgrade.
I would suggest investigating a full minor upgrade scenario before moving on to the patch. Does it work in that case?
I would suggest investigating a full minor upgrade scenario before moving on to the patch. Does it work in that case?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 22, 2008
10:57 AM
If the HKCU entry is not a component key, then try using Active Setup. Write a custom script (vbscript/batch file etc) and make its entry in the Run key. Though its require a log-off/reboot, its effective.