Downloads of v 8.0.212:


Last Update:


Package Maintainer(s):

Software Author(s):

  • Oracle


java server runtime environment jre admin

Server JRE (Java SE Runtime Environment)



Downloads of v 8.0.212:



Software Author(s):

  • Oracle

Server JRE (Java SE Runtime Environment)

Some Checks Have Failed or Are Not Yet Complete

1 Test Passing and 1 Failing Test

Validation Testing Passed

Verification Testing Failed


This package was rejected on 6/25/2019. The reviewer chocolatey-ops has listed the following reason(s):

rgra (maintainer) on 21 May 2019 12:53:51 +00:00:

User 'rgra' (maintainer) submitted package.

chocolatey-ops (reviewer) on 21 May 2019 13:27:24 +00:00:

server-jre8 has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.


Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • The package script downloads a file outside of using built-in helpers. Scripts should use the built-in helpers to download files. More...

chocolatey-ops (reviewer) on 21 May 2019 13:48:58 +00:00:

server-jre8 has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

chocolatey-ops (reviewer) on 10 Jun 2019 13:51:22 +00:00:

We've found server-jre8 v8.0.212 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:
* Log in to the site and respond to the review comments.
* Resubmit fixes for this version.
* If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

chocolatey-ops (reviewer) on 25 Jun 2019 13:54:16 +00:00:

Unfortunately there has not been progress to move server-jre8 v8.0.212 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.

Status Change - Changed status of package from 'submitted' to 'rejected'.


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.


The Oracle JDK License has changed for releases starting April 16, 2019. Please only use this package if you have purchased a valid license for your environment.

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 = "10"
$checksum = "de4c50344ee37816ac4af90638622ed307c903e4ae82b635ba3b742269fb747f"
$downloadHash = "59066701cf1a433da9770636fbc4c9aa"

# 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"

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 5632 Wednesday, October 17, 2018 Approved
Server JRE (Java SE Runtime Environment) 8.0.181 6678 Wednesday, July 18, 2018 Approved
Server JRE (Java SE Runtime Environment) 8.0.172 5193 Wednesday, April 25, 2018 Approved
Server JRE (Java SE Runtime Environment) 8.0.161 4398 Wednesday, January 24, 2018 Approved
Server JRE (Java SE Runtime Environment) 8.0.152 4739 Friday, October 20, 2017 Approved
Server JRE (Java SE Runtime Environment) 8.0.144 1907 Sunday, September 24, 2017 Approved
Server JRE (Java SE Runtime Environment) 6077 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