Adobe SVG viewer "winstall.exe" use
We're deploying the SVG viewer silently using a script to run the exe("SVGView.exe /qn"). Now, we're trying to find a way to uninstall the application silently.
I see the path to an uninstall executable(C:\Program Files\Common Files\Adobe\SVG Viewer 3.0\Uninstall\Winstall.exe
), but I don't know how to launch it or what switches to use to configure it. Does anyone have any ideas?
Thanks
I see the path to an uninstall executable(C:\Program Files\Common Files\Adobe\SVG Viewer 3.0\Uninstall\Winstall.exe
), but I don't know how to launch it or what switches to use to configure it. Does anyone have any ideas?
Thanks
0 Comments
[ + ] Show comments
Answers (11)
Please log in to answer
Posted by:
dj_xest
19 years ago
Dude, I'm also using Marimba for packaging and distribution.
If you can use 'q' for the install, you can also use it for the uninstall but not in most cases. Try to browse through the Registry Editor and look in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe SVG Viewer\UninstallString
put "-q" between the value in -u and -f--
C:\\Program Files\\Common Files\\Adobe\\SVG Viewer 3.0\\Uninstall\\Winstall.exe -u-q -fC:\\Program Files\\Common Files\\Adobe\\SVG Viewer 3.0\\Uninstall\\Install.log"
You can now incorporate it to the Marimba Packager in Customization tab by putting it directly there or use vbscript to call the uninstall command.
HOpe this help.. Send me beers when it is successful! (just kidding!) [;)]
If you can use 'q' for the install, you can also use it for the uninstall but not in most cases. Try to browse through the Registry Editor and look in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe SVG Viewer\UninstallString
put "-q" between the value in -u and -f--
C:\\Program Files\\Common Files\\Adobe\\SVG Viewer 3.0\\Uninstall\\Winstall.exe -u
You can now incorporate it to the Marimba Packager in Customization tab by putting it directly there or use vbscript to call the uninstall command.
HOpe this help.. Send me beers when it is successful! (just kidding!) [;)]
Posted by:
ditzah
8 years ago
Hey guys. Thanks to you I got the silent installation and uninstallation of Adobe SVG up and running.
Just for reference, I use Frontrange DSM to deploy the application, and I use for installation:
SVGView.exe /qn
And for uninstallation:
"C:\Program Files (x86)\Common Files\Adobe\SVG Viewer 3.0\Uninstall\Winstall.exe" -u -q -fC:\Program Files (x86)\Common Files\Adobe\SVG Viewer 3.0\Uninstall\Install.log
I also add a few keys to the registry, such as disabling the Auto Update feature:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Adobe SVG Viewer\3.03\AutoUpdate]"Enabled"="no"
And the EULA acceptance for all users:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Adobe SVG Viewer\3.03\EULA]"3.03x94"="accepted"
Thanks again.
Posted by:
dj_xest
19 years ago
Posted by:
MSIMaker
19 years ago
Posted by:
Mauricem
19 years ago
Posted by:
MSIMaker
19 years ago
Posted by:
Mauricem
19 years ago
Thanks to everyone for your responses. It worked!
Just for reference, here's the reformatted commandline option.
"C:\Program Files\Common Files\Adobe\SVG Viewer 3.0\Uninstall\Winstall.exe" -u -q -fC:\Program Files\Common Files\Adobe\SVG Viewer 3.0\Uninstall\Install.log
I'll add it to the Appdeploy package notes.
http://appdeploy.com/packages/detail.asp?id=454
BTW, we stopped using the Customization tab because it seemed unreliable, but, after this we may start using it again.
Just for reference, here's the reformatted commandline option.
"C:\Program Files\Common Files\Adobe\SVG Viewer 3.0\Uninstall\Winstall.exe" -u -q -fC:\Program Files\Common Files\Adobe\SVG Viewer 3.0\Uninstall\Install.log
I'll add it to the Appdeploy package notes.
http://appdeploy.com/packages/detail.asp?id=454
BTW, we stopped using the Customization tab because it seemed unreliable, but, after this we may start using it again.
Posted by:
MSIMaker
19 years ago
Posted by:
dj_xest
19 years ago
Posted by:
Mauricem
19 years ago
Usually we would run them as postinstall scripts. "Configuration" - "Customization" - "Add scripts".
We don't use the "Configuration" - "Startup" tab much, which is something we're trying to use more. We may be talking about the same thing though.
One undocumented trick we do use is to put files that we need to run locally as a script file. For example, if we want to run a script in a windows installer package to install a registry entry, we add the script and the reg file to the "batch path" as if it were a script file. This drops it into the 'scripts' directory of the package and we can run it locally.
We don't use the "Configuration" - "Startup" tab much, which is something we're trying to use more. We may be talking about the same thing though.
One undocumented trick we do use is to put files that we need to run locally as a script file. For example, if we want to run a script in a windows installer package to install a registry entry, we add the script and the reg file to the "batch path" as if it were a script file. This drops it into the 'scripts' directory of the package and we can run it locally.
Posted by:
rambone
18 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.