isscript11.msi will not uninstall

I installed isscript11.msi on my WinXP box and it worked. However, when I try to uninstall it I get an error that "This patch package could not be opened. Verify that the patch package exists and that you can access it or contact the application vendor."

I have not done anything to the msi. I simply installed it, and then tried to uninstall it. I've tried it on 2 different PCs. How can I get this isscript11.msi to uninstall? [/align] [/align]I've done some research, and the leading possibility is MSIZap. [/align]
Thanks. [/align]

0 Comments   [ + ] Show comments

Answers (4)

Posted by: anonymous_9363 13 years ago
Red Belt
MSIZap won't uninstall anything. Its purpose is to remove references to packages from the registry and remove cached copies of the MSI.

How are you trying to uninstall? Control Panel/Add Remove, or from a command line? If the former, what does the uninstall string in the registry look like? Post it here.
Posted by: troy_in_wi 13 years ago
Orange Belt
It does not show in Add/Remove Programs. It does not give an uninstall string in the Registry. I'm trying to uninstall via command line.
I've tried isscript.msi /uninstall but it gives the message above about "This patch package could not be opened. Verify that the patch exists...".
I've also tried msiexec.exe /x isscript11.msi but it gives the message "Action only valid for products that are currently installed.".
Maybe it installs itself but does not fully register itself.
Posted by: pgiesbergen 13 years ago
Orange Belt
You cannot uninstall isscriptxx.msi unless you create an uninstall script yourself. At installtime, it does not publish its components so msizap is useless. You can run isscriptxx.msi countless times, It will happily install everytime.
Posted by: troy_in_wi 13 years ago
Orange Belt
Most people I talk to simply do not uninstall ISScript. Since they do not uninstall it, there is the possibility of version conflicts because different versions have shared GUIDs. I need ISScript11 installed so I can install my Primary MSI. The approach I took was to make ISScript11 install before the installation of my Primary MSI, and then also make ISScript11 install before an uninstallation of my Primary MSI. It is redundant installing, but that way I know my ISScript11 will always be present when I install or uninstall my Primary MSI.
Thanks for your help!
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


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