The setup logs indicated that both version were successfully installed. It installs the 32-bit version first, followed by the 64-bit version. After running the setup, only the 64-bit version was present. I encountered this behavior while testing a script I use for installing Java during MDT deployments. When you use this option with 8u121, however, it removes both 32 and 64-bit versions, including any 8u121 JREs that are installed. Install 64-bit Java, and it will remove installed 64-bit versions. Install 32-bit Java, and it will remove installed 32-bit versions. Normally, the REMOVOLDERJRES option only removes installed JRES that match the architecture for the version you’re installing. The 8u121 setup behavior has changed, however, which can cause issues if you install both the 32 and 64-bit versions on your systems. Doing so ensures that you don’t have any older unpatched versions on your system. If you set REMOVEOLDERJRES to 1, the setup will find and remove any existing versions of the JRE that are installed. Oracle released the 8u121 update for Java SE last week with a little surprise for anyone who installs/updates the Java Runtime Environment (JRE) using the MSI file with the REMOVEOLDERJRES option.
0 kommentar(er)
