Downloads of v 8.0.202:


Last Update:

17 Jan 2019

Package Maintainer(s):

Software Author(s):

  • Oracle


java server runtime environment jre admin

Server JRE (Java SE Runtime Environment)

  • 1
  • 2
  • 3

8.0.202 | Updated: 17 Jan 2019



Downloads of v 8.0.202:



Software Author(s):

  • Oracle

  • 1
  • 2
  • 3
Server JRE (Java SE Runtime Environment) 8.0.202

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


To install Server JRE (Java SE Runtime Environment), run the following command from the command line or from PowerShell:


To upgrade Server JRE (Java SE Runtime Environment), run the following command from the command line or from PowerShell:


To uninstall Server JRE (Java SE Runtime Environment), run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade server-jre8 -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade server-jre8 -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure server-jre8 installed
    name: server-jre8
    state: present
    version: 8.0.202
    source: STEP 3 URL

See docs at

chocolatey_package 'server-jre8' do
  action    :install
  version  '8.0.202'
  source   'STEP 3 URL'

See docs at

    Name: server-jre8,
    Version: 8.0.202,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller server-jre8
   Name     = 'server-jre8'
   Ensure   = 'Present'
   Version  = '8.0.202'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'server-jre8':
  provider => 'chocolatey',
  ensure   => '8.0.202',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install server-jre8 version="8.0.202" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 15 Jul 2020.


Server JRE (Server Java Runtime Environment) for deploying Java applications on servers. Includes tools for JVM monitoring and tools commonly required for server applications, but does not include browser integration (the Java plug-in), auto-update, nor an installer.


This package unpacks the Java Server JRE version offered at to the default directory "C:\tools\Java\server-jre\jre1.8.0_{version}".

If you wish to unpack to an alternate directory, use the InstallationPath parameter. Example:
choco install server-jre8 -PackageParameters "/InstallationPath:c:\Program Files" -y

The installation will also set the JAVA_HOME environment variable to the destination directory if not present yet and add %JAVA_HOME%/bin to the PATH environment.

This package is only available in 64-bit.


The following package parameters can be set:

  • /InstallationPath - Install to a different destination folder. Default: C:\tools\Java\server-jre
  • /Force - Force setting JAVA_HOME to the new version even if the variable was already set
  • /Machine - Set JAVA_HOME and PATH on 'Machine' level, instead of 'User' level

These parameters can be passed to the installer with the use of --packageParameters.

For example: choco install server-jre8 --packageParameters '"/InstallationPath:C:\tools\Java /Force /Machine"'.

$packageName = $env:chocolateyPackageName
# The buildNumber should be easier to determine or pass from the nuspec
$buildNumber = "08"
$checksum = "7c46e565a353f4b318760aa7082a435458f9bba7e5b89d9e3fd6c190242093d9"
$downloadHash = "1961070e4c9b4e26a04e7f5a083f551e"

# Discard any -pre/-beta/-testing appended to avoid releasing an unfinished on
$semanticVersion = $env:chocolateyPackageVersion.Split("-")[0]
#8.0.xx to jdk1.8.0_xx
$versionArray = $semanticVersion.Split(".")
$majorVersion = $versionArray[0]
$minorVersion = $versionArray[1]
$updateVersion = $versionArray[2]

$folderVersion = "jdk1.$majorVersion.$($minorVersion)_$updateVersion"

$fileNameBase = "server-jre-$($majorVersion)u$($updateVersion)-windows-x64"
$fileName = "$fileNameBase.tar.gz"

# Oracle got clever and is throwing a hash/sessionID into the path
$url = "$($majorVersion)u$($updateVersion)-b$buildNumber/$($downloadHash)/$fileName"

$osBitness = Get-ProcessorBits
# 32-bit not supported
if ($osBitness -eq 32) {
   Throw "The package $packageName is only available for 64-bit architectures"

$arguments = @{}

# Now we can use the $env:chocolateyPackageParameters inside the Chocolatey package
$packageParameters = $env:chocolateyPackageParameters

# Default value
# uses deprecated Get-BinRoot
#$InstallationPath = Join-Path (Get-BinRoot) "Java/server-jre"
$InstallationPath = Join-Path (Get-ToolsLocation) "Java/server-jre"
$ForceEnvVars = $false
$EnvVariableType = "Machine"

# Now parse the packageParameters using good old regular expression
if ($packageParameters) {
    $match_pattern = "\/(?<option>([a-zA-Z0-9]+)):(?<value>([`"'])?([a-zA-Z0-9- \(\)\s_\\:\.]+)([`"'])?)|\/(?<option>([a-zA-Z]+))"
    $option_name = 'option'
    $value_name = 'value'

    if ($packageParameters -match $match_pattern ){
        $results = $packageParameters | Select-String $match_pattern -AllMatches
        $results.matches | % {
        Throw "Package Parameters were found but were invalid (REGEX Failure)"

    if ($arguments.ContainsKey("InstallationPath")) {
        Write-Host "InstallationPath Argument Found"
        $InstallationPath = $arguments["InstallationPath"]
    if ($arguments.ContainsKey("Force")) {
        Write-Host "Force Argument Found"
        $ForceEnvVars = $true
    if ($arguments.ContainsKey("User")) {
        Write-Host "User Argument Found"
        $EnvVariableType = "User"

} else {
    Write-Debug "No Package Parameters Passed in"

Write-Debug "Installing to $InstallationPath, Params: ForceEnvVars=$ForceEnvVars, EnvVariableType=$EnvVariableType"

# Future state, write install options file to use in uninstall (ie /Machine or /User /InstallationPath)
# This would be easier if installed with Install-ChocolateyZipFile and writing the parameters to $toolsDir aka Invocation.

#Create Temp Folder
$chocTempDir = Join-Path $env:TEMP "chocolatey"
$tempDir = Join-Path $chocTempDir "$packageName"
if ($env:packageVersion -ne $null) {$tempDir = Join-Path $tempDir "$env:packageVersion"; }
if (![System.IO.Directory]::Exists($tempDir)) {[System.IO.Directory]::CreateDirectory($tempDir) | Out-Null}

$tarGzFile = "$tempDir\$fileName"
$tarFile = "$tempDir\$fileNameBase.tar"

if ([System.IO.File]::Exists($tarGzFile)) {
    Write-Debug "Checking if existing file $tarGzFile matches checksum"
    #Check sum of existing file
    Try {
        Get-ChecksumValid -File $tarGzFile -Checksum $checksum -ChecksumType SHA256 -ErrorAction Stop
        Write-Debug "Checksum failed, deleting old file $tarGzFile"
        Remove-Item $tarGzFile

# Added some .NET code to remove the dependency on wget
# If chocolatey >= 0.9.10 could use Get-ChocolateyWebFile with $options
# Currently investigating a bug where it doesn't seem to pass the cookie in properly
#if ($env:ChocolateyVersion -gt "0.9.10") {
#$options =
#  Headers = @{
#    Cookie = " oraclelicense=accept-securebackup-cookie";
#  }
#Write-Debug "Downloading file $tarGzFile using Get-ChocolateyWebFile"
#Get-ChocolateyWebFile -PackageName $packageName -FileFullPath $tarGzFile -Url $url -Checksum $checksum -ChecksumType SHA256 -Options $options
# } # End Get-ChocolateyWebFile
# } else {
# Native .NET download for choco < 0.9.10
Write-Debug "Downloading file $tarGzFile using System.Net.WebClient"
$wc = New-Object System.Net.WebClient
$wc.Headers.Add([System.Net.HttpRequestHeader]::Cookie, "oraclelicense=accept-securebackup-cookie");
$wc.Proxy.Credentials = [System.Net.CredentialCache]::DefaultNetworkCredentials
$wc.DownloadFile($url, $tarGzFile)
Get-ChecksumValid -File $tarGzFile -Checksum $checksum -ChecksumType SHA256
# } # End native .NET block

# Wget dependency block {
#if (![System.IO.File]::Exists($tarGzFile)) {
#  $wget = Join-Path "$env:ChocolateyInstall" '\bin\wget.exe'
#  Write-Debug "wget found at `'$wget`'"
#  #Download file. Must set Cookies to accept license
#  Write-Debug "Downloading file $tarGzFile"
#  .$wget --quiet --no-check-certificate --header "Cookie:; oraclelicense=accept-securebackup-cookie" $url -O $tarGzFile
#  Get-ChecksumValid -File $tarGzFile -Checksum $checksum -ChecksumType SHA256
# } # End wget dependency block

#Extract gz to .tar File
Get-ChocolateyUnzip $tarGzFile $tempDir
#Extract tar to destination
Get-ChocolateyUnzip $tarFile $InstallationPath

$newJavaHome = Join-Path $InstallationPath $folderVersion
$oldJavaHome = Get-EnvironmentVariable "JAVA_HOME" $EnvVariableType

if(($oldJavaHome -eq "") -or $ForceEnvVars) {
   Write-Host "Setting JAVA_HOME to $newJavaHome"
   Install-ChocolateyEnvironmentVariable -variableName "JAVA_HOME" -variableValue $newJavaHome -variableType $EnvVariableType
else {
   Write-Debug "JAVA_HOME already set to $oldJavaHome."

# Need to do an existance check to see if the variable version is already in PATH
Install-ChocolateyPath '%JAVA_HOME%\bin' $EnvVariableType
Get-EnvironmentVariable -Name 'PATH' -Scope $EnvVariableType -PreserveVariables
#Remove-Item -Recurse $tempDir
$packageName = $env:chocolateyPackageName

$versionArray = $env:chocolateyPackageVersion.Split(".")
$folderVersion = "jdk1.$($versionArray[0]).$($versionArray[1])_$($versionArray[2])"
# This will need updated to handle install options file eventually
$InstallationPath = Join-Path (Get-ToolsLocation) "Java/server-jre"
$EnvVariableType = "Machine"

if ([System.IO.Directory]::Exists($InstallationPath)) {
    Write-Debug "Uninstalling $packageName from $InstallationPath"

    $JavaHome = Get-EnvironmentVariable "JAVA_HOME" $EnvVariableType
    if($JavaHome -eq $InstallationPath) {
        Install-ChocolateyEnvironmentVariable -variableName "JAVA_HOME" -variableValue $null -variableType $EnvVariableType
    Remove-Item -Recurse $InstallationPath
else {
    Write-Debug "No $packageName found at $InstallationPath"

# Remove installed variable(s) from PATH
# Loop via @DarwinJS on GitHub as a temp workaround,
#To avoid bad situations - does not use substring matching, regular expressions are "exact" matches
#Removes duplicates of the target removal path, Cleans up double ";", Handles ending "\"

# Expanded path looks like 'C:\tools\Java\server-jre\jdk1.8.0_101\bin'
# Need to escape the backslash in the regex
[regex] $PathsToRemove = "^(%JAVA_HOME%\\bin)"
$environmentPath = Get-EnvironmentVariable -Name 'PATH' -Scope $EnvVariableType -PreserveVariables
[string[]]$newpath = ''
foreach ($path in $environmentPath.split(';'))
  If (($path) -and ($path -notmatch $PathsToRemove))
        [string[]]$newpath += "$path"
        "$path added to `$newpath"
    } else {
        "Path to remove found: $path"
$AssembledNewPath = ($newpath -join(';')).trimend(';')

Install-ChocolateyEnvironmentVariable -variableName 'PATH' -variableValue $AssembledNewPath -variableType $EnvVariableType
"Path with variables"
$newEnvironmentPath = Get-EnvironmentVariable -Name 'PATH' -Scope $EnvVariableType -PreserveVariables
"Path with values instead of variables"

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Server JRE (Java SE Runtime Environment) 8.0.192 5758 Wednesday, October 17, 2018 Approved
Server JRE (Java SE Runtime Environment) 8.0.181 6784 Wednesday, July 18, 2018 Approved
Server JRE (Java SE Runtime Environment) 8.0.172 5307 Wednesday, April 25, 2018 Approved
Server JRE (Java SE Runtime Environment) 8.0.161 4523 Wednesday, January 24, 2018 Approved
Server JRE (Java SE Runtime Environment) 8.0.152 4890 Friday, October 20, 2017 Approved
Server JRE (Java SE Runtime Environment) 8.0.144 2057 Sunday, September 24, 2017 Approved
Server JRE (Java SE Runtime Environment) 7799 Monday, May 1, 2017 Approved

This package has no dependencies.

Discussion for the Server JRE (Java SE Runtime Environment) Package

Ground Rules:

  • This discussion is only about Server JRE (Java SE Runtime Environment) and the Server JRE (Java SE Runtime Environment) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Server JRE (Java SE Runtime Environment), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus