# NativeClientLauncher (7.9.10) with x86 (32-bit) platform

**URL:** <https://forum.inductiveautomation.com/t/nativeclientlauncher-7-9-10-with-x86-32-bit-platform/24593>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [May 2, 2019, 1:42pm UTC](https://forum.inductiveautomation.com/t/nativeclientlauncher-7-9-10-with-x86-32-bit-platform/24593 "2019-05-02T13:42:25Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pphillips](https://avatars.discourse-cdn.com/v4/letter/p/da6949/32.png) [@pphillips](https://forum.inductiveautomation.com/u/pphillips)\
**Post date:** [May 2, 2019, 2:02pm UTC](https://forum.inductiveautomation.com/t/nativeclientlauncher-7-9-10-with-x86-32-bit-platform/24593/2 "2019-05-02T14:02:09Z")

</div>

See [this thread.](http://forum.inductiveautomation.com/t/native-client-launcher-32-or-64-bit/21343)

The solution given to me was to delete the jre folder that gets unpacked when the clientlauncher.exe is run. This causes the 32bit client to use its installed version of Java rather than the 64bit version that the launcher tries to use.

---

_[View the full topic](https://forum.inductiveautomation.com/t/nativeclientlauncher-7-9-10-with-x86-32-bit-platform/24593)._