JDK-6630380 : files locked by DT causes MSI registry keys to be deleted during install
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 6u5,6u10
  • Priority: P1
  • Status: Closed
  • Resolution: Fixed
  • OS: windows,windows_xp
  • CPU: x86
  • Submitted: 2007-11-15
  • Updated: 2010-09-17
  • Resolved: 2008-01-25
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7
6u10 b08Fixed 7Fixed
Related Reports
Duplicate :  
Relates :  
Relates :  
Relates :  
Description
install 6u10
either with Deployment Toolkit online installer (http://web-east.east/www/tests/getjava/wat/install1.html)
or with deployment toolkit files locked (http://web-east.east/www/tests/getjava/6529645/f1.html)

after [HKLM\SOFTWARE\JavaSoft\Java Runtime Environment\1.6] JavaHome is created, and then during MSIInstallJRE in regutils.dll, 
[HKLM\SOFTWARE\JavaSoft\Java Runtime Environment\1.6.0_10\MSI] is deleted, and [HKLM\SOFTWARE\JavaSoft\Java Runtime Environment\1.6.0_10\MSI] JAVAREBOOT is created.

Patch in Place then has a difficult time detecting that 6u10 Consumer is already installed.

Comments
SUGGESTED FIX Removed SetReboot() and Reboot.rgs Log that there is a locked file until reboot in java_install_reg.log webrev: http://sa.sfbay.sun.com/projects/deployment_data/6u10/6630380.0 testcase: http://oklahoma.east/deployment/www/tests/1.6.0_10/6630380/test.txt
16-11-2007

EVALUATION During the install of 6u10, after [HKLM\SOFTWARE\JavaSoft\Java Runtime Environment\1.6] JavaHome was created, and then during MSIInstallJRE in regutils.dll, [HKLM\SOFTWARE\JavaSoft\Java Runtime Environment\1.6.0_10\MSI] was deleted, and [HKLM\SOFTWARE\JavaSoft\Java Runtime Environment\1.6.0_10\MSI] JAVAREBOOT was created. I was able to reproduce on my development system and capture with Process Monitor. This was during the install of 6u10 b07. I have 6u1, 6u2, and 6u3 installed on my development system. When installing 6u12 , [HKLM\SOFTWARE\JavaSoft\Java Runtime Environment] Java6FamilyVersion == "1.6.0_10", but no [HKLM\SOFTWARE\JavaSoft\Java Runtime Environment\1.6.0_10\MSI] MODE, the install logs "Couldn't read MODE for Java6FamilyVersion=1.6.0_10" to jusched.log and decides that the consumer version is not properly installed, and continues like it is the first consumer install. You could end up with 6u10 and 6u12 installs to C:\Program Files\Java\jre6\ and have problems uninstalling. *** (#1 of 1): [ UNSAVED ] ###@###.###
15-11-2007