/build/static/layout/Breadcrumb_cap_w.png

Java 1.50.09 build 3

I can't for the life of me get the auto update to turn off. Has anyone gotten this to work on the latest build?

This doesn't work:

msiexec /i java.msi ALLUSERS=1 REBOOT=ReallySuppress JAVAUPDATE=0 AUTOUPDATECHECK=0 IEXPLORER=1 JU=0 CUSTOM=1 /qn

0 Comments   [ + ] Show comments

Answers (7)

Posted by: venki_msi 18 years ago
Senior Yellow Belt
0
Actually u can try another way, install the application> check for java control panel icon, or click the shortcut and u can find a java system tray icon > uncheck the auto upadte option, capture the regsitry changes and inculde in to the package..

This is also one of the way of disabling the auto upadtes,

do u have any java related entry related control icon or shortcuts(lt will look coffee cup icon)?

Thanks,

Venki
Posted by: AngelD 18 years ago
Red Belt
0
Java Update runs a scheduler (jusched.exe) as a background process. Make sure to remove this from being executed. Possible location would be: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\SunJavaUpdateSched

Info about "Update Panel Options" and "Java Update Scheduler" can be found at http://java.sun.com/j2se/1.5.0/docs/guide/deployment/deployment-guide/jcp.html
Posted by: turbokitty 18 years ago
6th Degree Black Belt
0
http://java.sun.com/j2se/1.5.0/docs/guide/deployment/deployment-guide/silent.html

As you can see from the deployment guide, JAVAUPDATE=0 is supposed to work.. but it doesn't with this build I was hoping someone else had figured this out... I'm not keen on snapshotting the registry change.
Posted by: turbokitty 18 years ago
6th Degree Black Belt
0
I ran a repackager snapshot and it changes data in a binary registry key so that's not an option either.

This whole "MSI" is actually just a wrapper for an executable install. The wrapper collects the installation options through the dialogs and populates corresponding properties. The properties are then used as install conditions for custom actions that make DLL calls.

The whole MSI has about 5 components that are just zip files that get uncompressed by a custom action. It's a good example of how not to code an MSI.
Posted by: AngelD 18 years ago
Red Belt
0
If the MSI is only a wrapper then just repackage the whole thing and off you go ;)
Posted by: turbokitty 18 years ago
6th Degree Black Belt
0
Haha.. it's true! I could do that.

I was playing with it a bit more and apparently I was getting too fancy. Some/all of the properties that used to suppress the updates in previous versions conflict with JAVAUPDATE.
This works:

msiexec /i java.msi ALLUSERS=1 REBOOT=ReallySuppress JAVAUPDATE=0 /qn

Now I have to figure out why Radia pukes on it. <sigh>
Posted by: aogilmor 18 years ago
9th Degree Black Belt
0
you can get around this but it's not easy. create a transform and put a CA in to delete the JavaUpdate reg key, waaaay at the end of the installexecute sequence.

Even this is not fool proof, however, as removing the app will trigger re-population of this key. this is a known java bug.

I agree this is a particularly badly designed installation.
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