Reply to Thread

Re: Uninstall Reboot Message

Yes, that confirms what I was thinking. We do check all of the EXE's (programs) to see if they are in use, but it sounds like we need to be checking all the files that are going to be removed in the uninstallation process.

Re: Uninstall Reboot Message

Mark,

if the system needs a reboot after an uninstall means that one or more files were locked (in-use) during the uninstallation process. The only way to handle your specific scenario is to check in your (custom) uninstall if all files can be removed. You could handle this in a custom uninstall script by using "Check In-Use Folder Tree..." and "Check In-Use File...". And it's always a good idea to see if your main application is not active - you can check this with "Detect Active Application...".

To sum it up: only continue with the uninstall if the main app is not active (not running) and the files can be removed.

Does this help?

Friedrich

Re: Uninstall Reboot Message

Any additional thoughts on this?

Re: Uninstall Reboot Message

Mark,

good question! I'll have to give it some thoughts.

Friedrich

Uninstall Reboot Message

When we run the uninstall to remove a previous version, sometimes a client will see a "reboot required" message.
Attachment 5067
When this happens they are basically caught in a "no win" scenario: if they proceed, then the uninstallation will be placed in the "pending file rename" operations which (after the next reboot) will actually remove some of the current version files. If they do choose to reboot, then the installation (which is designed only to be run when previous versions are present) complains because no previous version was found.

I have implementing a "reboot and resume" feature for some of our other products. Is there a way that I can catch this condition so that I can handle it with a "reboot and resume?"