JDK-7047893 : REGRESSION: JDK 7 installation fail with Error 2229 with UAC on Windows German Vista
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 7
  • Priority: P2
  • Status: Closed
  • Resolution: Cannot Reproduce
  • OS: windows_vista
  • CPU: x86
  • Submitted: 2011-05-24
  • Updated: 2011-11-08
  • Resolved: 2011-11-08
Related Reports
Relates :  
Relates :  
Description
Problem to install JDK 7 latest build with UAC on on Windows Vista.


1.) Step to reproduce -

     . click the latest JDK 7 bundles (jre-7-ea-bin-b141-windows-i586-05_may_2011.exe)
     . then came the security warning from Vista. 
     . Accepted it and see the welcome dialog in Germain.
     . click on the install button, 
     . the dialog was removed, 
     . then saw a short preparing wait messagebox,
     . then come the first error box -> click ok, 
     . then come the second identical box -> click ok
     . setup is terminated.

Worked fine with b134, but not work since b141

 

2.) Use the a Vista SP2 with the latest pack level. UAC is enabled. The local is German.

Comments
EVALUATION I am wondering if the jre1031.MST transform from b134 is cached and causing issues when trying to install b141. MSI version is 7.0.0 for b134 and b141, so there is no version difference for Windows Installer to use http://www.packagedeploy.com/forum/windows-msi/error-2229-when-initiating-minor-upgrade-when-upgrading-aninstallation-based-transform-251/
13-07-2011

WORK AROUND Use REINSTALL_NO_PROMPT=1 parameter to work aroudn the problem.
03-06-2011

EVALUATION I'm unable to reproduce running b141 with /lang=1031 (which applies the German transform) on winXP sp3.
25-05-2011

EVALUATION I have a list of questions: -Is there any way I can connect to this machine? -Is there more than one single machine experiencing by one customer this problem? -Does that machine already have a previous build of Java 7? Run java -version to determine. -They say b134 worked fine. What if they try running b134 now? Does it work? My initial thoughts are that this is a single machine corruption issue, and not a P2 affecting lots of people. MSI tends to do this now and then.
25-05-2011