On Mon Feb 9 15:23:32 2026 +0000, Rémi Bernon wrote:
It will be visible, though we can maybe try to hide it. Regarding its entry point it has the same entry point as the main thread, as this is initialized when mapping the main executable. The new application main thread is initialized as any other thread and also has `main_image_info.TransferAddress` as entry point. Idk if this is likely to cause any confusion, and whether we should try to use a different address? So it looks like this visibly diverges from how thing look on Windows. I think the only way is to have it hidden in some way and not appear in any app-visible queries. That would probably need some attribute for this first thread on the server and explicitly excluding it from any user visible queries. That would mean of course that such a thread will have some limitations in what it can do, likely it won't be able to send window messages.
Then, probably the condition when the process is considered terminated should exclude this service thread too? -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10058#note_129198