5 Replies Latest reply on Dec 1, 2017 3:48 PM by jasweat

    Java updates - is it 3 packages to maintain?  x86, x64, x86 for x64?

    kjstech

      Hello,

       

      Curious how you maintain Java updates.

       

      Do you publish, use the package boot manager to uninstall old versions and maintain 3 different Java applications?

       

      Like right now I'm going through and publishing these:

      Java Runtime Environment 8u152 (x86 for x64) (Upgrade)

      Java Runtime Environment 8u152 (x64) (Upgrade)

      Java Runtime Environment 8u152 (x86) (Upgrade)

       

      So is that correct?  Every time there is a java update you have to maintain 3 packages?  Can Oracle get a clue?

        • Re: Java updates - is it 3 packages to maintain?  x86, x64, x86 for x64?
          kjstech

          I guess it doesn't matter.  I approved them, I am offered Java Runtime Environment 8u152 (x86 for x64) (Upgrade) when I run Windows update on my Windows 10 1703 machine.  However after preparing and getting to 100% it throws Error 0x80070643.  All other updates install fine.

           

          I can't figure this one out.

            • Re: Java updates - is it 3 packages to maintain?  x86, x64, x86 for x64?
              kjstech

              I turned on verbose msi logging and in my appdata %temp% directory an msi563d4.LOG was generated containing this:

              === Verbose logging started: 11/29/2017  13:15:25  Build type: SHIP UNICODE 5.00.10011.00  Calling process: C:\WINDOWS\SoftwareDistribution\Download\Install\packageboot.exe ===

              MSI (c) (40:B0) [13:15:25:248]: Resetting cached policy values

              MSI (c) (40:B0) [13:15:25:248]: Machine policy value 'Debug' is 0

              MSI (c) (40:B0) [13:15:25:248]: ******* RunEngine:

                         ******* Product: {26A24AE4-039D-4CA4-87B4-2F83218000F0}

                         ******* Action:

                         ******* CommandLine: **********

              MSI (c) (40:B0) [13:15:25:248]: Client-side and UI is none or basic: Running entire install on the server.

              MSI (c) (40:B0) [13:15:25:248]: Grabbed execution mutex.

              MSI (c) (40:B0) [13:15:25:248]: Cloaking enabled.

              MSI (c) (40:B0) [13:15:25:248]: Attempting to enable all disabled privileges before calling Install on Server

              MSI (c) (40:B0) [13:15:25:248]: Incrementing counter to disable shutdown. Counter after increment: 0

              MSI (s) (04:20) [13:15:25:248]: Running installation inside multi-package transaction {26A24AE4-039D-4CA4-87B4-2F83218000F0}

              MSI (s) (04:20) [13:15:25:248]: Grabbed execution mutex.

              MSI (s) (04:40) [13:15:25:264]: Resetting cached policy values

              MSI (s) (04:40) [13:15:25:264]: Machine policy value 'Debug' is 0

              MSI (s) (04:40) [13:15:25:264]: ******* RunEngine:

                         ******* Product: {26A24AE4-039D-4CA4-87B4-2F83218000F0}

                         ******* Action:

                         ******* CommandLine: **********

              MSI (s) (04:40) [13:15:25:264]: Machine policy value 'DisableUserInstalls' is 0

              MSI (s) (04:40) [13:15:25:264]: MainEngineThread is returning 1605

              MSI (s) (04:20) [13:15:25:264]: User policy value 'DisableRollback' is 0

              MSI (s) (04:20) [13:15:25:264]: Machine policy value 'DisableRollback' is 0

              MSI (s) (04:20) [13:15:25:264]: Incrementing counter to disable shutdown. Counter after increment: 0

              MSI (s) (04:20) [13:15:25:264]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

              MSI (s) (04:20) [13:15:25:264]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

              MSI (s) (04:20) [13:15:25:264]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

              MSI (c) (40:B0) [13:15:25:264]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

              MSI (c) (40:B0) [13:15:25:264]: MainEngineThread is returning 1605

              === Verbose logging stopped: 11/29/2017  13:15:25 ===

               

               

              On my Windows 10 1709 laptop I see both the 8u152 (x64) upgrade AND the 8u152 (x86 for x64) upgrade.  Both fail with the same error code 0x80070643.

               

              Any idea's?

                • Re: Java updates - is it 3 packages to maintain?  x86, x64, x86 for x64?
                  kjstech

                  Ok I updated Patch Manager from 2.1.3 to 2.1.5 and now it works great.

                   

                  It seemed to be a bug that was fixed in 2.1.5 about continuing on error (where pacakgeboot would get an msi 1605 code on the GUID's for java versions not existing on the machine).

                   

                  We're all good.  So back to the original question, do most of you approve all three versions of Java 8 to cover your bases?

                   

                  Java Runtime Environment 8u152 (x86 for x64) (Upgrade)

                  Java Runtime Environment 8u152 (x64) (Upgrade)

                  Java Runtime Environment 8u152 (x86) (Upgrade)

                  1 of 1 people found this helpful