# Native Client Launcher 7.7.5 doesn't work for Windows

**URL:** <https://forum.inductiveautomation.com/t/native-client-launcher-7-7-5-doesnt-work-for-windows/10662>\
**Category:** Ignition\
**Created:** [October 24, 2015, 1:00pm UTC](https://forum.inductiveautomation.com/t/native-client-launcher-7-7-5-doesnt-work-for-windows/10662 "2015-10-24T13:00:17Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![framebuilder](https://avatars.discourse-cdn.com/v4/letter/f/96bed5/32.png) [@framebuilder](https://forum.inductiveautomation.com/u/framebuilder)\
**Post date:** [October 24, 2015, 1:00pm UTC](https://forum.inductiveautomation.com/t/native-client-launcher-7-7-5-doesnt-work-for-windows/10662/1 "2015-10-24T13:00:17Z")

</div>

clientlauncher.exe version 7.7.5 for Windows doesn’t open. I get the following error attached.

Our Gateway is version 7.7.5, Gateway Java is 1.8.0\_60

I’ve tried with different computers with 1.6, 1.7, and 1.8 JREs and all have the same error.

I have a copy of clientlauncher.exe 7.7.4 and it works fine.  
 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/c/c1b63b6b9a2164895b5b4c3abd6cbbe2bbfee4f0.jpg)

---

<div class="post-metadata">

**Author:** ![mgross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mgross/32/3311_2.png) [@mgross](https://forum.inductiveautomation.com/u/mgross)\
**Post date:** [October 26, 2015, 4:19pm UTC](https://forum.inductiveautomation.com/t/native-client-launcher-7-7-5-doesnt-work-for-windows/10662/2 "2015-10-26T16:19:16Z")

</div>

Does it generate a clientlauncher.log file? It would be in /.ignition/clientlauncher-data. If so, is there anything interesting in there?

---

<div class="post-metadata">

**Author:** ![framebuilder](https://avatars.discourse-cdn.com/v4/letter/f/96bed5/32.png) [@framebuilder](https://forum.inductiveautomation.com/u/framebuilder)\
**Post date:** [October 26, 2015, 4:58pm UTC](https://forum.inductiveautomation.com/t/native-client-launcher-7-7-5-doesnt-work-for-windows/10662/3 "2015-10-26T16:58:55Z")

</div>

Unfortunately, it doesn’t make it that far. In fact, I don’t think it can find java.exe at all because I never see it attempt to launch it in Task Manager.

If I create a /jre folder in the same directory as clientlauncher.exe 7.7.5 with a copy of my java install, it launches fine.

java -version from CLI also executes correctly.

I tried a JAVA\_HOME env variable but it didn’t help. Something must have changed between 7.7.4 and 7.7.5 regarding how it looks for java.exe. It’s almost like it only looks for it in a /jre folder near the executable. Does this sound reasonable?

---

<div class="post-metadata">

**Author:** ![mgross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mgross/32/3311_2.png) [@mgross](https://forum.inductiveautomation.com/u/mgross)\
**Post date:** [October 26, 2015, 5:50pm UTC](https://forum.inductiveautomation.com/t/native-client-launcher-7-7-5-doesnt-work-for-windows/10662/4 "2015-10-26T17:50:20Z")

</div>

I went back thru our bug database, and it looks like there was an issue with the 7.7.5 native launcher that has your symptoms. It recently got fixed (Fogbugz ticket 5830 for anyone else who reads this). The fix should be present in the next 7.7.6 RC.

---

<div class="post-metadata">

**Author:** ![framebuilder](https://avatars.discourse-cdn.com/v4/letter/f/96bed5/32.png) [@framebuilder](https://forum.inductiveautomation.com/u/framebuilder)\
**Post date:** [October 26, 2015, 6:53pm UTC](https://forum.inductiveautomation.com/t/native-client-launcher-7-7-5-doesnt-work-for-windows/10662/5 "2015-10-26T18:53:10Z")

</div>

Cool. I’ll keep using 7.7.4 until the new one gets released.

It appears that there is a checksum validation on launchclient.jar that always ensures the latest version .jar file is downloaded from the Gateway regardless of the version of the clientlauncher.exe so we should be fine for awhile.