Details
-
Bug
-
Resolution: Won't Fix
-
P3
-
6u101
-
Windows 8 Enterprise with x64 bundles, 6u95-b11 --> 6u101-b13
Windows Server 2003 Enterprise SP2 with ia32 bundles, 6u95-b12 --> 6u101-b13
-
itanium
-
windows_8
Description
Intel reported the following issue with upgrading from 6u95 to 6u101:
1) The following commands reproduce the behavior during JDK upgrade:
Windows 8 Enterprise with x64 bundles
jdk-6u95-fcs-bin-b11-windows-i586-16_mar_2015.exe /L C:\jdk-6u95-b12_i586.log /s ADDLOCAL="ToolsFeature,SourceFeature"
jdk-6u101-fcs-bin-b13-windows-i586-26_may_2015.exe /L C:\jdk-6u101-b13_i586.log /s ADDLOCAL="ToolsFeature,SourceFeature"
Windows Server 2003 Enterprise SP2 with ia32 bundles
jdk-6u95-fcs-bin-b12-windows-x64-09_apr_2015.exe /L C:\jdk-6u95-b12_x64.log /s ADDLOCAL="ToolsFeature,SourceFeature"
jdk-6u101-fcs-bin-b13-windows-x64-26_may_2015.exe /L C:\jdk-6u101-b13_x64.log /s ADDLOCAL="ToolsFeature,SourceFeature"
The following registry field was not updated to 6u101 JDK after the installation:
HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit\1.6\JavaHome C:\Program Files\Java\jdk1.6.0_95
2) Please note that I do not have any 6u101 ia32 or x64 JRE bundles so the following commands were used to reproduce the issue with JRE registry:
Windows Server 2003 Enterprise SP2 with ia32 bundles
jre-6u45-windows-i586.exe /L C:\jre-6u45_i586.log /s STATIC=1
jdk-6u101-fcs-bin-b13-windows-i586-26_may_2015.exe /L C:\jdk-6u101-b13_i586.log /s ADDLOCAL="ToolsFeature,SourceFeature,PublicjreFeature"
The following registry fields were not updated to 6u101 JRE after the installation:
HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\1.6\JavaHome C:\Program Files\Java\jre1.6.0_45
HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\1.6\RuntimeLib C:\Program Files\Java\jre1.6.0_45\bin\server\jvm.dll
I could also see the same issue with 6u95-b12 and 6u101-b13 ia64 JRE bundles:
Windows Server 2008 R2 for Itanium with ia64 bundles
jre-6u95-windows-ia64.exe /s STATIC=1
jre-6u101-windows-ia64.exe /s [STATIC=1]
1) The following commands reproduce the behavior during JDK upgrade:
Windows 8 Enterprise with x64 bundles
jdk-6u95-fcs-bin-b11-windows-i586-16_mar_2015.exe /L C:\jdk-6u95-b12_i586.log /s ADDLOCAL="ToolsFeature,SourceFeature"
jdk-6u101-fcs-bin-b13-windows-i586-26_may_2015.exe /L C:\jdk-6u101-b13_i586.log /s ADDLOCAL="ToolsFeature,SourceFeature"
Windows Server 2003 Enterprise SP2 with ia32 bundles
jdk-6u95-fcs-bin-b12-windows-x64-09_apr_2015.exe /L C:\jdk-6u95-b12_x64.log /s ADDLOCAL="ToolsFeature,SourceFeature"
jdk-6u101-fcs-bin-b13-windows-x64-26_may_2015.exe /L C:\jdk-6u101-b13_x64.log /s ADDLOCAL="ToolsFeature,SourceFeature"
The following registry field was not updated to 6u101 JDK after the installation:
HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit\1.6\JavaHome C:\Program Files\Java\jdk1.6.0_95
2) Please note that I do not have any 6u101 ia32 or x64 JRE bundles so the following commands were used to reproduce the issue with JRE registry:
Windows Server 2003 Enterprise SP2 with ia32 bundles
jre-6u45-windows-i586.exe /L C:\jre-6u45_i586.log /s STATIC=1
jdk-6u101-fcs-bin-b13-windows-i586-26_may_2015.exe /L C:\jdk-6u101-b13_i586.log /s ADDLOCAL="ToolsFeature,SourceFeature,PublicjreFeature"
The following registry fields were not updated to 6u101 JRE after the installation:
HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\1.6\JavaHome C:\Program Files\Java\jre1.6.0_45
HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\1.6\RuntimeLib C:\Program Files\Java\jre1.6.0_45\bin\server\jvm.dll
I could also see the same issue with 6u95-b12 and 6u101-b13 ia64 JRE bundles:
Windows Server 2008 R2 for Itanium with ia64 bundles
jre-6u95-windows-ia64.exe /s STATIC=1
jre-6u101-windows-ia64.exe /s [STATIC=1]