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
- :
- Uninstall fails if I no longer have access to the MSI file
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
‎Aug 18, 2017
09:44 AM
Uninstall fails if I no longer have access to the MSI file
Users are copying the release folder to their desktop to install our application then removing the folder after it completes. When they go to uninstall, the process can no longer find the .MSI file. So I tried to update the install to cache the MSI locally but it is disabled. The Note reads "This setting is enabled for releases that do not have the .msi file available in the same folder as the Setup.exe file on the target system". Why? I need to enable this and so far have found nothing in the Forum to help. Thanks in advance.
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 18, 2017
12:41 PM
switch to a single compressed *.exe and you should be able to use that setting.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 21, 2017
12:13 AM
I would add as well, thinking about it: It's unusual that your setup requires the *.msi for uninstallation.
It may be that you can fix this problem itself. Check the uninstall log for "ResolveSource" to see what is triggering it. You shouldn't need this action firing off unless there's a good reason. The default for new projects is to have a condition on the action in the sequence to prevent this very thing.
It may be that you can fix this problem itself. Check the uninstall log for "ResolveSource" to see what is triggering it. You shouldn't need this action firing off unless there's a good reason. The default for new projects is to have a condition on the action in the sequence to prevent this very thing.
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)