CreateProcessAsUser hToken 为零

Question

I'm creating an app (name AppRunner) that will run an executable (name EXE) using winapi.

In AppRunner, I'm using CreateProcessAsUser in order to run EXE, and this method takes an hToken (a user token).

When AppRunner will be executed by user System in session 0, It will successfully fetch the user token (WTSQueryUserToken with the console session id) and everything will work fine.
However, when AppRunner will be executed by the logged in user in session>0, It will not be able to get the user token.

I noticed that when calling CreateProcessAsUser with hToken=0, EXE is being executed under the logged in user in the user's session (>0).

Can I assume that calling CreateProcessAsUser with hToken = 0 will execute EXE under the logged in user in the user's session ? I didn't find any documentation about it in the CreateProcessAsUser page.

Thanks

Answer 1

BTW, in case anyone else encounter this: CreateProcessAsUser with hToken=0 will indeed create a process with the same user as the user of the current process, BUT, CreateEnvironmentBlock will create an environment with default values, which means that appdata folder for example will point to the default user and not the current user's appdata folder. This is a big issue for me

Two workarounds:

1. Inherit parent process' (AppRunner) environment when calling CreateEnvironmentBlock . Then APPDATA environment variable will point to the current user's appdata folder. But USERPROFILE still point to C:\Users\Default .
2. Acquire parent process' (AppRunner) token using GetCurrentProcessToken , then pass this token to CreateEnvironmentBlock . Then APPDATA and USERPROFILE environment variable both point to current user.