Software Deployment Question

Oracle java 8 update 111 msi extracting

10/20/2016 13142 views
For wsus package publisher i need msi package of java. Last java update is 111.
I downloaded exe package, started process monitor and looked at the installing process. Found out, that this process create jre1.8.0_11164 on %appdata%LocalLow\Oracle\Java\jre1.8.0_111_x64. ok
But when i start this msi, i catch this errorgfdwye.png
What am i doing wrong?
Answer Summary:
1 Comment   [ + ] Show comment


  • Hi mykolaq,

    I solved that this morning by launching it "As Admin".

    Create a cmd calling the msi. Save. Right click, run as Administrator.


Answer Chosen by the Author

I ran into the same issue and found this article helpfull.


Have fun,
Answered 10/20/2016 by: 786_ak
Third Degree Green Belt

  • i'm so inattentive. Thanks

All Answers

Need more details.
  • What command are you using?
  • What security context, SYSTEM or user account?
  • Do you turn on logging for the msi install? (l*vx)

I've seen in other Java packages that the MSI and does not like handling PROPERTIES passed to the msi, thus you need to use the config.xml -  I now think this is the better option rather than using PROPERTIES. If you look around on itninja, you will find other posts that will help.

Answered 10/20/2016 by: rileyz
Red Belt

  • What comment for what? i started exe without any parameters, msi too. Security - user (vs admin rights). I didnt turn msi logging

Remember that all the EXE does is pass parameters to MSIExec.EXE so just use the MSI to begin with. Remember also that the MSI isn't a "proper" MSI, since it's just a wrapper for Oracle's installer.

>I didnt turn msi logging
So how on Earth do you expect to find out which Action is causing the problem? Divine intervention?

Answered 10/20/2016 by: VBScab
Red Belt

  • Fairly, u're right.
Do you have to have 64-bit? I extracted the .msi for the 32-bit version yesterday without error. 
Answered 10/20/2016 by: rockhead44
Red Belt

Log of msi install . Parameters
 msiexec /i jre1.8.0_11164.msi /qb /L*V c:\javalog.txt
Answered 10/20/2016 by: mykolaq
White Belt

Hi mykolaq,  

I solved that this morning by launching it "As Admin".

Create a cmd calling the msi.  Save.  Right click, run as Administrator.

Answered 10/20/2016 by: mathieu.bourgon
White Belt

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ