/build/static/layout/Breadcrumb_cap_w.png

msi Uninstall techniques

I am wondering if anyone has any pros or cons on the two methods I know of to do an msi uninstall. The first method I learned was to use the uninstall string for the product which is found in the registry. The second method I have begun to use in to utilize the original msi that you installed with. I have begun to think that there may be advantages to the later method because there seems to be a bit of security that the you are certain the tools you need to uninstall will be there. I deploy the msi with a batch file to execute it. It seems possible that registry problems could affect the use of the uninstall string. But then again you would probably want to re-image that machine. Any thoughts?

0 Comments   [ + ] Show comments

Answers (8)

Posted by: yatyat 20 years ago
Yellow Belt
1
by typing "msexec /x {GUID}", it only shows "Are you sure you want to uninstall this product". But no product name is shown. How can I show the product name too? Or how can I run the uninstaller the same as clicking the Add/Remove Program?
Thx so much!
Posted by: MSIMaker 20 years ago
2nd Degree Black Belt
0
Using the msi is the preferred method because its the original installer and will use the properties it used on the install to uninstall it.
Posted by: ab2cv 20 years ago
Orange Senior Belt
0
I wouldn't have thought there was any difference really. When you install an MSI, an uncompressed version of it is copied into C:\WINDOWS\Installer and this is what is used to uninstall the MSI if you use the product code. This is also how the MSI is uninstalled if you use the Add/Remove programs from the control panel. As the locally cached MSI is an exact copy of your original source MSI, it should make no difference. . . unless I'm missing something?

Furthermore, if your source MSI is stored across a network, then you'll reduce network traffic during an uninstall if you use the locally cached version
Posted by: ewall 20 years ago
Purple Belt
0
I'm with ab2cv... the locally-cached copy of the MSI should be faster, and moreso it should be exactly what was installed.

If your company is like my current employer, sometimes we make updates to the original MSI and inc the version number (1.0.1)... doing a "msiexec /x package.msi" might be incorrect in this case if the older v1.0.0 version is installed, whereas doing the "msexec /x {GUID}" is always correct.
Posted by: kkaminsk 20 years ago
9th Degree Black Belt
0
Also if you uninstall by going MSIEXEC /X \\networkserver\share\msi.msi the system has to load up the MSI to determine it's GUID. When you use MSIEXEC /X {GUID} the system knows right away what needs to be done.
Posted by: McClane 20 years ago
Yellow Belt
0
I made an msi from the IBM Iseries Access setup, with Installshield Adminstudio6 - Repackager - WXP
It works without any problems, but if I remove the program from the Control Panel, and restart the computer, I get the "Application Error: Isass exe" message and the computer does not log in after restarting.
What can be the problem?
Posted by: d_fisher 20 years ago
Senior Yellow Belt
0
If you want it to be completely silent put a /Q at the end.

msiexec /x {QUID}/q

Doug
Posted by: ab2cv 20 years ago
Orange Senior Belt
0
<quote>how can I run the uninstaller the same as clicking the Add/Remove Program? </quote>

To do this, check the registry value stored under 'UninstallString' or 'ModifyPath', for the product you want to uninstall - found at;

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID}\

This is the command that is run when you try to uninstall aproduct via the Add/Remove programs.

Alan
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
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