# \[FB14892\] Client launcher uses Azul Java even with useBundledJre=false

**URL:** <https://forum.inductiveautomation.com/t/fb14892-client-launcher-uses-azul-java-even-with-usebundledjre-false/26054>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [June 24, 2019, 10:50am UTC](https://forum.inductiveautomation.com/t/fb14892-client-launcher-uses-azul-java-even-with-usebundledjre-false/26054 "2019-06-24T10:50:10Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ggross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ggross/32/12668_2.png) [@ggross](https://forum.inductiveautomation.com/u/ggross)\
**Post date:** [June 26, 2019, 5:19pm UTC](https://forum.inductiveautomation.com/t/fb14892-client-launcher-uses-azul-java-even-with-usebundledjre-false/26054/2 "2019-06-26T17:19:48Z")

</div>

For some reason the default install location of Java isn’t being found and we always fall back to the internal version when this happens. We are looking into why this is happening, but to get around the issue adding a JAVA\_HOME environment variable as a System Variable to your Windows installation will resolve the issue. This environment variable will need to point to the installation directory for Java (ex. C:\Program Files\Java\jre1.8.0\_191).

Thanks,  
Garth

---

_[View the full topic](https://forum.inductiveautomation.com/t/fb14892-client-launcher-uses-azul-java-even-with-usebundledjre-false/26054)._