v2. Diff: - squashed v1-1/5 and v1-2/5 - split the server change in v1-4/5; became v2-3/5 - changed the wtsapi32 change in 4/5 to always return the session id 1. I have probed Windows for this; Windows returns on a standard install three sessions; Session 0/Services, Session 11/Console, Session 65535/RDP-TCP. Since the name is fixed on Console, and session name handling would involve more elaborate session handling on the server side, I've fixed the session id to also always be 1. This session is guaranteed to always exist and is exactly the behaviour from before my changes. I still don't have a good idea how to deal with 5/5 though. So far, I haven't found a viable way to do this correctly server-side. I could, obviously, move the same hackjob to the server and reset the winstation to the default value if the parent process' session_id != new process' session_id. Let me know if this sounds like a viable way to do things, then I'll go ahead and push this in v3. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9843#note_126429