@IMK, Thanks for posting in Q&A. For Win32 app, it has a setting named "Install behavior". when it is set as system, it will run under system account. When it is set as user, the command will run under currently logging user. For different user, the variable "%appdata%" will be different.
https://learn.microsoft.com/en-us/mem/intune/apps/apps-win32-add#step-2-program
To make iWin32 work, the command needs to be able to run successfully on the device side before we deploy it. You can manually test the command on one affected device to see if it works. For example, if the above setting is set as user, we can test on current logging user. For system account, you can use PsExec tool to run as system account to test.
https://learn.microsoft.com/en-us/sysinternals/downloads/psexec
Hope the above information can help.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.