Closing Explorer on Uninstall
Hi,
i am currently packaging an application called Winmerge 2.12.4 on Win 7. On Uninstall(System Context) it prompts to close down explorer. If I uninstall as an Admin it just closes explorer without prompting. Does anyone know a way around this?
any help is greatly appreciated.
i am currently packaging an application called Winmerge 2.12.4 on Win 7. On Uninstall(System Context) it prompts to close down explorer. If I uninstall as an Admin it just closes explorer without prompting. Does anyone know a way around this?
any help is greatly appreciated.
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
A way around what, the restart itself or the prompt/lack of prompt?
From reading about the product, I assume it installs as an Explorer extension, in the same way that a similar product - Beyond Compare - does. As such, an Explorer restart would be required to remove the integration e.g. the context menus.
From reading about the product, I assume it installs as an Explorer extension, in the same way that a similar product - Beyond Compare - does. As such, an Explorer restart would be required to remove the integration e.g. the context menus.
Posted by:
Automan
14 years ago
Sorry, I didn't make that clear.
I don't want it to prompt or to restart explorer. I was hoping that a reboot at the end of the uninstall would take care of removing the explorer extension.
I've added a property that worked for a colleague of mine but didn't work in my package MSIRESTARTMANAGERCONTROL=Disable
I don't want it to prompt or to restart explorer. I was hoping that a reboot at the end of the uninstall would take care of removing the explorer extension.
I've added a property that worked for a colleague of mine but didn't work in my package MSIRESTARTMANAGERCONTROL=Disable
Posted by:
anonymous_9363
14 years ago
Hardly surprising, as the installer isn't Windows Installer-based! :-)
Your best bet would be to capture the legacy set-up to MSI format using your MSI authoring tool of choice.
Your best bet would be to capture the legacy set-up to MSI format using your MSI authoring tool of choice.
Posted by:
Automan
14 years ago
Hi VBScab,
Thanks for the response. That is what I have done. I've repackaged the app using Install Shield. Tested all seemed fine except for this issue. I added the property listed above and set it to Disable. Still didn't resolve the issue.
Thanks for the response. That is what I have done. I've repackaged the app using Install Shield. Tested all seemed fine except for this issue. I added the property listed above and set it to Disable. Still didn't resolve the issue.
Posted by:
anonymous_9363
14 years ago
MSIRESTARTMANAGERCONTROL is only supported from WI v4.0 onwards, IIRC. If your machines don't have at least that version, the engine will simply ignore that property value.
Try setting 'RebootYesNo' to 'N' and 'Reboot' to 'R' in your transform.
Try setting 'RebootYesNo' to 'N' and 'Reboot' to 'R' in your transform.
Posted by:
Automan
14 years ago
I'm installing it on Windows 7 and this uses Installer version 5.0.
those properties are set and still gives the message.
those properties are set and still gives the message.
Posted by:
Automan
14 years ago
I think I've found the issue. I didn't set the property correctly.
MSIRESTARTMANAGERCONTROL was MSIRESTARTMANAGER in my MSI. Doh!!!
MSIRESTARTMANAGERCONTROL was MSIRESTARTMANAGER in my MSI. Doh!!!
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.