/build/static/layout/Breadcrumb_cap_w.png

Silent Uninstallation of JRE 1.3.1_19

I am able to install silently using the response file. But unable to uninstall silently with response file.

Tried the following but no luck.

1. Created response file during uninstallation using the below command.

"C:\Program Files\InstallShield Installation Information\{68249B7A-B714-11D7-88E8-0050DA21757E}\Setup.exe" -uninst -r -f1"c:\temp\uninst.iss"

2. Copied the uninst.iss file to C:\Program Files\InstallShield Installation Information\{68249B7A-B714-11D7-88E8-0050DA21757E}\
3. Tried to uninstall using the below command.
"C:\Program Files\InstallShield Installation Information\{68249B7A-B714-11D7-88E8-0050DA21757E}\Setup.exe" -uninst -s -f1"C:\Program Files\InstallShield Installation Information\{68249B7A-B714-11D7-88E8-0050DA21757E}\uninst.iss"

no luck. Still the UI screens are coming.

any help would be highly appreciated!!!

0 Comments   [ + ] Show comments

Answers (5)

Posted by: spartacus 11 years ago
Black Belt
0
Have you checked the uninstall string in the registry following the installation - it should be located in the key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\JRE 1.3.1 ?

If it takes the following form :

C:\WINDOWS\IsUninst.exe -f"C:\Program Files\JavaSoft\JRE\1.3.1\Uninst.isu"

You can modify this command to perform the silent installation as follows

C:\WINDOWS\IsUninst.exe -y -x -a -f"C:\Program Files\JavaSoft\JRE\1.3.1\Uninst.isu"

This method works for JRE 1.3.1-b24, so hopefully it should work for 1.3.1_19

Regards,

Spartacus
Posted by: WSPPackager 11 years ago
Senior Purple Belt
0
Hi,

I did extract the uninstallstring from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{68249B7A-B714-11D7-88E8-0050DA21757E}\
RunDll32 C:\PROGRA~1\COMMON~1\INSTAL~1\engine\6\INTEL3~1\Ctor.dll,LaunchSetup "C:\Program Files\InstallShield Installation Information\{68249B7A-B714-11D7-88E8-0050DA21757E}\Setup.exe" -uninst

I prepared the response file while uninstallation and copied to C:\Program Files\InstallShield Installation Information\{68249B7A-B714-11D7-88E8-0050DA21757E}\
as I already explained.
Posted by: spartacus 11 years ago
Black Belt
0
OK, so it looks like there is a difference between JRE 1.3.1_19 and the example I used which was 1.3.1-b24 .. oh, well it was worth a try :-)


Nevertheless, I note that your own uninstall string was

RunDll32 C:\PROGRA~1\COMMON~1\INSTAL~1\engine\6\INTEL3~1\Ctor.dll,LaunchSetup "C:\Program Files\InstallShield Installation Information\{68249B7A-B714-11D7-88E8-0050DA21757E}\Setup.exe" -uninst

so you should first try the following to record your uninstall response file

RunDll32 C:\PROGRA~1\COMMON~1\INSTAL~1\engine\6\INTEL3~1\Ctor.dll,LaunchSetup "C:\Program Files\InstallShield Installation Information\{68249B7A-B714-11D7-88E8-0050DA21757E}\Setup.exe" -uninst -r -f1"c:\temp\uninst.iss"

then move your uninst.iss to C:\Program Files\InstallShield Installation Information\{68249B7A-B714-11D7-88E8-0050DA21757E} as you did before

then try

RunDll32 C:\PROGRA~1\COMMON~1\INSTAL~1\engine\6\INTEL3~1\Ctor.dll,LaunchSetup "C:\Program Files\InstallShield Installation Information\{68249B7A-B714-11D7-88E8-0050DA21757E}\Setup.exe" -uninst -s -f1"C:\Program Files\InstallShield Installation Information\{68249B7A-B714-11D7-88E8-0050DA21757E}\uninst.iss"

In other words, I am suggesting you retain the RunDll32 C:\PROGRA~1\COMMON~1\INSTAL~1\engine\6\INTEL3~1\Ctor.dll,LaunchSetup portion of the uninstall string, which you don't appear to be doing at the moment.

Regards,

Spartacus
Posted by: anonymous_9363 11 years ago
Red Belt
0
JRE is - as an application - trivially simple, in terms of what it dumps on to a workstation. As such, removal is equally as simple. In the time you've spent faffing about trying to get the uninstall string to work, you could have built an uninstalling MSI by populating the RemoveFile and RemoveRegistry tables. At worst, you could have captured the uninstall..
Posted by: WSPPackager 11 years ago
Senior Purple Belt
0
Spartacus,

When we use RunDll32 commandline with repsonse file, receiving an error. This command is unable to recognise the switch -f1.

VbScab,

Yes, we can convert it into an MSI. we have done many in the past but curious to check if someone had answer/solution for this problem. If so, we can make use of the vendor supplied code rather than being converted into an MSI.

will try couple of other approaches, if nothing works out then we know the solution "Convert it into an MSI"
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

Share

 
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