Custom Uninstaller - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

LearnSomethingNew
Posts: 2
Joined: Wed Jun 29, 2011 12:39 am

Custom Uninstaller

I have an older piece of software installed on 500+ Windows XP Pro SP3 clients that needs to be removed silently. The original installer was built using wise and the uninstall package will not accept the standard removal string:

Code: Select all

unwise.exe /s "C:\Program Files\Program\INSTALL.LOG".
I'm looking for resources that I can utilize with Advanced Installer. The software that I need to uninstall has hooks into some system services that require a reboot to remove. Can anyone point me in the right direction?
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Custom Uninstaller

Hello and welcome to the Advanced Installer Forums,

Here is an article to help you with this.

To find out the .MSI GUID, you can contact Wise for the command line that extracts the .MSI from the .EXE. Once you have the .MSI, you can edit it with Orca.exe and find out the GUID.

You can follow this article for the silent msiexec.exe command line that can be adapted for the uninstall command line from the previous article as well.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
LearnSomethingNew
Posts: 2
Joined: Wed Jun 29, 2011 12:39 am

Re: Custom Uninstaller

Mihai,

Thank you for the quick response. I did some testing with the original install package and these were my results:

1) Running the .exe installer extracts a handful of .tmp files, 1 .dat file, and 1 .dll file to the %temp% directory. No MSI packages =/

2) I ran the .exe installer with the /X string to optionally extract specific files. There are no MSI packages included. It appears that this installer is comprised of all the root files. The package is simply extracting them to the proper locations upon execution.

Given this information, what's the suggested route when there is no MSI GUID to call? Based on the research I've done thus far, the unwise.exe is calling the INSTALL.LOG file to reference which files/registry keys need to be removed.
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Custom Uninstaller

Hello,

In this case, you should contact Wise support or the .EXEs author to find out if it's .MSI based. Usually the .MSI should be extracted upon the .EXE execution in the Temp folder. Another clear indicator is that the msiexec.exe process should start after executing the .EXE( you can easily verify this using the Windows Task Manager or Process Explorer tool ).

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”