# Execute Program action in 5.5 - trying to change the running user results in app crash

**URL:** <https://www.finalbuilder.com/forums/t/execute-program-action-in-5-5-trying-to-change-the-running-user-results-in-app-crash/7672>\
**Category:** Bugs\
**Created:** [July 7, 2025, 3:02pm UTC](https://www.finalbuilder.com/forums/t/execute-program-action-in-5-5-trying-to-change-the-running-user-results-in-app-crash/7672 "2025-07-07T15:02:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jonathanmeltzer](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/j/34f0e0/32.png) [@jonathanmeltzer](https://www.finalbuilder.com/forums/u/jonathanmeltzer)\
**Post date:** [July 7, 2025, 3:02pm UTC](https://www.finalbuilder.com/forums/t/execute-program-action-in-5-5-trying-to-change-the-running-user-results-in-app-crash/7672/1 "2025-07-07T15:02:23Z")

</div>

I have an Execute Program action that has worked fine for months, but after the 5.5 install I am getting an encrypt/decrypt error instead. While troubleshooting, I saw that the action was set in the Runtime/Execution Properties to Run Action As User, with a user specified. Thinking that this could be the cause of the problem, I tried to change that property on the action, but each time I click on that line the application crashes. This has some time sensitivity, as it is a daily process that is failing, and in fact it has failed for the last week, at least. Probably since the upgrade to 5.5.

---

<div class="post-metadata">

**Author:** ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)\
**Post date:** [July 8, 2025, 12:14am UTC](https://www.finalbuilder.com/forums/t/execute-program-action-in-5-5-trying-to-change-the-running-user-results-in-app-crash/7672/2 "2025-07-08T00:14:50Z")

</div>

Hi Jonathan

Thanks for the report - this one is my fault - in the last update I grepped the source and thought I had replaced a function call everywhere, but sadly I missed one (so it was still using the old encryption algorithm).

We were able to fix this issue in a way there should be no data loss (I did make sure to test this).

[https://downloads.finalbuilder.com/downloads/automise/550/AT550\_1673.exe](https://downloads.finalbuilder.com/downloads/automise/550/AT550_1673.exe)

[https://downloads.finalbuilder.com/downloads/automise/550/ATCMD550\_1673.exe](https://downloads.finalbuilder.com/downloads/automise/550/ATCMD550_1673.exe)

---

<div class="post-metadata">

**Author:** ![jonathanmeltzer](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/j/34f0e0/32.png) [@jonathanmeltzer](https://www.finalbuilder.com/forums/u/jonathanmeltzer)\
**Post date:** [July 8, 2025, 12:02pm UTC](https://www.finalbuilder.com/forums/t/execute-program-action-in-5-5-trying-to-change-the-running-user-results-in-app-crash/7672/3 "2025-07-08T12:02:22Z")

</div>

Thank you! Will this make the Execute Program work as is, or does it make it so that I can change the Run Action As User properties without the crash, or both?

---

<div class="post-metadata">

**Author:** ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)\
**Post date:** [July 8, 2025, 12:03pm UTC](https://www.finalbuilder.com/forums/t/execute-program-action-in-5-5-trying-to-change-the-running-user-results-in-app-crash/7672/4 "2025-07-08T12:03:24Z")

</div>

It should work as is. With opening the action to check that the password is still set.

---

<div class="post-metadata">

**Author:** ![jonathanmeltzer](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/j/34f0e0/32.png) [@jonathanmeltzer](https://www.finalbuilder.com/forums/u/jonathanmeltzer)\
**Post date:** [July 8, 2025, 2:25pm UTC](https://www.finalbuilder.com/forums/t/execute-program-action-in-5-5-trying-to-change-the-running-user-results-in-app-crash/7672/5 "2025-07-08T14:25:04Z")

</div>

You’re right. The project now works as it did before. Thank you for the quick turnaround!
