/build/static/layout/Breadcrumb_cap_w.png

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.

0 Comments   [ + ] Show comments

Answers (7)

Posted by: anonymous_9363 11 years ago
Red Belt
0
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.
Posted by: Automan 11 years ago
Senior Yellow Belt
0
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
Posted by: anonymous_9363 11 years ago
Red Belt
0
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.
Posted by: Automan 11 years ago
Senior Yellow Belt
0
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.
Posted by: anonymous_9363 11 years ago
Red Belt
0
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.
Posted by: Automan 11 years ago
Senior Yellow Belt
0
I'm installing it on Windows 7 and this uses Installer version 5.0.

those properties are set and still gives the message.
Posted by: Automan 11 years ago
Senior Yellow Belt
0
I think I've found the issue. I didn't set the property correctly.

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.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ