Java has become a little bit of a nightmare to deploy and looking for answers on Google doesn’t make you much wiser since people states all kinds of things in different forums. Therefore, I’m going to make my best to clarify how it works in Java 6 (1.6.0). Previous versions (1.5.0) supported silent install switches like JAVAUPDATE=0. However I’ve been reading through the silent switches documentation for Java 1.6.0 and have been unable to find anything equivalent at all to what they had back in the days…

This means that we will have to use more drastic methods and edit the registry to stop the Java Auto Updater. But first, we need to grab the correct installer. Do this by visiting Oracles website.  Grab the Offline-installer. I noticed that you only will be able to see the 64-bit version if you’re running a 64-bit OS. I will show you further down that the difference between the x86 installer and the x64 installer is quite big.

Now it’s a little bit up you if you want to disable Java directly in the installation or by using a GPO or GPP. If you’re going to use GPO/GPP, simply install Java by using the /s switch. Like this:

jre-6u24-windows-i586-s.exe /s (Remember that you’re probably will be using a different version)

If you’re going to disable Java directly, add this information into a .bat-file and put it right beside the Java installer (jre-6u24-windows-i586-s.exe):

Start /wait jre-6u24-windows-i586-s.exe /s

Start /wait means that the installer needs to finish before the .bat-file starts processing the next command line.

Next, we need to edit the registry to disable the Java Auto Update “feature”.

This parameter is located in different locations depending on what architecture of Windows you are using and what version of Java you have installed. However, something really important to know is that the Java x64 doesn’t have an Auto Updater.  This means that you’re good to go if this is the version you’re planning to use!

The below table describes the different location scenarios of the registry key you need to change:

OS Architecture Java Version Registry Path
Windows x86 Java x86 HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Update\Policy
Windows x64 Java x86 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\JavaSoft\Java Update\Policy
Windows x64 Java x64 No Java Update feature included in installation.

The magic key that you need to change is:


If you’re going to use a GPP, I would say that you’re quite set now. Just add the registry information above to a GPP registry update policy. It might be a good idea to select the box to “Apply once and to not reapply” on the Common tab. You can also use Item-level targeting to look for the current registry value, EnableJavaUpdate=1, to ensure that the policy only strikes on computers with this issue.

However, if you’re going to disable Java Update directly in the installation, create a .reg file containing the following information and save it right beside the .bat file you previously created:

Windows Registry Editor Version 5.00


[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\JavaSoft\Java Update\Policy]

Yes, this will add a little bit more information to the registry than you might need if you’re planning to use only x86 or x64, so feel free to edit it to match your environment.

Now you need to add the .reg file to your .bat file. Do this by entering the following information into the .bat file:

regedit.exe /s disableupdate.reg

Also ensure that your folder containing all necessary files now look something like this:

You’re done! Simply execute the .bat file in your deployment solution to deploy Java without Java Auto Update. You can of course this in any deployment solution like SCCM or Altiris but here’s a sample of how it looks in MDT: