Jdk 8u161 Windows I586

Posted on

Oracle has released “Java Platform, Standard Edition 8 Update 161” also known as ‘Java Runtime Environment Version 8.0 Update 161’.

Java jre-8u161-windows-i586

License; Java SE 8 Readme; NB 8.2 3rd Party Readme; Installation Instructions; Java SE Release Notes; NetBeans Release Notes; Java SE Development Kit 8u111 和 NetBeans IDE 8.2 复合软件包下载 (简体中文). Jdk-6u45-windows-i586.exe - Google Drive.

This release contains fixes for security vulnerabilities.

First of all download and run either jre-8u161-windows-i586.exe for Windows 7 / 8 / 8.1 / 10 / XP 32-bit or jre-8u161-windows-x64.exe for Windows 7 / 8 / 8.1 / 10 / XP 64-bit. If you use 32-bit and 64-bit browsers interchangeably, you will need to install both 32-bit and 64-bit Java in order to have the Java plug-in for both browsers. These offline installers are available in the Java SE Runtime Environment 8 Downloads section of Oracle’s Java website.

When the License Agreement screen pops up, look in the “c:Documents and Settings<username>Local SettingsApplication DataOracleJavajre1.8.0_161 directory” when you’re using Windows XP or “C:Users<username>AppDataLocalLowOracleJavajre1.8.0_161” when your’re using Windows 7 / 8 / 8.1 / 10.

For the x64 version look in the “C:Users<username>AppDataLocalLowOracleJavajre1.8.0_161_x64” directory. In that directory you will find the ‘jre1.8.0_161.msi‘. The jre1.8.0_161 msi file is the one we can use to deploy “Java Runtime Environment Version 8.0 Update 161” by using MSI technology.

Start up the AdminStudio Tuner and create a response transform file. It’s as simple as that if you want to do a default deployment. For an advanced deployment you can further tweak you J2RE configuration two ways:

  • by changing the ‘Setup Properties’
  • by changing registry settings
Download

The result is the same. You can change some basic ‘Setup Properties’ in the Tuner:

  • AUTOUPDATECHECK – Java Update mechanism – on {1} or off {0}
  • EULA – popup the EULA when you first start a Java applet – on {1} or off {0}
  • IEXPLORER – indicates that the Plug-in should be registered with the Internet Explorer browser – on {1} or off {0}
  • JAVAUPDATE – indicates that the Java Update feature should be disabled (the Update tab in the Java Plug-in Control Panel will not appear) – on {1} or off {0}However, it seems that using the property doesn’t work anymore and that you have to set this registry key additionally:[HKEY_LOCAL_MACHINESOFTWAREJavaSoftJava UpdatePolicy]“EnableAutoUpdateCheck”=dword:00000000
  • MOZILLA – indicates that the Plug-in should be registered with Mozilla 1.1 and later browsers – on {1} or off {0}
  • WEB_JAVA – if used, disables any Java application from running in the browser. WEB_JAVA=1, the default, enables Java applications in the browser. This field is available as of the 7u10 release. For more information, see Setting the Security Level of the Java Client.
  • WEB_JAVA_SECURITY_LEVEL, if used, sets the security level of unsigned Java apps running in a browser. The possible values for this field are V (very high), H (high), M (medium, the default) or L (low). This field is available as of the 7u10 release. For more information, see Setting the Security Level of the Java Client.

… but you can also collect the JRE’s registry settings to tweak the JRE a little more.

Launch the “Java Control Panel” (available in c:Program FilesJavajre8binjavacpl.exe). Most settings you will change by using this utility will then be stored in the registry in [HKEY_LOCAL_MACHINESOFTWAREJavaSoft]. Some examples:

  • Click on the “Update” tab. If you uncheck the “Check for Update Automatically” you will shutdown the Java Update mechanism. This may be wise, because we want to deploy newer versions by using ZENworks and not automatically by using the Java Update mechanism.
  • If you want to disable the ‘Update’ tab, then use this registry setting to enable (00000001) or disable it (00000000):[HKEY_LOCAL_MACHINESOFTWAREJavaSoftJava UpdatePolicy]“EnableJavaUpdate”=dword:00000000

Some settings however are stored somewhere else. Some examples:

  • Click on the “Advanced” tab. If you open up the “Miscellaneous” node by clicking on the + sign, you can check or uncheck “Place Java icon in system tray”. Which just does what is says. Now it has become more difficult for users to fiddle around with the J2RE configuration. This setting is stored in:C:Documents and Settings%USERNAME%AppDataSunJavaDeploymentdeployment.properties.as: “deployment.system.tray.icon=true”
  • Click on the “General” tab. Click on ‘Network Settings’. The settings you configure are also stored in the deployment.properties file.This ‘deployment.properties’ file is used for storing and retrieving deployment configuration properties in the Java Control Panel. They are also used for customizing runtime behavior for both Java Plug-in and Java Web Start. There is always a User-Level deployment.properties file. Its location, which is non-configurable, is described here. There may also be an (optional) System-Level deployment.properties file. If it exists, its location is determined by a System Administrator through the deployment.config file as described here.

You can add a Custom Action (1122) to your Transform file, where you run this command:

cmd.exe /C rmdir “%PROGRAMDATA%MicrosoftWindowsStart MenuProgramsJava” /S

to remove the Start Menu shortcuts. In the InstallUIExecuteSequence table you set the Sequence ID of this Custom Action to ‘3183’. Which is then between the InstallJava custom action (3181), which apparently create these shortcuts, and InstallFinalize (3185).

This page describes options for installing, configuring, and creating a log file for the Windows Java Runtime Environment.

This page contains the following topics:

See 'JDK 8 and JRE 8 Installation Start Here' for general information about installing JDK 8 and JRE 8.

Introduction

This page describes options for installation of the Java SE Runtime Environment (JRE) on Windows 32-bit platform. It is intended for:

  • System administrators deploying the JRE with Java Plug-in and Java Web Start technologies on multiple PCs in their Intranet without user interaction.

  • Vendors having products requiring the JRE. The JRE can be silently (non-interactively from the command line) installed with their product.

JRE installers are built using Microsoft Window Installer (MSI) 2.0 technology. MSI contains built-in support for silent installations. This topic explains how to manually install the JRE using the .exe file that runs the MSI.

Jdk-8u161-windows-i586.exe

Command-Line Installation

This section describes the command-line options for the JRE Windows Offline Installer. Run the installer as follows:

  • jre refers to the JRE Windows Offline Installer base file name (for example, jre-8u05-windows-i586.exe).

  • Free reggae drum beats. INSTALLCFG=configuration_file_path specifies the path of the installer configuration file. See 'Installing With a Configuration File' for more information.

  • options are options with specified values separated by spaces. Use the same options as listed in Table 20-1, 'Configuration File Options'. In addition, you may use the option /s for the JRE Windows Offline Installer to perform a silent installation.

Static Installation

If you perform a static installation of the JRE (by specifying the command-line or configuration file option STATIC=1), then the Java Auto Update feature will leave that JRE installed during a Java update. A later version of the same JRE family will be installed in a separate directory. This mode ensures that vendors, who require a specific version of the JRE for their product, can be certain that the JRE will not be overwritten by a newer version.

The default installation directory of a static JRE is C:Program Files (x86)Javajren (for 32-bit versions) or C:Program FilesJavajren (for 64-bit versions), where n is the full Java SE release and update number (for example, n = 1.8.0_20 for release 8 update 20). Office 2010 free download with crack full version filehippo.

Java Jre-8u161-windows-i586

Creating a Log File

Use a log file to verify that an installation succeeded. To create a log file describing the installation, append /L C:pathsetup.log to the install command and scroll to the end of the log file to verify.

The following is an example of creating a log file:

Jdk-8u161-nb-8_2-windows-i586

This example causes the log to be written to the pathsetup.log file.