JDK-7114486 : Removing jre 6ux makes IE to use the old 7u2 plug-in by default
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u30
  • Priority: P1
  • Status: Closed
  • Resolution: Fixed
  • OS: windows
  • CPU: generic
  • Submitted: 2011-11-22
  • Updated: 2013-10-23
  • Resolved: 2012-01-17
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 7 JDK 8
7u4Fixed 8 b22Fixed
Related Reports
Relates :  
JDK-7045457 - uninstall of JRE 7 with JRE 6 on the machine left 10.0.0 deployment registry key behind
Description
System has both;
- latest jre 6u29 installed
- jre 7u2 installed   

If uninstall jre 6u29, the IE will use the old  java plug-in (of 7u2) by default

*** Test configurations:
- x86 XP, win7
- IE 8

*** Steps to reproduce:
0) Make sure no jre or javafx runtime on the system
1) Install jre 6u29
2) Install jre 7u2 (latest b13)
3) Use IE to invoke any java applet to ensure the 7u2 new java plug-in being used
4) Uninstall jre 6u29 
5) Use IE to invoke any java applet.

If you see the old/deprecated  7u2 java plug-in is used, then the issue is reproducible

*** Warning from the java console
Warning: using first-generation plugin.
This plugin is deprecated and will be removed in the next major
release of Java.  Please report any technical difficulties
with the next-generation plugin at http://bugs.sun.comJava Plug-in 1.7.0_02
Using JRE version 1.7.0_02-b13 Java HotSpot(TM) Client VM
User home directory = C:\Users\uadmin
----------------------------------------------------
Comments
Verified the original report on different scenarios: A) Install 6u29, jre 8-b112, uninstall 6u29 As old plug-in is no longer part of jre 8, so the report problem does not apply to jre 8 B) Install 6u29, jre 7u45, uninstall 6u29 Applet loaded using the new plug-in of 7u45 Fix verified
23-10-2013
EVALUATION Attempt to fixing it by loading msvcr100.dll at the beginning of the ssv functions which are being called by the 6ux installer during uninstallation of JRE. But that approach didn't work. For now, the fix is statically linking ssv dlls with MS runtime library.
11-01-2012
EVALUATION This is reproducible only on machines which don't have VS2010 installed. The problem is due to during uninstall of 6ux, it calls a function in a 7ux dll which has dependency on msvcr100.dll. The following entries from a process monitor log collected by SQE confirms the above: 8:19:41.3318241 PM MsiExec.exe 1916 CreateFileMapping C:\Program Files\Java\jre7\bin\jp2ssv.dll SUCCESS SyncType: SyncTypeOther 8:19:41.3319512 PM MsiExec.exe 1916 Load Image C:\Program Files\Java\jre7\bin\jp2ssv.dll SUCCESS Image Base: 0x743c0000, Image Size: 0x10000 8:19:41.3319663 PM MsiExec.exe 1916 CloseFile C:\Program Files\Java\jre7\bin\jp2ssv.dll SUCCESS 8:19:41.3321613 PM MsiExec.exe 1916 CreateFile C:\Windows\System32\MSVCR100.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a 8:19:41.3322926 PM MsiExec.exe 1916 CreateFile C:\Windows\System32\MSVCR100.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a 8:19:41.3325016 PM MsiExec.exe 1916 CreateFile C:\Windows\system\MSVCR100.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a 8:19:41.3326357 PM MsiExec.exe 1916 CreateFile C:\Windows\MSVCR100.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a 8:19:41.3326572 PM MsiExec.exe 1916 FileSystemControl C:\Windows\System32 SUCCESS Control: FSCTL_IS_VOLUME_MOUNTED 8:19:41.3327737 PM MsiExec.exe 1916 CreateFile C:\Windows\System32\MSVCR100.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a 8:19:41.3329240 PM MsiExec.exe 1916 CreateFile C:\Program Files\MKS Toolkit\bin\MSVCR100.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a 8:19:41.3330958 PM MsiExec.exe 1916 CreateFile C:\Program Files\MKS Toolkit\bin\X11\MSVCR100.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a 8:19:41.3332771 PM MsiExec.exe 1916 CreateFile C:\Program Files\MKS Toolkit\mksnt\MSVCR100.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a 8:19:41.3334428 PM MsiExec.exe 1916 CreateFile C:\Windows\System32\MSVCR100.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a 8:19:41.3335833 PM MsiExec.exe 1916 CreateFile C:\Windows\MSVCR100.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a 8:19:41.3337425 PM MsiExec.exe 1916 CreateFile C:\Windows\System32\wbem\MSVCR100.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a 8:19:41.3338640 PM MsiExec.exe 1916 CreateFile C:\Windows\System32\WindowsPowerShell\v1.0\MSVCR100.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
22-12-2011
EVALUATION We can't change the uninstaller for all old releases. Needs to fixed in the deployment stack in jdk7 updates
15-12-2011
EVALUATION this should be fixed by: 7045457: uninstall of JRE 7 with JRE 6 on the machine left 10.0.0 deployment registry key behind that's the main CR we used to backporting fx-aware installer changes to 6uX. I verified that the bug cannot be reproduced using eng. build from sustaining with the fix for 7045457. we should make sure SQE tests this case too when 7045457 is being verified.
01-12-2011
EVALUATION This is a JDK6 uninstaller bug, so assigning to Mukesh's team.
01-12-2011
EVALUATION Removing the SR for 7u2. This is an issue with the JDK6 uninstaller, not JDK7. It's likely that the JDK6 uninstaller does not know how to register the new deployment that common-deployment team created in 7u2.
01-12-2011
WORK AROUND Uninstall/reinstall 7u2.
01-12-2011