Please help!!

I'm trying to put a script together to uninstall old versions of Macromedia Shockwave Player. The Adobe Uninstaller.exe doesn't work.

I finally managed to uninstall via msiexec.exe /x but when I used with the GUID (uninstall string) I get the following Windows Installer Prompt:

DO YOU WANT TO UNINSTALL THIS PRODUCT?

YES NO


For some reason I can't make this prompt go away and just let the uninstall be seamless. The script stalls at this waiting for the user to click 'YES' OR 'NO'

I tried the -qb and -qn switches but they don't help. The installation still stalls and it just sits there with no prompt at all...

I also tried a registry setting in the HKEY_CURRENT_USER\Software\Microsoft\Windows\Current Version\Explorer and added the following Key and Value:

KEY = DontShowMeThisDialogAgain VALUE = GUID or Uninstall String of Shockwave

Is there any registry setting, value, or something in my script I can include to silence, turn off that annoying Uninstall Prompt so the application can uninstall without this?

I've tried just about everything and I'm banging my head against the wall!

Would an .mst do the trick?

Any comments or suggestions would be greatly appreciated.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Check your string..

With progress bar
Msiexec /x {GUID} /qb
or progress bar with no Cancel button
Msiexec /x {GUID} /qb!
or for silent
Msiexec /x {GUID} /qn

I'm not sure if it would matter but you could try
Msiexec /x {GUID} LIMITUI=1

ALSO - Log your uninstall to see why it is hanging - or atleast try to see
e.g. Msiexec /x {GUID} /l*v c:\temp\Uninstall.log /qb!

Secondly - an MST is only applied during installation, so no it wouldn't help in this situation.
Answered 07/10/2007 by: gmorgan618
Blue Belt

Please log in to comment
0
Thanks for the reply. I tried the following but no luck:

Msiexec /x {GUID} /qb!

Msiexec /x {GUID} LIMITUI=1


Here is a screenshot of that prompt I was telling you about that I want to silence:

http://i6.photobucket.com/albums/y223/aquarta/ScreenHunter_02Jul1112.47.gif

I run the script, everything works and the moment it gets to the uninstall portion, the script stalls in its tracks and displays that prompt waiting for user input. For the life of me I can't figure out how to get the script to uninstall and by pass this message. Answer file? I thought one of the msiexec switches would help but all it does is hides the problem and not fix it (prompt disappears but script still stops).

Thanks for letting me know that .mst won't work so I don't have to waste time creating one.

Any other possible ideas?
Answered 07/11/2007 by: aquarta
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: aquarta

Thanks for the reply. I tried the following but no luck:

Msiexec /x {GUID} /qb!

Msiexec /x {GUID} LIMITUI=1


Here is a screenshot of that prompt I was telling you about that I want to silence:

http://i6.photobucket.com/albums/y223/aquarta/ScreenHunter_02Jul1112.47.gif

I run the script, everything works and the moment it gets to the uninstall portion, the script stalls in its tracks and displays that prompt waiting for user input. For the life of me I can't figure out how to get the script to uninstall and by pass this message. Answer file? I thought one of the msiexec switches would help but all it does is hides the problem and not fix it (prompt disappears but script still stops).

Thanks for letting me know that .mst won't work so I don't have to waste time creating one.

Any other possible ideas?



/qb!

Familiarize yourself with the msi.chm help file and the Microsoft online resources. http://msdn2.microsoft.com/EN-US/library/aa367988.aspx

/qb! is basic UI which as you saw, will prompt the user. You have to use a lower level of UI (/qn) to avoid the prompt.

Hope this helps.
Answered 07/11/2007 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
Thank you very much for your reply and the links. Unfortunately it appears that any type of msiexec switch doesn't work. The dialog that gets prompted are with "yes" and "no" buttons. The switches that i looked up for msiexec looks like they are for "cancel" buttons. The other switches are to turn off the UI and the user doesn't see anything but that just makes the dialog prompt run in the background and the script still hangs, waiting for user input to click either "yes" or "no"

Is there another way other than msiexec to run the uninstall string from the registry and at the same time cancelling out or automatically answering the "yes" or "no" to that prompt?
Answered 07/12/2007 by: aquarta
Senior Yellow Belt

Please log in to comment
0
/qn is supposed to do that. it should work with either a guid or path to the msi i believe. did you try that?
Answered 07/12/2007 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
My thoughts exactly. I thought the /qn switch would do the trick. Here is my line of code in my script just to make sure the syntax is correct:

MsiExec.exe /x {838A1BC9-95CA-4880-9BE3-2A7D23600A2B} /qn /l msi_swf101116.log

As a result, here is a screen capture of what happens when I deploy the package via Symantec Live State. As you'll notice the script stops as Line 20 (hence the line above) and nothing happens from there. The prompt is probably hiding in the background but the user can't see it:

http://i6.photobucket.com/albums/y223/aquarta/ScreenHunter_01Jul1214.03.gif

My script is all set to go for installing etc. but the uninstall is the only part that is hanging me up!

Again, thanks for your help. Any other help or suggestions would be greatly appreciated.
Answered 07/12/2007 by: aquarta
Senior Yellow Belt

Please log in to comment
0
that's a symantec issue, not a Windows Installer issue. Looks like it's just not handling the command line correctly.
Answered 07/12/2007 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
perhaps a little off topic maybe related.

Are you aware that flash and shockwave have user based CA's which fail on deployment systems which attempt to perform install and uninstall during logged out scenarios.
Answered 07/12/2007 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
Thanks for the tip. Just for kicks, I created a batch file with just the msiexec.exe /X {GUID} /-qn /log and it worked perfectly. However, when putting that same line in LiveState, that where it just hangs. I contacted Symantec technical support and they are currently investigating. At first the guy seemed like he didn't want to help because he thought it was me that was the problem (user error) and not LiveState.

After describing that it works in a plain .bat file and not working in LiveState, he changed his tune. I'm waiting to see what he has discovered.
Answered 07/17/2007 by: aquarta
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity