Short answer

The compiled Process should be executed by an Administrator account (or Run as an Administrator).

Long answer

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 the 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 being executed by an administrator account.

In this way, all the users that have access to the machine will be able to run compiled Processes.

Hence, even though one Per Machine Token is being consumed, all the users can run executables.

Case 2 - The first compiled Process is being executed by a non-administrator account.

In this way, only this particular user is able to execute compiled Processes.

Hence, the Per Machine concept becomes also per user.

However, in case the exe runs with admin privileges at least once, it becomes Per Machine again and every user can run it.

In-depth analysis

Case 1

When an administrator is running a compiled Process, a string called “Machine ID” is being created by WinAutomation and stored into the registry, in both the registry folders “LOCAL_MACHINE” and “CURRENT_USER”.

Every user – administrator or not, has access to “LOCAL_MACHINE” by default. Hence, any user that runs compiled Processes, will be able to access that Machine ID.

Case 2

On the other hand, when a non-administrator is executing a compiled Process, the Machine ID is being created and stored into the “CURRENT_USER” folder ONLY.

Hence, the compiled Processes that are being executed by other users (non-administrators), 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.