2 Replies Latest reply on Oct 26, 2018 9:34 PM by brian.taylor.support

    Java 192 < 191

    rbabcock Apprentice

      If I scan a machine that has Java 8 version 192 installed, it gets flagged as needing version 191 because < 8.0.1910.12.


      strfinfo javaw.exe returns "ProductVersion=8.0.1920.12"


      but getvers javaw.exe returns "javaw.exe Version: 8,0,192,12"


      Getvers is an old (2006) program; I don't know where I got it.  The point is, two programs here return 192 or 1920 which suggests the version info might be in more than one place in the file and the two places might not agree.


      Ivanti Patch for Windows® Servers Standard 9.3.0 Build 4510

      Definition version is

        • 1. Re: Java 192 < 191
          brian.taylor.support SupportEmployee



          Thank you for posting your question here.  I think I see the discrepancy on this one - for javaw.exe, there is a listed File version and a separate Product Version.  For 8u191, they both list 8.0.1910.12, but for 8u192, the File version is while the Product version is 8.0.1920.12.  So, it looks like Oracle didn't keep that consistent for 8u192.  Let me get this info up to our content team for further evaluation.  I'll update this thread when I have more information.




          • 2. Re: Java 192 < 191
            brian.taylor.support SupportEmployee

            Quick update on this - this detection issue was resolved with today's XML release (which included the release of 8u192), so now when you have 8u192 installed, 8u191 will show as Effectively Installed as expected (I verified that's the case on my own system).  Our content team has a ticket open with Oracle to address the root issue on their side, but our detection logic works around it now, so once you update your definitions you should be good to go.  If you see any continued issue with this, please open a support case and we will dig further to get the bottom of it for you.