# \[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:** 15

<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 9, 2020, 8:33am UTC](https://forum.inductiveautomation.com/t/feature-15996-ignition-launchers-use-ignition-instead-of-appdata/32139/15 "2020-07-09T08:33:24Z")

</div>

Hi,  
Facing a similar issue here [Separate post for clarity](http://forum.inductiveautomation.com/t/use-custom-working-directory/36429)  
I put redirect.txt on .ignition/ directory, it managed to move away from the .ignition directroy for creating clientlauncher-data to the desired location. However, it still tries to extract chromium related files in C:\Users… . Is there a way to redirect that as well to a location where running executables are not blocked by groupd policy.

 ![WD](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/a/1ad2a1cc8c114fdb78d6fad677f6b8fd4e7d1b5f.png)  
Thanks…

---

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