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
- :
- Uninstalling Patch does not restore original files
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 17, 2008
03:02 PM
Uninstalling Patch does not restore original files
Hi, I'm rather new to InstallShield. I have a Basic MSI project. Part of this project builds patches for a prior version of the same product.
After installing the .msp patch, I verify that all files have been updated correctly, however when I uninstall the patch (using MSI 3.0 and the Add/Remove programs option to remove patches) I find all files updated by the patch are deleted, and the original (unpatched) files are not restored.
I have been playing around with various settings in InstallShield but I have been unable to keep this from happening.
Note: All files are being dynamically added to the project at build time. The Project itself has no references to the files themselves until the build is run.
I am using default patch sequencing.
This is a minor upgrade (Same Product code, Update Code between versions)
Can someone clue me in on what I am doing wrong?
After installing the .msp patch, I verify that all files have been updated correctly, however when I uninstall the patch (using MSI 3.0 and the Add/Remove programs option to remove patches) I find all files updated by the patch are deleted, and the original (unpatched) files are not restored.
I have been playing around with various settings in InstallShield but I have been unable to keep this from happening.
Note: All files are being dynamically added to the project at build time. The Project itself has no references to the files themselves until the build is run.
I am using default patch sequencing.
This is a minor upgrade (Same Product code, Update Code between versions)
Can someone clue me in on what I am doing wrong?
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 13, 2008
11:05 AM
Did you get this resolved? I am getting the same issue.
Help anyone??
Help anyone??
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 13, 2008
11:14 AM
I did get it resolved. I was using dynamic file links in my projects. Unfortunately dynamic file linking and generating patches do not seem to work together.
When creating the patch, the Dynamic File links generate a new Component ID that does not match the original, which breaks the patch and uninstall process.
When creating the patch, the Dynamic File links generate a new Component ID that does not match the original, which breaks the patch and uninstall process.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 13, 2008
11:19 AM
One thing to try: in the last panel of the Release Wizard, there's a "previous package" setting you can use, the intention of which is to keep the File, Component, and Media keys matched up between builds. As you've seen, this is especially useful when using dynamic file links.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 13, 2008
11:41 AM
Thanks for the fast reply... looks like I'll have to create small updates instead. At least for my next release.
![](/skins/images/04FED02024358F0FDF89E0836F432D6F/responsive_peak/images/icon_anonymous_message.png)