# \[Feature-15996\] Ignition Launchers use ~/.ignition instead of AppData

**URL:** <https://forum.inductiveautomation.com/t/feature-15996-ignition-launchers-use-ignition-instead-of-appdata/32139>\
**Category:** Ignition\
**Created:** [February 11, 2020, 7:10pm UTC](https://forum.inductiveautomation.com/t/feature-15996-ignition-launchers-use-ignition-instead-of-appdata/32139 "2020-02-11T19:10:34Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![kishlaya.brahmachari](https://avatars.discourse-cdn.com/v4/letter/k/ecb155/32.png) [@kishlaya.brahmachari](https://forum.inductiveautomation.com/u/kishlaya.brahmachari)\
**Post date:** [July 10, 2020, 8:02am UTC](https://forum.inductiveautomation.com/t/feature-15996-ignition-launchers-use-ignition-instead-of-appdata/32139/17 "2020-07-10T08:02:33Z")

</div>

Well the launcher was indeed installed by an administrator, however the Chromium binaries were extracted into a default C:\Users… Supplying addtion JVM parameters solved this problem. [Here I found my solution](http://forum.inductiveautomation.com/t/use-custom-working-directory/36429/2)

---

_[View the full topic](https://forum.inductiveautomation.com/t/feature-15996-ignition-launchers-use-ignition-instead-of-appdata/32139)._