Download Java MSI x64 and x86 8.0.1910.12

Download Java MSI x64 and x86 8.0.1910.12.

For installtion with Configuration Manager use:


msiexec.exe /i "jre1.8.0_191.msi" /qn JU=0 JAVAUPDATE=0 AUTOUPDATECHECK=0 RebootYesNo=No


msiexec.exe /i "jre1.8.0_19164.msi" /qn JU=0 JAVAUPDATE=0 AUTOUPDATECHECK=0 RebootYesNo=No

For uninstall use:


msiexec /x {26A24AE4-039D-4CA4-87B4-2F32180191F0} /qn /norestart



msiexec /x {26A24AE4-039D-4CA4-87B4-2F64180191F0} /qn /norestart

Release Highlights

New Features


Build Environment Update Linux x86/x64 Moved to gcc 7.3 On x86/x64 Linux, the toolchain used to build the JDK has been upgraded from GCC 4.3 to GCC 7.3.



Changed Central File System Location for File The file system location in Windows for the file has been moved from %ProgramData%\Oracle\Java\ to %ProgramFiles%\Java\conf

There is no change in the file path for Linux, Solaris, or macOS.


Disabled all DES TLS Cipher Suites DES-based TLS cipher suites are considered obsolete and should no longer be used. DES-based cipher suites have been deactivated by default in the SunJSSE implementation by adding the “DES” identifier to the jdk.tls.disabledAlgorithms security property. These cipher suites can be reactivated by removing “DES” from the jdk.tls.disabledAlgorithms security property in the file or by dynamically calling the Security.setProperty() method. In both cases re-enabling DES must be followed by adding DES-based cipher suites to the enabled cipher suite list using the SSLSocket.setEnabledCipherSuites() or SSLEngine.setEnabledCipherSuites() methods.

Note that prior to this change, DES40_CBC (but not all DES) suites were disabled via the jdk.tls.disabledAlgorithms security property.


Removal of Several Symantec Root CAs The following Symantec root certificates are no longer in use and have been removed:

  • Symantec
    • equifaxsecurecaDN: OU=Equifax Secure Certificate Authority, O=Equifax, C=US
    • equifaxsecureglobalebusinessca1DN: CN=Equifax Secure Global eBusiness CA-1, O=Equifax Secure Inc., C=US
    • equifaxsecureebusinessca1DN: CN=Equifax Secure eBusiness CA-1, O=Equifax Secure Inc., C=US
    • verisignclass1g3caDN: CN=VeriSign Class 1 Public Primary Certification Authority – G3, OU=”(c) 1999 VeriSign, Inc. – For authorized use only”, OU=VeriSign Trust Network, O=”VeriSign, Inc.”, C=US
    • verisignclass2g3caDN: CN=VeriSign Class 2 Public Primary Certification Authority – G3, OU=”(c) 1999 VeriSign, Inc. – For authorized use only”, OU=VeriSign Trust Network, O=”VeriSign, Inc.”, C=US
    • verisignclass1g2caDN: OU=VeriSign Trust Network, OU=”(c) 1998 VeriSign, Inc. – For authorized use only”, OU=Class 1 Public Primary Certification Authority – G2, O=”VeriSign, Inc.”, C=US
    • verisignclass1caDN: OU=Class 1 Public Primary Certification Authority, O=”VeriSign, Inc.”, C=US

Removal of Baltimore Cybertrust Code Signing CA The following Baltimore CyberTrust Code Signing root certificate is no longer in use and has been removed:

  • baltimorecodesigningcaDN: CN=Baltimore CyberTrust Code Signing Root, OU=CyberTrust, O=Baltimore, C=IE

Removal of SECOM Root Certificate The following SECOM root certificate is no longer in use and has been removed:

  • secomevrootca1DN: OU=Security Communication EV RootCA1, O=”SECOM Trust Systems CO.,LTD.”, C=JP
Java Improvements for Docker Containers The following changes have been introduced in JDK 10 to improve the execution and configurability of Java running in Docker containers:
  • JDK-8146115 Improve docker container detection and resource configuration usage

The JVM has been modified to be aware that it is running in a Docker container and will extract container specific configuration information instead of querying the operating system. The information being extracted is the number of CPUs and total memory that have been allocated to the container. The total number of CPUs available to the Java process is calculated from any specified cpu sets, cpu shares or cpu quotas. This support is only available on Linux based platforms. This new support is enabled by default and can be disabled in the command line with the JVM option:


In addition, this change adds a JVM option that provides the ability to specify the number of CPUs that the JVM will use:


This count overrides any other automatic CPU detection logic in the JVM.

  • JDK-8186248 Allow more flexibility in selecting Heap % of available RAM

Three new JVM options have been added to allow Docker container users to gain more fine grained control over the amount of system memory that will be used for the Java Heap:

  • -XX:InitialRAMPercentage
  • -XX:MaxRAMPercentage
  • -XX:MinRAMPercentage

These options replace the deprecated Fraction forms (-XX:InitialRAMFraction-XX:MaxRAMFraction, and -XX:MinRAMFraction).

  • JDK-8179498 attach in linux should be relative to /proc/pid/root and namespace aware

This bug fix corrects the attach mechanism when trying to attach from a host process to a Java process that is running in a Docker container.


Improved Cipher Inputs The specification of javax.crypto.CipherInputStream has been clarified to indicate that this class may catch BadPaddingException and other exceptions thrown by failed integrity checks during decryption. These exceptions are not re-thrown, so the client may not be informed that integrity checks failed. Because of this behavior, this class may not be suitable for use with decryption in an authenticated mode of operation (e.g. GCM). Applications that require authenticated encryption can use the Cipher API directly as an alternative to using this class.

Bug Fixes

The following are some of the notable bug fixes included in this release:


LDAPS Communication Failure Application code using LDAPS with a socket connect timeout that is <= 0 ( the default value ) may encounter an exception when establishing the connection.

The top most frames from Exception stack traces of applications encountering such issues might resemble the following:

javax.naming.ServiceUnavailableException: <server:port>; socket closed
at com.sun.jndi.ldap.Connection.readReply(Unknown Source)
at com.sun.jndi.ldap.LdapClient.ldapBind(Unknown Source)


Better HTTP Redirection Support In this release, the behavior of methods which application code uses to set request properties in has changed. When a redirect occurs automatically from the original destination server to a resource on a different server, then all such properties are cleared for the redirect and any subsequent redirects. If these properties are required to be set on the redirected requests, then the redirect responses should be handled by the application by calling HttpURLConnection.setInstanceFollowRedirects(false) for the original request.



You might also like

Leave a Reply

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Read More