On Mon Feb 23 11:31:37 2026 +0000, Rémi Bernon wrote:
Okay, well I'm not fully convinced either, and actually the more I look into it the more I am convinced that host GUI integration belongs to a separate process, wineserver in particular as pretty much all of it needs to go through it eventually. When I suggested that idea for X11 (but now I'm starting to think that all platforms could do the same) you didn't seem very excited about it either ;). Of course, it could be another process (lets say dwm.exe), but that seems more inefficient and unnecessarily complicated to me. The split in https://gitlab.winehq.org/wine/wine/-/commit/39afcaac4a7a713188c5c23f5fe5114... also makes sense in that this is similar-ish to how things work with `NtCreateProcessEx` only creating a process without any threads, which need to be created later.
Granted we don't properly implement this how this is done on windows, but we do have a [wine bug](https://bugs.winehq.org/show_bug.cgi?id=23451) for it, so it would be nice to ultimately work into that direction (with `NtCreateUserProcess` being implemented on top of `NtCreateSection`, `NtCreateProcessEx` and `NtCreateThreadEx`). This would also indirectly play well together with having the unix main thread hidden (and useable for another purpose), since I don't believe it is possible to have a process without a thread on unix-like systems. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10163#note_133860