Help Center


Java 8 Update 60-b27

Installs 32-bit Java 8 Update 60 Build 27 on 32-bit and 64-bit computers.
**Google Chrome 42+ disables Java and all other NPAPI plugins**
Performs Uninstall of previous Java 8 updates. The Java8U60.mst file removes the forced static installation introduced in 8 Update 20.
Does not remove Java 6 or 7
Does not stop Microsoft Edge browser (since Edge doesn't support the Java plugin)
Deployment disables Java Auto Update
Java 8 is not supported on XP and 2003 computers.


Update 60-b27



Package Library Subscription Level

Package Library availability for Java 8:

Download into PDQ Deploy
Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request


  • 0

    How is this different than the download that Oracle has posted as they do not refer to it anyway but version 8 and build 60?  (I..e what is "b27")

  • 0

    All these years I *thought* the build was after the hyphen, but it is not!

    "The full version string for this update release is 1.8.0_60-b27 (where "b" means "build"). The version number is 8u60."




  • 0

    Great catch and great question, Eddie. I'd like to explain why we made this change.

    Oracle has finally decided to add the full version (including the build) into the Uninstall key of the Registry. This means that Inventory programs, such as PDQ Inventory and SCCM can easily determine the full version of the installed JRE.

    There are a handful of instances in the past when Oracle has released a new build of Java without incrementing the Update number. This would wreak havoc for a SysAdmin since they couldn't easily be able to tell which computer had the latest build or not. In PDQ Inventory you would have to use a Registry or a File Scanner to differentiate different builds in the same update. The last instance of this happened in Update 40 when build 25 was initially made GA (General Availability) and then build 26 went GA a few weeks later. According to Inventory programs two computers with the different builds (25 and 26) were both reported as Java 8 Update 40 with a version of 8.0.400.

    Anyway, since the two builds in Update 40 we have internally kept track of the full version number so that the Package Library would be able to see that a later build was released it would show up as a new version.

    Now that Oracle includes the full version (Family, Minor, Update, Build) in the registry both PDQ Deploy and PDQ Inventory can easily tell the difference between new builds within the same Update without having to use File or Registry scanners.

    The actual version that Oracle places in the registry for the recent update 60 is listed as 8.0.600.27. Since this isn't very readable we just modified our usual labeling of the PDQ Deploy package name from "...Update nn" to "...Update nn-b_nn_".

    To illustrate the change, here is a PDQ Inventory screenshot of a computer with an older Java 8 Update 51 (64-bit) and the latest 32-bit version of Java 8 Update 60. Note how the build number is now accounted for in the version field for Update 60.



  • 0

    I may be mistaken but, I thought the latest java version was supposed to perform an uninstall of previous java updates.  I still show both on my system.

  • 0


    If you use the package from the Package Library then an uninstall of previously released Java 8 updates is performed. (It won't catch any beta versions).

    If you built your own package or just ran the installation manually then it doesn't perform an uninstall. This behavior was changed in Java 8 Update 20. 

    Did you deploy the version from the Package Library?

  • 0

    Hello Shane,

    I imported and deployed the version from the package library - Java 8 Update 60-b27.  I tested the deployment on my system first, and that's when is saw both version still there.

    screenshot below.


    Thanks for your help.


  • 0

    Sorry, screen shot didn't show on my side.  Will attach the file.


  • 0

    Will you post the Uninstall string for Java 8 Update 51? You can copy it from that same window. The column should be just to the right of the Install Date. We have seen a few instances (albeit a long time ago) where there were some Java installations that had different uninstall product keys.

  • 0

    Here it is:

    MsiExec.exe /qn /norestart /X{26A24AE4-039D-4CA4-87B4-2F83218051F0}


  • 0


    Can I just add the uninstall string to the package that I have imported already. Adding to the list of strings that you guys have.


  • 0

    Sorry for the last comment, as I see that the same string is already in there.

  • 0

    Is this happening on all of your systems or just one? Click on the deployment. Go to a machine that didn't have 51 uninstalled and click on the 5 Steps link. Open the output log for the Uninstall step. Unless the target computer was Windows 10, you should see a blank space under the second to last command (which means it was successful). See attachments.

    So far (after about two dozen different attempts) we have been unable to duplicate this issue.




  • 0

    I am using the free version of PDQ. I am hoping our bosses will allow me to purchase the version but in the mean time to make my life easier I am using PDQ to install these programs. Java 8 Update 60-b27 is not deploying on all the targets in the list. This is because I must not be gaining the deployment version to distribute. Could anyone assist me with locating the correct version?


    Also since this is the free version and a responsibility that I have just taken over... do I need to create a step to remove the previous java version? It looks like my predecessor didn't realize this and all of the PC's had two versions of Java when I took over. Thanks for any help in advance.

  • 0

    Hi Ricky, Java 7 will not automatically uninstall when you push Java 8. Previous updates of Java 8 will be uninstalled, but you can have multiple versions. You would want to do an uninstall of 7 if you didn't want to have both versions. A quick way to do this is to use our Deploy Enterprise trial. Doing so gives you access to up to three packages in our package library. You would want to download the uninstall for Java 7. You can start your trial at A key will be automatically emailed to you.

  • 0

    Thank you for the information. I will try that today.

Article is closed for comments.