United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: 6630380 files locked by DT causes MSI registry keys to be deleted during install
6630380 : files locked by DT causes MSI registry keys to be deleted during install

Details
Type:
Bug
Submit Date:
2007-11-15
Status:
Closed
Updated Date:
2010-09-17
Project Name:
JDK
Resolved Date:
2008-01-25
Component:
install
OS:
windows_xp,windows
Sub-Component:
install
CPU:
x86
Priority:
P1
Resolution:
Fixed
Affected Versions:
6u5,6u10
Fixed Versions:
6u10

Related Reports
Backport:
JDK-2199137 - files locked by DT causes MSI registry keys to be deleted during install
Duplicate:
JDK-6617684 - Uninstall of 6u6 patch in place left registry entry
Relates:
JDK-6629444 - 6u10b07 installer causes 1722 when installing on top of 6uN older builds
Relates:
JDK-6634518 - Detect / prevent install 6u10 on top of 6u10
Relates:
JDK-6533331 - Java Installer fails to update/register CurrentVersion and BrowserJavaVersion correctly

Sub Tasks

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
2007-11-16 
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 ] ###@###.###
2007-11-15


Hardware and Software, Engineered to Work Together