Key Path: SOFTWARE\JavaSoft\Java Update\Policy If you didn't have Java installed on your management station, you can enter the following: When you’re taken back to the last window, it should look something like the screenshot below. In the bottom window, you should see EnableJavaUpdate. (If you don't, you can skip the next couple of steps and copy the entry manually.) In the window that opens, click the “.” button next to Key Path.īrowse down to HKEY_LOCAL_MACHINE > SOFTWARE > JavaSoft > Java Update > Policy. If you have Java installed on your management station, you can browse the registry to the setting you will be changing. Right-click and choose New > Registry Item. In your GPO, go to Computer Configuration > Preferences > Windows Settings > Registry. In my example, it is an empty GPO, but there’s no reason why you can’t add this to an existing GPO. First off you will need a Group Policy Object (GPO) that applies to your computers that need to have the updater disabled. You could set this manually, but there’s actually a much easier way to do this in Group Policy. Here’s what it looks like in the Windows Registry with updates enabled: The registry entry is named EnableJavaUpdate and is a DWORD value that defaults to 1 for the update functionality to be enabled. The full path of the key is HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Update\Policy. There’s a registry setting in HKEY_LOCAL_MACHINE that will allow you to completely disable both update notifications and the update functionality. This tutorial applies to 32-bit Java running on a 32-bit Operating System or 64-bit Java running on 64-bit Operating System.ĭisabling the Java update notifications is actually pretty easy. If you disable the update notifications, you still need to keep the software up to date! Many of the security flaws in 3rd party software can lead to malware infections and/or compromised computers. This tutorial is intended for systems administrators that are using some kind of systems management product for updating 3rd party software like SCCM, Landesk, etc.
Here’s how to disable the Java update checks so that your end users don’t see messages like this: In a small environment, this may not be a problem, but in a larger environment, this can generate a lot of unnecessary support requests when a user that doesn’t have Admin rights gets a UAC prompt that wants Admin credentials.
To totally unlock this section you need to Log-inīy default, an installation of Java will check for updates and then will prompt the end user to install the update whether or not the user has Admin rights.