The compiled Process should Run as Administrator.
Compiled Processes (.exe files) can be created through WinAutomation. Any number of compiled Processes can run on a single machine, by purchasing a single Per Machine Token.
The number of different users that will be able to execute compiled Processes on that machine depends on the way that the first compiled Process runs for the first time.
Case 1 - The first compiled Process is executed as an administrator (right click > run as admin).
In this way, all users that have access to the machine will be able to run compiled Processes.
Hence, even though one Per Machine Token has been consumed, all the users can run executable files.
Case 2 - The first compiled Process is executed normally.
In this way, only one user is able to execute compiled Processes.
Hence, the Per Machine Token has been consumed by one user only.
However, in case the .exe file is executed as admin (right click > run as admin) at least once later on, it will behave as a Per Machine Token again, and every user will be able to run it.
When an administrator runs a compiled Process, a string called “Machine ID” is created by WinAutomation and stored into the registry, in the registry folders “LOCAL_MACHINE” and “CURRENT_USER”.
Every user (regardless of administrator privileges) has access to “LOCAL_MACHINE” by default. Hence, any user that runs compiled Processes will be able to access that Machine ID.
On the other hand, when a non-administrator executes a compiled Process, the Machine ID is created and stored into the “CURRENT_USER” folder ONLY.
Hence, the compiled Processes that are executed by other users, will NOT be able to access that Machine ID.
*Access to the Machine ID by the compiled Process is crucial for its authentication.
For more information regarding Runtime Tokens check this article.