Error 1720 uninstalling a msi

I'm trying to uninstall a msi file and allways I find the error message "Error 1720 -There is a problem with this Windows Installer package. A script required for this install to complete could not be run" and the unistallation doesn't continue.
I know how I have to do to solve this error when I'm making a msi package, but this is a package made by someone else, and I need to uninstall it.
Do you know how can I do that?


0 Comments   [ + ] Show comments

Answers (2)

Posted by: Jsaylor 13 years ago
Second Degree Blue Belt
The least crude option would be to log the installation (use /l* c:\mylog.log,) find the custom action that's responsible for stopping the installation, and see what it's trying to do (hopefully it's commented!) or what it's failing on, then attempt to remedy the situation causing the error in the first place before uninstalling.

Most of the time when an uninstall fails on a CA, it's because the author didn't expect X or Y condition, and it may be best to correct the condition rather than try to modify somebody else's MSI.

EDIT: Unless the dude that made it never bothered testing an uninstallation, in which case you'll probably have to fix or get rid of the CA in the MSI, redeploy it to your workstations with REINSTALL=all and REINSTALLMODE=vomus to recache the MSI with the proper files, then run an uninstall of the new package afterwards.
Posted by: FunWithApps 13 years ago
Senior Yellow Belt
If this is on a single machine, you could try running Windows Installer Cleanup tool.


I don't think there is any way to run this on multiple machines.
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