Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.


Java Packages - Need 32bit installed on 64bit machines

I noticed I've been having issues with the Java Packages (Regardless of using standard or the alternative package). Could the 64bit packages be updated to not skip a 32bit install on a 64bit machine? I'm working on editing the steps on my current packages but thought this might be beneficial to others.

The reason for this is any 32bit browser needs the 32bit version of Java installed and on all of the 64bit systems in our environment we have to unfortunately use 32bit IE to access certain webpages (Accounting and HR departments).



John (and sorry if this isn't in the right place...)



Date Votes
  • What issues are you seeing other than having to deploy both the 32 and 64-bit packages? We are hesitant to include the 32-bit installation in the 64-bit package because many of our customers only use the 64-bit Java and have no desire for the 32-bit to be installed. For those customers who want both architectures. they can simply deploy both packages.

    Are you seeing other issues or errors besides that?


  • Thanks for the Reply Shane. I could be wrong but it looks like deploying the 32bit version on a 64bit system is installing the package to %ProgramW6432%, which installs it to "Program Files", instead of "Program Files x86".

    The problem I'm having is the Kronos website we use to check timecards relies on Java. On our 64bit machines, after deploying the 32bit Java version, the website returns that Java isn't installed. I noticed if I remove java and reinstall from the Java website, the 32bit version is installed to the Program Files x86 folder and everything appears to work correctly.

    I haven't had a chance to duplicate the package and edit the conditions and install location, but I'll give it a shot to see if it works. I understand that we all have different environments and I didn't consider that would be installing both on 64bit systems.

  • Quick follow up, The Java 32 Alternative package installs Java correctly.

    The regular Java 32 package has the installer (when 64 bit is detected) pointing to %ProgramW6432% and it installs to "Program Files". When Java is there, it shows installed under Add/Remove programs but 32bit IE doesn't detect that Java is installed.

    The alternative package however installs 32bit Java on 64bit windows correctly to the "Program Files x86" folder and 32bit IE detects it correctly.

    I have no issue pushing these together when needed. No need to push a request for them to be added.

  • Just to add to this:

    We have to customize the heck out of our Java installation, so I feel your pain!  One particular software program that we use dumps temporary files in the java install folder and then hard codes itself to that particular path.  As you know, every time you update java, the install folder changes to match the name of the java version.  Therefore, every time we updated Java, it broke this lovely piece of software all across our campus.  And to top it off, Java does not like to re-install into a file location that is not empty of all other files.  Nice!!

    We ended up using a parameter that forces java to install where you want it:


    This way, the path never changes no matter how many updates we do and this software always knows where to find Java. 

    We also wrote a script that wipes all versions of the Java JRE but leaves the JDK alone.  Many uninstall scripts remove the JDK too...

    We then use a powershell step in our package that deletes anything in our java directory.

    Looks something like this:

    Remove-Item "c:\Program Files (x86)\Java\*" -recurse  



    We uninstall all Java JRE, delete any remaining lingering files and install java back into the same custom folder. each time.


    I thought that the INSTALLDIR= might come in handy for you in the future John.