Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8080735

silent install parameters causes jre pre-installed jre 64-bit version to uninst

XMLWordPrintable

    • x86
    • windows_8

      FULL PRODUCT VERSION :


      ADDITIONAL OS VERSION INFORMATION :
      Windows 8 x64 Enterprise All patches applied.

      EXTRA RELEVANT SYSTEM CONFIGURATION :
      240GB SSD C drive
      i7 CPU
      16GB Ram

      A DESCRIPTION OF THE PROBLEM :
      Using the following parameters for JDK 8u40 works perfectly.

      start /w jdk-8u40-windows-x64.exe INSTALL_SILENT=Enable /L C:\Java\jdk.log ADDLOCAL="ToolsFeature,SourceFeature" "INSTALLDIR=c:\Java\Jdk8" STATIC=0

      It installs without touching the 8u40/8u45 jre 32/64 bit installations that is present on the machine.

      Now with the latest 8u45 theres something going on... Observe these two install commands are identical except the filenames are different. This one below dows not behave as expected.

      start /w jdk-8u45-windows-x64.exe INSTALL_SILENT=Enable /L C:\Java\jdk.log ADDLOCAL="ToolsFeature,SourceFeature" "INSTALLDIR=c:\Java\Jdk8" STATIC=0

      This will cause the 64-bit jre to be uninstalled in the process.



      REGRESSION. Last worked in version 8u40

      ADDITIONAL REGRESSION INFORMATION:
      java -version
      java version "1.8.0_45"
      Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
      Java HotSpot(TM) Client VM (build 25.45-b02, mixed mode, sharing)

      STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
      install jre 8u45 64-bit
      install jdk 8u45 with the silent install parameters above.

      jre 64-bit will get uninstalled.

      EXPECTED VERSUS ACTUAL BEHAVIOR :
      EXPECTED -
      jre 64-bit and jdk 64-bit are installed.
      ACTUAL -
      jre 64-bit is uninstalled.

      REPRODUCIBILITY :
      This bug can be reproduced always.

            pardesha Pardeep Sharma
            webbuggrp Webbug Group
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: