few problems

[darkjezza]

have these warnings

WARNING: InputHook build failed -- keyboard/mouse isolation unavailable
WARNING: MultiSeatInputHook.dll not found at C:\Users\Jezza\Desktop\MultiSeat\scripts..\src\MultiSeat.InputHook\build\Release\MultiSeatInputHook.dll -- keyboard/mouse isolation unavailable

and these

[SUDOVDA] Open device failed!
[SUDOVDA] Open device failed!
[SUDOVDA] Open device failed!
[SUDOVDA] Open device failed!
[SUDOVDA] Open device failed!

[vibesoftwarecoder]

Thanks for the report. Short version: the first pair of warnings is harmless and you can ignore them — the second one is the real problem. Let me split them, and then I need one thing from you, because I can't tell from the paste what's actually broken.

The InputHook warnings — harmless, ignore them

WARNING: InputHook build failed -- keyboard/mouse isolation unavailable
WARNING: MultiSeatInputHook.dll not found ...

These fire because install-service.ps1 only builds that DLL if MSYS2 is present at C:\msys64, and it isn't on your machine. That's fine — MSYS2 is an optional developer dependency, not a prerequisite.

More to the point: that DLL is unused by default. EnableKeyboardMouseIsolation defaults to false, and the feature is a no-op as currently architected — the low-level keyboard/mouse hooks get installed from the service process in Session 0, where GetForegroundWindow() returns NULL, so the filter never actually blocks anything. There's also no cross-session keyboard/mouse bleed to prevent in the current design: physical input goes to the console session, and Moonlight's input is injected inside the seat session. So a missing MultiSeatInputHook.dll changes nothing about how MultiSeat runs.

Fair criticism on our side: two WARNINGs for an optional, off-by-default, currently-inert component reads like a failed install. I'll downgrade that wording so it stops alarming people.

The SudoVDA errors — this is the actual issue

[SUDOVDA] Open device failed!

That's Apollo failing to open a handle to the SudoVDA virtual display driver. Without it, Apollo can't create a virtual display for the seat, so the seat won't stream properly. Most likely causes, roughly in order:

1. The driver was installed but the machine hasn't been rebooted since. SudoVDA needs one reboot after first install before its device interface is usable. If install-prerequisites.ps1 asked for a reboot and it hasn't happened yet, this is almost certainly it — reboot and re-run the prerequisites script to confirm it comes back clean.
2. The driver is installed but in an error state (bad/partial install).
3. A privilege problem — SudoVDA's IPC needs an elevated token, and Windows hands back a filtered medium-integrity token for admin accounts in some paths.

What I need from you

The warnings alone don't tell me what's failing from your side, so — what's the actual symptom? Does a seat fail to provision, does it provision but not stream, does Moonlight not see it, is there no picture? That determines which of the above it is.

Along with that, could you paste:

1. The display device list (read-only):

Get-PnpDevice -Class Display -ErrorAction SilentlyContinue |
  Select-Object Status, FriendlyName, InstanceId | Format-Table -AutoSize

I'm looking for a SudoMaker/SudoVDA entry and what its Status says.

2. Whether you've rebooted since running install-prerequisites.ps1.

3. The service log from C:\ProgramData\MultiSeat\logs\, and the seat's apollo.log from C:\ProgramData\MultiSeat\apollo\<account>\apollo.log. If the logs folder is completely empty after the service has run, tell me — that's a separate startup problem worth chasing on its own.

One other thing worth doing regardless: please pull the latest master before you retest. A bug was just fixed (#9) where the prerequisites script, when run under 32-bit PowerShell on a 64-bit OS, couldn't see driver device nodes or find staged driver INFs — which made driver installs silently under-report. If you happened to launch it from a 32-bit PowerShell, that could be tangled up in what you're seeing.

[darkjezza]

ok so i got the latest version but still getting this

OK: SudoVDA detected (Virtual Display Driver)
NOTE: VirtualDisplayDriver service not found — run prerequisites\install-prerequisites.ps1 to install SudoVDA OK: SudoVDA detected (Virtual Display Driver)

[vibesoftwarecoder]

Thanks — that output was the useful part, and you found a real bug. I reproduced it exactly here and it's now fixed on master (caa53a3).

Those two lines contradict each other, and both were wrong:

OK: SudoVDA detected (Virtual Display Driver)
NOTE: VirtualDisplayDriver service not found — run install-prerequisites.ps1 to install SudoVDA

Line 1 was a false positive. The check matched the display's friendly name against VDD|Virtual Display|SudoVDA|MTT — a pattern that matches basically any virtual display driver. On my own machine, which genuinely has no SudoVDA, it cheerfully reported SudoVDA detected (USB Mobile Monitor Virtual Display). Yours matched something called "Virtual Display Driver," which is almost certainly a different virtual display driver, not SudoVDA. It now checks the way the service itself does — a ROOT\DISPLAY device whose DeviceDesc/HardwareID actually says SudoMaker/SudoVDA — and prints the registry key so the claim is verifiable.

Line 2 was chasing the wrong driver. VirtualDisplayDriver is the service belonging to an optional persistent display driver (MttVDD), used only so a headless machine has a display at boot. SudoVDA doesn't register that service at all, so its absence tells you nothing about SudoVDA — yet the message told you to go install SudoVDA. That's now an informational note that says what it actually is.

So: pull master and re-run install-service.ps1. You'll get an honest answer either way. My guess is it will now say SudoVDA is not installed — which lines up with the [SUDOVDA] Open device failed! errors in your first post, and means the driver was never really there despite the script's reassurance.

---

A correction on something I told you earlier. I asked you to send "the service log from C:\ProgramData\MultiSeat\logs\" and said an empty folder might indicate a separate startup problem. That was wrong, and I'm sorry for the runaround. The service writes no log files at all — it logs to the Windows Event Log. That folder only ever receives audio-helper.log, and only after a seat has run, so an empty folder there is completely normal. The docs said otherwise; that's fixed too.

To actually read the service log:

.\scripts\show-logs.ps1

or directly:

Get-WinEvent -FilterHashtable @{LogName='Application'; ProviderName='MultiSeat.Service'} -MaxEvents 50

---

Two other things that may be relevant to your machine, both found while chasing this:

1. SudoVDA usually needs a reboot after it's installed before its device interface works. If the script installs it and you haven't rebooted, Open device failed! is expected. On my box, Apollo detected the missing driver, reinstalled it itself, and logged "A reboot may be required" — worth doing before concluding anything is broken.

2. HidHide was silently failing to install from the prerequisites script (wrong silent-install switches — it installed nothing at all, no error surfaced). Also fixed on master. If you saw a HidHide warning, that's why.

When you've pulled and re-run, could you paste the new SudoVDA line plus the Get-PnpDevice -Class Display output from my earlier message? With honest detection in place, those two together will say definitively whether the driver is present, and I can tell you exactly what to do next.

And I'm still curious about the original question: what's actually failing for you — does a seat fail to provision, provision but not stream, or something else? That still shapes where to look.

[darkjezza]

apollo.log

ok so i got it working but the resolution is wrong on client and sound not working on host or client

`=== MultiSeat service log -- Application event log, last 24 h ===
[2026-08-07 00:04:47] Information Service started successfully.
[2026-08-07 00:04:48] Error Category: MultiSeat.Service.Sessions.RdpWrapper
EventId: 0

rdpwrap.ini does NOT contain an entry for build 26200. Update rdpwrap.ini from https://github.com/sebaxakerhtc/rdpwrap.ini or apply a manual patch.

[2026-08-07 00:04:48] Error Category: MultiSeat.Service.MultiSeatWorker
EventId: 0

RDP Wrapper multi-session patch not detected. Concurrent sessions will not work. Install RDP Wrapper Library and restart.

[2026-08-07 00:05:10] Error Category: MultiSeat.Service.Sessions.SeatManager
EventId: 0

Seat f20feea7-23eb-4eb6-9e8f-f77fd2952183: provisioning failed at Provisioning

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142

[2026-08-07 00:05:10] Error Category: MultiSeat.Service.MultiSeatWorker
EventId: 0

Failed to auto-provision seat 'Emulation'

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 382
at MultiSeat.Service.MultiSeatWorker.AutoProvisionSeatsAsync(CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\MultiSeatWorker.cs:line 161

[2026-08-07 00:10:19] Information Service started successfully.
[2026-08-07 00:10:19] Error Category: MultiSeat.Service.Sessions.RdpWrapper
EventId: 0

rdpwrap.ini does NOT contain an entry for build 26200. Update rdpwrap.ini from https://github.com/sebaxakerhtc/rdpwrap.ini or apply a manual patch.

[2026-08-07 00:10:19] Error Category: MultiSeat.Service.MultiSeatWorker
EventId: 0

RDP Wrapper multi-session patch not detected. Concurrent sessions will not work. Install RDP Wrapper Library and restart.

[2026-08-07 00:10:41] Error Category: MultiSeat.Service.Sessions.SeatManager
EventId: 0

apollo.log

apollo2.log

Seat 953d38aa-8f09-4426-a3b7-a34f5f329ec6: provisioning failed at Provisioning

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142

[2026-08-07 00:10:41] Error Category: MultiSeat.Service.MultiSeatWorker
EventId: 0

Failed to auto-provision seat 'Emulation'

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 382
at MultiSeat.Service.MultiSeatWorker.AutoProvisionSeatsAsync(CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\MultiSeatWorker.cs:line 161

[2026-08-07 00:34:42] Information Service started successfully.
[2026-08-07 00:34:43] Error Category: MultiSeat.Service.Sessions.RdpWrapper
EventId: 0

rdpwrap.ini does NOT contain an entry for build 26200. Update rdpwrap.ini from https://github.com/sebaxakerhtc/rdpwrap.ini or apply a manual patch.

[2026-08-07 00:34:43] Error Category: MultiSeat.Service.MultiSeatWorker
EventId: 0

RDP Wrapper multi-session patch not detected. Concurrent sessions will not work. Install RDP Wrapper Library and restart.

[2026-08-07 00:35:05] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Session for Emulation timed out after 15204ms — mstsc is still running. RDP Wrapper multi-session patch may not be active — the connection may have reconnected an existing session instead of creating a new one. Check RDPConf.exe (Listener state should be 'Listening [fully supported]').

[2026-08-07 00:35:05] Error Category: MultiSeat.Service.Sessions.SeatManager
EventId: 0

Seat cb3d04ae-bee0-469b-9cc4-e8602f2a0052: provisioning failed at Provisioning

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142

[2026-08-07 00:35:05] Error Category: MultiSeat.Service.MultiSeatWorker
EventId: 0

Failed to auto-provision seat 'Emulation'

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 382
at MultiSeat.Service.MultiSeatWorker.AutoProvisionSeatsAsync(CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\MultiSeatWorker.cs:line 161

[2026-08-07 00:56:18] Information Service started successfully.
[2026-08-07 00:56:18] Error Category: MultiSeat.Service.Sessions.RdpWrapper
EventId: 0

rdpwrap.ini does NOT contain an entry for build 26200. Update rdpwrap.ini from https://github.com/sebaxakerhtc/rdpwrap.ini or apply a manual patch.

[2026-08-07 00:56:18] Error Category: MultiSeat.Service.MultiSeatWorker
EventId: 0

RDP Wrapper multi-session patch not detected. Concurrent sessions will not work. Install RDP Wrapper Library and restart.

[2026-08-07 00:56:41] Error Category: MultiSeat.Service.Sessions.SeatManager
EventId: 0

Seat 3ffcdcfc-00b4-4d32-9483-ca82cfa1c986: provisioning failed at Provisioning

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142

[2026-08-07 00:56:41] Error Category: MultiSeat.Service.MultiSeatWorker
EventId: 0

Failed to auto-provision seat 'Emulation'

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 382
at MultiSeat.Service.MultiSeatWorker.AutoProvisionSeatsAsync(CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\MultiSeatWorker.cs:line 161

[2026-08-07 00:59:05] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0
SpanId: 9690661b7edc05f8
TraceId: d8f7cd5f243069c85a677311f8e08799
ParentId: 0000000000000000

Session for Emulation timed out after 15244ms — mstsc is still running. RDP Wrapper multi-session patch may not be active — the connection may have reconnected an existing session instead of creating a new one. Check RDPConf.exe (Listener state should be 'Listening [fully supported]').

[2026-08-07 00:59:05] Error Category: MultiSeat.Service.Sessions.SeatManager
EventId: 0
SpanId: 9690661b7edc05f8
TraceId: d8f7cd5f243069c85a677311f8e08799
ParentId: 0000000000000000

Seat f2fc88a6-ce24-40a0-a1fe-fbdd004c6589: provisioning failed at Provisioning

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142

[2026-08-07 01:00:17] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0
SpanId: 2e04ef6736777961
TraceId: e9cdc218fb90460290606bda8823aa7f
ParentId: 0000000000000000

Session for Emulation timed out after 15375ms — mstsc is still running. RDP Wrapper multi-session patch may not be active — the connection may have reconnected an existing session instead of creating a new one. Check RDPConf.exe (Listener state should be 'Listening [fully supported]').

[2026-08-07 01:00:17] Error Category: MultiSeat.Service.Sessions.SeatManager
EventId: 0
SpanId: 2e04ef6736777961
TraceId: e9cdc218fb90460290606bda8823aa7f
ParentId: 0000000000000000

Seat 485e5a2c-0e55-45f3-a821-a3e6aeec9602: provisioning failed at Provisioning

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142

[2026-08-07 01:00:35] Error Category: MultiSeat.Service.Sessions.RdpWrapper
EventId: 0
SpanId: baa21294644a7c7f
TraceId: bebd93b368eb175a6000f3ff32f5765b
ParentId: 0000000000000000

rdpwrap.ini does NOT contain an entry for build 26200. Update rdpwrap.ini from https://github.com/sebaxakerhtc/rdpwrap.ini or apply a manual patch.

[2026-08-07 01:00:39] Error Category: MultiSeat.Service.Sessions.RdpWrapper
EventId: 0
SpanId: 8b891faa492573f7
TraceId: 4430647be0628673339c3a4f7717b52f
ParentId: 0000000000000000

rdpwrap.ini does NOT contain an entry for build 26200. Update rdpwrap.ini from https://github.com/sebaxakerhtc/rdpwrap.ini or apply a manual patch.

[2026-08-07 01:07:28] Information Service started successfully.
[2026-08-07 01:08:49] Information Service stopped successfully.
[2026-08-07 01:09:43] Information Service started successfully.

=== Helper log files in C:\ProgramData\MultiSeat\logs ===
audio-helper.log (08/07/2026 01:12:56)

--- Last 80 lines of audio-helper.log ---
[2026-08-03 13:02:33.117 +10:00] SetDefaultAudioDevice deviceId={0.0.1.00000000}.{3be81bc8-a4a0-4337-9d79-df9d8975a0f2}
SessionId=2 User=JEZZASPC\Emulation
role=0 HRESULT=0x00000000 OK
role=1 HRESULT=0x00000000 OK
role=2 HRESULT=0x00000000 OK
Result=SUCCESS
[2026-08-03 13:04:41.025 +10:00] SetDefaultAudioDevice deviceId={0.0.1.00000000}.{3be81bc8-a4a0-4337-9d79-df9d8975a0f2}
SessionId=2 User=JEZZASPC\Emulation
role=0 HRESULT=0x00000000 OK
role=1 HRESULT=0x00000000 OK
role=2 HRESULT=0x00000000 OK
Result=SUCCESS
[2026-08-05 12:41:56.221 +10:00] SetDefaultAudioDevice deviceId={0.0.1.00000000}.{3be81bc8-a4a0-4337-9d79-df9d8975a0f2}
SessionId=1 User=JEZZASPC\Jezza
role=0 HRESULT=0x00000000 OK
role=1 HRESULT=0x00000000 OK
role=2 HRESULT=0x00000000 OK
Result=SUCCESS
[2026-08-07 01:07:50.970 +10:00] SetDefaultAudioDevice deviceId={0.0.1.00000000}.{3be81bc8-a4a0-4337-9d79-df9d8975a0f2}
SessionId=2 User=JEZZASPC\Emulation
role=0 HRESULT=0x00000000 OK
role=1 HRESULT=0x00000000 OK
role=2 HRESULT=0x00000000 OK
Result=SUCCESS
[2026-08-07 01:09:54.757 +10:00] SetDefaultAudioDevice deviceId={0.0.1.00000000}.{3be81bc8-a4a0-4337-9d79-df9d8975a0f2}
SessionId=3 User=JEZZASPC\Emulation
role=0 HRESULT=0x00000000 OK
role=1 HRESULT=0x00000000 OK
role=2 HRESULT=0x00000000 OK
Result=SUCCESS
[2026-08-07 01:12:56.151 +10:00] SetDefaultAudioDevice deviceId={0.0.1.00000000}.{3be81bc8-a4a0-4337-9d79-df9d8975a0f2}
SessionId=4 User=JEZZASPC\JezzasGuest
role=0 HRESULT=0x00000000 OK
role=1 HRESULT=0x00000000 OK
role=2 HRESULT=0x00000000 OK
Result=SUCCESS

=== Per-seat Apollo logs (pass a path to Get-Content to read one) ===
C:\ProgramData\MultiSeat\apollo\Jezza\apollo.log (08/05/2026 12:42:22)
C:\ProgramData\MultiSeat\apollo\Emulation\apollo.log (08/07/2026 01:12:10)
C:\ProgramData\MultiSeat\apollo\JezzasGuest\apollo.log (08/07/2026 01:13:38)`

[vibesoftwarecoder]

Good — that apollo.log was exactly what I needed. Both remaining symptoms are now explained, and the resolution one is our bug. They're unrelated to each other, so I'll take them separately.

The wrong resolution — confirmed MultiSeat bug, fixed

Your log has these two facts side by side:

config: 'output_name' = {f96a9834-1d18-5ee4-83e0-0964152a1577}
Desktop resolution [3440x1440]
Display refresh rate [1000Hz]

output_name is what MultiSeat hands Apollo to tell it which display to capture. It's set — but Apollo is capturing a 3440x1440 @ 1000Hz surface, which is your RDP session desktop, not a virtual display. That's why the client resolution is wrong: the stream is showing your real desktop at its own size, and 1920x1080 never gets a look in.

Here's the display list your seat actually enumerated:

[
  {
    "device_id": "{f96a9834-1d18-5ee4-83e0-0964152a1577}",
    "display_name": "\\.\DISPLAY1",
    "edid": null,
    "friendly_name": "",
    "info": {
      "primary": true,
      "refresh_rate": { "value": { "denominator": 1, "numerator": 1000 } },
      "resolution": { "height": 1440, "width": 3440 }
    }
  }
]

One display. No virtual display at all. And MultiSeat picked it anyway.

The cause is a bad heuristic on our side. SudoVDA registers at 1000 Hz, and inside an RDP session Windows reports its friendly_name as empty — so MultiSeat had a fallback that said "the first display running at 1000 Hz is SudoVDA." The problem: the Microsoft RDP indirect display is also 1000 Hz, also has edid: null, and also has an empty friendly_name. It is indistinguishable from SudoVDA on those fields. So on every RDP-loopback seat the fallback could match the RDP desktop and confidently report success — and on a machine with no SudoVDA at all, like yours, it always did.

Fixed. The fallback now requires the 1000 Hz display to be non-primary and requires more than one display to be present — because SudoVDA is always attached alongside the session desktop, never as the lone primary. When neither holds, MultiSeat now returns nothing and logs the truth instead of a false positive:

No SudoVDA display in Apollo log: 1 display(s) enumerated and the only 1000Hz match was the session's primary display — that is the RDP surface, not a virtual display. Apollo created no virtual display for this seat.

I ran the new parser against your actual attached log to confirm it: it now correctly rejects {f96a9834-…} instead of accepting it.

Important caveat, so this doesn't waste your time: this fix stops MultiSeat pointing Apollo at the wrong display. It does not by itself create the right one. What it does is stop the real problem from hiding behind a fake success — and the real problem is that no virtual display is being created on your machine at all. That lines up with the [SUDOVDA] Open device failed! errors in your very first post.

So the resolution won't be correct until the virtual display exists, which brings me to the thing I need from you.

What I need: your display device inventory

Could you paste the output of:

Get-PnpDevice -Class Display | Format-Table Status,FriendlyName,InstanceId -AutoSize

I'm specifically looking for whether a SudoVDA / SudoMaker device node exists. Something I learned the hard way on my own machine this week and that may well apply to yours:

• The SudoVDA driver being "installed" and a SudoVDA device node existing are two different things. The driver package can sit in the Windows driver store while no device node exists — and in that state Apollo reports exactly the Open device failed! / device node missing errors you saw.
• A reboot cannot fix that. SudoVDA's node is root-enumerated, meaning it has to be explicitly created by the installer, not discovered from hardware. If it isn't there, rebooting forever won't produce it. (I previously told you a reboot might be the answer — that advice was incomplete; sorry.)

That one command will tell us definitively which situation you're in, and the fix differs a lot depending on the answer.

The audio — a different problem, and a known gap

Your Apollo-side audio config is correct and healthy. From your log:

config: 'virtual_sink' = CABLE In 16ch (VB-Audio Virtual Cable)
config: 'keep_sink_default' = disabled
config: 'auto_capture_sink' = disabled
Selected audio sink: virtual-Stereo{0.0.0.00000000}.{830e49b1-...}
Audio capture format is [F32 48000 2.0]
Opus initialized: 48 kHz, 2 channels, 96 kbps (total), LOWDELAY

The device is selected, the format negotiated, the encoder up, and there are no audio errors. So this isn't a misconfiguration — it's the gap described in issue #12, and I want to be straight with you about it rather than send you on a hunt.

Windows has exactly one machine-wide default output device, shared by the console and every seat. MultiSeat used to force that default onto the seat's virtual cable, which is what made the host go silent whenever a seat was active (#12). We removed that in the current build — seats no longer hijack the host default. The trade-off is that nothing is now forcibly pointing the seat's applications at the cable; Apollo's virtual_sink is meant to redirect the game during an active stream, and if that redirect doesn't land, the game renders to the machine default while Apollo captures the cable — so the client gets silence even though every log line looks correct.

Two things that would help me place you exactly:

1. In your Moonlight client, is "Play audio on host PC" off? If it's on, Apollo uses a different path and virtual_sink isn't used.
2. What is your Windows default playback device set to right now (Sound settings → Output)?

And on "sound not working on host": is the host silent only while a seat is running, or silent all the time? Those point at completely different causes — the first is #12, the second is more likely the VB-CABLE install having taken over your default output.

Honest status on this one: proper per-seat audio isolation — where each seat gets its own output independent of the host — is not built yet. It needs per-application audio routing (IAudioPolicyConfigFactory::SetPersistedDefaultAudioEndpoint) rather than the single machine-wide default we have today. It's the top priority on my list and it's what #12 tracks, but I don't want to imply it's a config you can flip today, because it isn't.

Summary

Symptom	Status
Wrong resolution on client	Root cause found (our bad 1000 Hz heuristic), fixed — but needs a working virtual display to actually help
No virtual display	Need your Get-PnpDevice -Class Display output to diagnose
No audio	Not a config error; known architectural gap (#12), per-seat audio not yet implemented

The resolution fix is on master now as 006a7ec — pull and re-run install-service.ps1 when convenient. Expect it to change what the log tells you, not to fix the resolution on its own; that needs the virtual display. So the Get-PnpDevice -Class Display output is the thing that unblocks the rest.

[darkjezza]

resolution still bugged

apollo.log

=== MultiSeat service log -- Application event log, last 24 h ===
[2026-08-07 00:04:47] Information Service started successfully.
[2026-08-07 00:04:48] Error Category: MultiSeat.Service.Sessions.RdpWrapper
EventId: 0

rdpwrap.ini does NOT contain an entry for build 26200. Update rdpwrap.ini from https://github.com/sebaxakerhtc/rdpwrap.ini or apply a manual patch.

[2026-08-07 00:04:48] Error Category: MultiSeat.Service.MultiSeatWorker
EventId: 0

RDP Wrapper multi-session patch not detected. Concurrent sessions will not work. Install RDP Wrapper Library and restart.

[2026-08-07 00:05:10] Error Category: MultiSeat.Service.Sessions.SeatManager
EventId: 0

Seat f20feea7-23eb-4eb6-9e8f-f77fd2952183: provisioning failed at Provisioning

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142

[2026-08-07 00:05:10] Error Category: MultiSeat.Service.MultiSeatWorker
EventId: 0

Failed to auto-provision seat 'Emulation'

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 382
at MultiSeat.Service.MultiSeatWorker.AutoProvisionSeatsAsync(CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\MultiSeatWorker.cs:line 161

[2026-08-07 00:10:19] Information Service started successfully.
[2026-08-07 00:10:19] Error Category: MultiSeat.Service.Sessions.RdpWrapper
EventId: 0

rdpwrap.ini does NOT contain an entry for build 26200. Update rdpwrap.ini from https://github.com/sebaxakerhtc/rdpwrap.ini or apply a manual patch.

[2026-08-07 00:10:19] Error Category: MultiSeat.Service.MultiSeatWorker
EventId: 0

RDP Wrapper multi-session patch not detected. Concurrent sessions will not work. Install RDP Wrapper Library and restart.

[2026-08-07 00:10:41] Error Category: MultiSeat.Service.Sessions.SeatManager
EventId: 0

Seat 953d38aa-8f09-4426-a3b7-a34f5f329ec6: provisioning failed at Provisioning

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142

[2026-08-07 00:10:41] Error Category: MultiSeat.Service.MultiSeatWorker
EventId: 0

Failed to auto-provision seat 'Emulation'

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 382
at MultiSeat.Service.MultiSeatWorker.AutoProvisionSeatsAsync(CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\MultiSeatWorker.cs:line 161

[2026-08-07 00:34:42] Information Service started successfully.
[2026-08-07 00:34:43] Error Category: MultiSeat.Service.Sessions.RdpWrapper
EventId: 0

rdpwrap.ini does NOT contain an entry for build 26200. Update rdpwrap.ini from https://github.com/sebaxakerhtc/rdpwrap.ini or apply a manual patch.

[2026-08-07 00:34:43] Error Category: MultiSeat.Service.MultiSeatWorker
EventId: 0

RDP Wrapper multi-session patch not detected. Concurrent sessions will not work. Install RDP Wrapper Library and restart.

[2026-08-07 00:35:05] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Session for Emulation timed out after 15204ms — mstsc is still running. RDP Wrapper multi-session patch may not be active — the connection may have reconnected an existing session instead of creating a new one. Check RDPConf.exe (Listener state should be 'Listening [fully supported]').

[2026-08-07 00:35:05] Error Category: MultiSeat.Service.Sessions.SeatManager
EventId: 0

Seat cb3d04ae-bee0-469b-9cc4-e8602f2a0052: provisioning failed at Provisioning

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142

[2026-08-07 00:35:05] Error Category: MultiSeat.Service.MultiSeatWorker
EventId: 0

Failed to auto-provision seat 'Emulation'

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 382
at MultiSeat.Service.MultiSeatWorker.AutoProvisionSeatsAsync(CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\MultiSeatWorker.cs:line 161

[2026-08-07 00:56:18] Information Service started successfully.
[2026-08-07 00:56:18] Error Category: MultiSeat.Service.Sessions.RdpWrapper
EventId: 0

rdpwrap.ini does NOT contain an entry for build 26200. Update rdpwrap.ini from https://github.com/sebaxakerhtc/rdpwrap.ini or apply a manual patch.

[2026-08-07 00:56:18] Error Category: MultiSeat.Service.MultiSeatWorker
EventId: 0

RDP Wrapper multi-session patch not detected. Concurrent sessions will not work. Install RDP Wrapper Library and restart.

[2026-08-07 00:56:41] Error Category: MultiSeat.Service.Sessions.SeatManager
EventId: 0

Seat 3ffcdcfc-00b4-4d32-9483-ca82cfa1c986: provisioning failed at Provisioning

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142

[2026-08-07 00:56:41] Error Category: MultiSeat.Service.MultiSeatWorker
EventId: 0

Failed to auto-provision seat 'Emulation'

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 382
at MultiSeat.Service.MultiSeatWorker.AutoProvisionSeatsAsync(CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\MultiSeatWorker.cs:line 161

[2026-08-07 00:59:05] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0
SpanId: 9690661b7edc05f8
TraceId: d8f7cd5f243069c85a677311f8e08799
ParentId: 0000000000000000

Session for Emulation timed out after 15244ms — mstsc is still running. RDP Wrapper multi-session patch may not be active — the connection may have reconnected an existing session instead of creating a new one. Check RDPConf.exe (Listener state should be 'Listening [fully supported]').

[2026-08-07 00:59:05] Error Category: MultiSeat.Service.Sessions.SeatManager
EventId: 0
SpanId: 9690661b7edc05f8
TraceId: d8f7cd5f243069c85a677311f8e08799
ParentId: 0000000000000000

Seat f2fc88a6-ce24-40a0-a1fe-fbdd004c6589: provisioning failed at Provisioning

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142

[2026-08-07 01:00:17] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0
SpanId: 2e04ef6736777961
TraceId: e9cdc218fb90460290606bda8823aa7f
ParentId: 0000000000000000

Session for Emulation timed out after 15375ms — mstsc is still running. RDP Wrapper multi-session patch may not be active — the connection may have reconnected an existing session instead of creating a new one. Check RDPConf.exe (Listener state should be 'Listening [fully supported]').

[2026-08-07 01:00:17] Error Category: MultiSeat.Service.Sessions.SeatManager
EventId: 0
SpanId: 2e04ef6736777961
TraceId: e9cdc218fb90460290606bda8823aa7f
ParentId: 0000000000000000

Seat 485e5a2c-0e55-45f3-a821-a3e6aeec9602: provisioning failed at Provisioning

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\multiseat\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142

[2026-08-07 01:00:35] Error Category: MultiSeat.Service.Sessions.RdpWrapper
EventId: 0
SpanId: baa21294644a7c7f
TraceId: bebd93b368eb175a6000f3ff32f5765b
ParentId: 0000000000000000

rdpwrap.ini does NOT contain an entry for build 26200. Update rdpwrap.ini from https://github.com/sebaxakerhtc/rdpwrap.ini or apply a manual patch.

[2026-08-07 01:00:39] Error Category: MultiSeat.Service.Sessions.RdpWrapper
EventId: 0
SpanId: 8b891faa492573f7
TraceId: 4430647be0628673339c3a4f7717b52f
ParentId: 0000000000000000

rdpwrap.ini does NOT contain an entry for build 26200. Update rdpwrap.ini from https://github.com/sebaxakerhtc/rdpwrap.ini or apply a manual patch.

[2026-08-07 01:07:28] Information Service started successfully.
[2026-08-07 01:08:49] Information Service stopped successfully.
[2026-08-07 01:09:43] Information Service started successfully.
[2026-08-07 10:44:36] Information Service stopped successfully.
[2026-08-07 10:45:01] Information Service started successfully.
[2026-08-07 10:45:19] Warning Category: MultiSeat.Service.Streaming.ApolloManager
EventId: 0

No SudoVDA display in Apollo log: 1 display(s) enumerated and the only 1000Hz match was the session's primary display — that is the RDP surface, not a virtual display. Apollo created no virtual display for this seat.

[2026-08-07 10:45:19] Warning Category: MultiSeat.Service.Sessions.SeatManager
EventId: 0

Seat e6396f4f-79be-4f0d-8487-0aefcd558238: SudoVDA display not found in Apollo log — streaming will capture primary monitor instead of virtual display

=== Helper log files in C:\ProgramData\MultiSeat\logs ===
audio-helper.log (08/07/2026 10:45:11)

--- Last 80 lines of audio-helper.log ---
[2026-08-03 13:02:33.117 +10:00] SetDefaultAudioDevice deviceId={0.0.1.00000000}.{3be81bc8-a4a0-4337-9d79-df9d8975a0f2}
SessionId=2 User=JEZZASPC\Emulation
role=0 HRESULT=0x00000000 OK
role=1 HRESULT=0x00000000 OK
role=2 HRESULT=0x00000000 OK
Result=SUCCESS
[2026-08-03 13:04:41.025 +10:00] SetDefaultAudioDevice deviceId={0.0.1.00000000}.{3be81bc8-a4a0-4337-9d79-df9d8975a0f2}
SessionId=2 User=JEZZASPC\Emulation
role=0 HRESULT=0x00000000 OK
role=1 HRESULT=0x00000000 OK
role=2 HRESULT=0x00000000 OK
Result=SUCCESS
[2026-08-05 12:41:56.221 +10:00] SetDefaultAudioDevice deviceId={0.0.1.00000000}.{3be81bc8-a4a0-4337-9d79-df9d8975a0f2}
SessionId=1 User=JEZZASPC\Jezza
role=0 HRESULT=0x00000000 OK
role=1 HRESULT=0x00000000 OK
role=2 HRESULT=0x00000000 OK
Result=SUCCESS
[2026-08-07 01:07:50.970 +10:00] SetDefaultAudioDevice deviceId={0.0.1.00000000}.{3be81bc8-a4a0-4337-9d79-df9d8975a0f2}
SessionId=2 User=JEZZASPC\Emulation
role=0 HRESULT=0x00000000 OK
role=1 HRESULT=0x00000000 OK
role=2 HRESULT=0x00000000 OK
Result=SUCCESS
[2026-08-07 01:09:54.757 +10:00] SetDefaultAudioDevice deviceId={0.0.1.00000000}.{3be81bc8-a4a0-4337-9d79-df9d8975a0f2}
SessionId=3 User=JEZZASPC\Emulation
role=0 HRESULT=0x00000000 OK
role=1 HRESULT=0x00000000 OK
role=2 HRESULT=0x00000000 OK
Result=SUCCESS
[2026-08-07 01:12:56.151 +10:00] SetDefaultAudioDevice deviceId={0.0.1.00000000}.{3be81bc8-a4a0-4337-9d79-df9d8975a0f2}
SessionId=4 User=JEZZASPC\JezzasGuest
role=0 HRESULT=0x00000000 OK
role=1 HRESULT=0x00000000 OK
role=2 HRESULT=0x00000000 OK
Result=SUCCESS
[2026-08-07 10:45:11.582 +10:00] SetDefaultAudioDevice deviceId={0.0.1.00000000}.{3be81bc8-a4a0-4337-9d79-df9d8975a0f2}
SessionId=5 User=JEZZASPC\Emulation
role=0 HRESULT=0x00000000 OK
role=1 HRESULT=0x00000000 OK
role=2 HRESULT=0x00000000 OK
Result=SUCCESS

=== Per-seat Apollo logs (pass a path to Get-Content to read one) ===
C:\ProgramData\MultiSeat\apollo\Jezza\apollo.log (08/05/2026 12:42:22)
C:\ProgramData\MultiSeat\apollo\JezzasGuest\apollo.log (08/07/2026 01:21:24)
C:\ProgramData\MultiSeat\apollo\Emulation\apollo.log (08/07/2026 10:45:37)

[vibesoftwarecoder]

That service log was worth more than the apollo.log — thanks for pasting the whole thing. It surfaced a blocker that sits underneath the resolution problem, and I don't think the resolution symptom can be trusted until it's fixed.

Start here: RDP Wrapper isn't patched for your Windows build

This is in your log at every single service start:

rdpwrap.ini does NOT contain an entry for build 26200.
RDP Wrapper multi-session patch not detected. Concurrent sessions will not work.

and then, six separate times:

RDP loopback session for 'Emulation' did not appear within timeout

with this warning alongside one of them:

Session for Emulation timed out after 15204ms — mstsc is still running. RDP Wrapper multi-session patch may not be active — the connection may have reconnected an existing session instead of creating a new one.

That last line is the important one, because it explains your resolution symptom. MultiSeat builds each seat as a new RDP loopback session. Without the RDPWrap patch Windows won't create a second session, so mstsc reconnects the one that already exists — and the "seat" ends up being your own desktop rather than an isolated session.

Which is exactly what your seat enumerated: one display, primary, 3440×1440 — your real monitor. Not a virtual display, and not a fresh session either.

So the resolution being wrong is downstream of this. I'd fix RDPWrap first; otherwise we'd be diagnosing display and audio behaviour on a substrate that isn't doing what it's supposed to.

First, an apology for that error message — it names the wrong number

Chasing this down, I found our own check was wrong, so don't go hunting for a "26200" entry.

rdpwrap.ini is keyed by termsrv.dll's file version — sections look like [10.0.26100.8737]. The Windows build number (26200) is a different identifier from a different numbering scheme. Our check was substring-searching the ini for the OS build, which is wrong in both directions: it passes on any ini that happens to contain those digits anywhere, and it would fail a perfectly-patched machine whose ini simply had no section from that branch. It's been fixed to resolve the real termsrv.dll version and look for that exact section.

So the conclusion still stands — your ini is out of date, because a current one would have matched — but the number to check is not 26200.

The fix

Same Windows build here (26200), and this machine hit the identical failure on 2026-07-14 after a Windows update replaced termsrv.dll. What fixed it:

1. Find out which termsrv.dll you actually have. Note this reads the numeric version fields, not the version string — see the warning below, it matters:

$vi = [System.Diagnostics.FileVersionInfo]::GetVersionInfo("$env:SystemRoot\System32\termsrv.dll")
"{0}.{1}.{2}.{3}" -f $vi.FileMajorPart,$vi.FileMinorPart,$vi.FileBuildPart,$vi.FilePrivatePart

⚠️ Do not use .VersionInfo.FileVersion or the file's Properties → Details tab for this. Windows servicing updates the binary version resource but leaves the human-readable string block stale, so they disagree on a patched machine. On this host the string says 10.0.26100.8115 while the numeric fields say 10.0.26100.8737 — and 8737 is the truth (I confirmed by hashing the DLL against the WinSxS copies). Look up the string version and you'll be checking for a termsrv.dll that isn't installed. This cost me a day.

2. Delete the cached ini. This matters — install-prerequisites.ps1 prefers an rdpwrap.ini sitting next to the script over downloading a fresh one, so if there's a stale copy there from an earlier run, re-running just re-copies the same stale file:

Remove-Item .\prerequisites\rdpwrap.ini -ErrorAction SilentlyContinue

3. Re-run the prereq script. It refreshes the ini from sebaxakerhtc/rdpwrap.ini (the actively-maintained one — the ini bundled with RDPWrap v1.6.2 stopped being updated in 2017) and restarts TermService so the new offsets take effect:

.\prerequisites\install-prerequisites.ps1

4. Confirm the ini actually covers your DLL, substituting the version from step 1:

Select-String -Path 'C:\Program Files\RDP Wrapper\rdpwrap.ini' -Pattern '^\[10\.0\.26100\.8737\]'

The current upstream ini is 555,632 bytes. If yours is much smaller, the download didn't work — grab it manually into C:\Program Files\RDP Wrapper\rdpwrap.ini.

For reference, I checked upstream today: the ini's most recent change was 2026-08-02, and it covers the whole current 26100 branch (.8521, .8544, .8690, .8737, .8749). If your termsrv version isn't in that list, you may be on a build newer than upstream has offsets for, which is a different conversation — tell me the version and we'll go from there.

5. Verify it's live:

• RDPConf.exe — Listener state should read Listening [fully supported]
• Then the real test, with a seat running: qwinsta should show two sessions in Active state (your console session plus the seat's)

If RDPConf still shows [not supported] after all that, paste what it reports and I'll take a look.

Your log confirms the parser fix works

This is from your 10:45 run, so you're on the new build:

No SudoVDA display in Apollo log: 1 display(s) enumerated and the only 1000Hz match was the session's primary display — that is the RDP surface, not a virtual display. Apollo created no virtual display for this seat.

That's 006a7ec doing its job. Before it, MultiSeat would have grabbed that same 3440×1440 primary display, written it into Apollo's output_name, and reported success — silently. Now it says what's actually true.

As I flagged last time, this doesn't fix your resolution on its own, and it wasn't going to. It removes the false success that was hiding the real problem: no virtual display is being created on your machine.

Worth pulling latest master again when convenient — two fixes since your build, neither of which will change your symptoms but both of which make the diagnostics you're sending me trustworthy:

• 2467d4b — MultiSeat could read a stale Apollo log from a previous run instead of the live one, because it trusted a cached file size that Windows doesn't update while a file is being written.
• 35605ca — the rdpwrap.ini check described above, which now validates against the real termsrv.dll version instead of the OS build number.

Still need one thing from you

I've asked twice and I think it's just got lost in the noise, so — this one command, from an elevated PowerShell:

Get-PnpDevice -Class Display | Format-Table Status,FriendlyName,InstanceId -AutoSize

This is the only thing blocking the next step, and here's why it's worth the 10 seconds:

There are two different virtual display drivers in play. SudoVDA (SudoMaker) is the one MultiSeat looks for by default. Apollo also ships its own Sunshine Virtual Display Driver — a completely separate INF package with its own device node. On this machine I found SudoVDA had no device node at all while the Sunshine VDD was present and working, and Apollo has a config key that points it at the second one instead:

dd_use_sunshine_virtual_display_driver = enabled

On this box that key made Apollo stop hunting for the absent SudoVDA and target the driver that actually exists. I'm holding it unshipped because it ran into a separate problem here (another Apollo instance already owns that adapter, so the seat's instance can't restart it), and I don't want to ship a key that helps one machine and confuses another.

If your display list shows a Sunshine VDD node, that key is a strong candidate for your machine and it's a one-line change. If it shows neither driver, the answer is different — you'd need the driver installed first. I genuinely can't tell which without the output.

The audio

Haven't forgotten it — you mentioned sound not working on host or client. That's a known architectural gap rather than a quick fix: seats currently share the host's audio devices instead of each getting their own session-isolated endpoint. It's tracked in #12, it's the next significant piece of work, and I'd rather fix your session isolation first since audio behaviour on a session that isn't actually isolated won't tell either of us much.

tl;dr: clear the cached ini → re-run prereqs → confirm Listening [fully supported] → send me the Get-PnpDevice -Class Display output.

[darkjezza]

apollo.log

Status FriendlyName InstanceId

---

OK Virtual Display Driver ROOT\DISPLAY\0000
OK SudoMaker Virtual Display Adapter ROOT\DISPLAY\0001
OK Sunshine Virtual Display Driver ROOT\DISPLAY\0002
OK NVIDIA GeForce RTX 4080 PCI\VEN_10DE&DEV_2704&SUBSYS_168819DA&REV_A1\4&D0BDF66&0&0009
Unknown Microsoft Remote Display Adapter SWD\REMOTEDISPLAYENUM\RDPIDD_INDIRECTDISPLAY&SESSIONID_0001
OK AMD Radeon(TM) Graphics PCI\VEN_1002&DEV_164E&SUBSYS_D0001458&REV_CB\4&16012499&0&0041
OK NVIDIA GeForce GTX 1660 SUPER PCI\VEN_10DE&DEV_21C4&SUBSYS_13D310DE&REV_A1\6&1C1C48D1&0&00400011

PS
C:\Users\Jezza\Desktop\MultiSeat> .\scripts\show-logs.ps1
=== MultiSeat service log -- Application event log, last 24 h ===
[2026-08-10 10:31:59] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:32:04] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:32:09] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:32:14] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:32:19] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:32:24] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:32:29] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:32:34] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:32:39] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:32:44] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:32:49] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:32:54] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:32:59] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:33:04] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:33:09] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:33:14] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:33:19] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:33:24] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:33:29] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:33:34] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:33:39] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:33:44] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:33:49] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:33:54] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:33:59] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:34:04] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:34:09] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:34:14] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:34:19] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:34:24] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:34:29] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:34:34] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:34:39] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:34:44] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:34:49] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:34:54] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:34:59] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:35:04] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:35:09] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:35:14] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:35:19] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:35:24] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:35:29] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:35:34] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:35:39] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 10:35:44] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

Keepalive process for session 2 exited, but WTS session is still active

[2026-08-10 17:01:38] Information Service started successfully.
[2026-08-10 17:02:23] Warning Category: MultiSeat.Service.Streaming.ApolloManager
EventId: 0

No SudoVDA display in Apollo log: 1 display(s) enumerated and the only 1000Hz match was the session's primary display — that is the RDP surface, not a virtual display. Apollo created no virtual display for this seat.

[2026-08-10 17:02:23] Warning Category: MultiSeat.Service.Sessions.SeatManager
EventId: 0

Seat b9d6f663-6ad9-433c-9536-bcc572f578f0: SudoVDA display not found in Apollo log — streaming will capture primary monitor instead of virtual display

[2026-08-10 17:16:38] Warning Category: MultiSeat.Service.Monitoring.SessionHealthCheck
EventId: 0

Seat b9d6f663-6ad9-433c-9536-bcc572f578f0: session 2 is Disconnected (PC may have slept) — reconnecting

[2026-08-10 17:16:45] Warning Category: MultiSeat.Service.Streaming.ApolloManager
EventId: 0

Seat b9d6f663-6ad9-433c-9536-bcc572f578f0: restarting Apollo (attempt 1/3)

[2026-08-10 17:16:47] Warning Category: MultiSeat.Service.Sessions.SeatManager
EventId: 0

Seat b9d6f663-6ad9-433c-9536-bcc572f578f0: skipping display isolation — DisplayDevicePath is unset, TermService CPU may be elevated

[2026-08-10 17:46:33] Warning Category: MultiSeat.Service.Monitoring.SessionHealthCheck
EventId: 0

Seat b9d6f663-6ad9-433c-9536-bcc572f578f0: session 2 is Disconnected (PC may have slept) — reconnecting

[2026-08-10 17:46:33] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

cmdkey exited with code -1073741502 during reconnect for Emulation

[2026-08-10 17:46:33] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0

PowerShell exited with code -1073741502 writing Default.rdp — mstsc may still show a dialog if the file wasn't updated

[2026-08-10 17:47:19] Information Service started successfully.
[2026-08-10 17:47:40] Warning Category: MultiSeat.Service.Streaming.ApolloManager
EventId: 0

No SudoVDA display in Apollo log: 1 display(s) enumerated and the only 1000Hz match was the session's primary display — that is the RDP surface, not a virtual display. Apollo created no virtual display for this seat.

[2026-08-10 17:47:40] Warning Category: MultiSeat.Service.Sessions.SeatManager
EventId: 0

Seat 7aa76b01-c5f5-42bf-a22e-fbbe8275a0b7: SudoVDA display not found in Apollo log — streaming will capture primary monitor instead of virtual display

[2026-08-10 17:54:15] Warning Category: MultiSeat.Service.Monitoring.SessionHealthCheck
EventId: 0

Seat 7aa76b01-c5f5-42bf-a22e-fbbe8275a0b7: session 2 is Disconnected (PC may have slept) — reconnecting

[2026-08-10 17:54:21] Warning Category: MultiSeat.Service.Streaming.ApolloManager
EventId: 0

Seat 7aa76b01-c5f5-42bf-a22e-fbbe8275a0b7: restarting Apollo (attempt 1/3)

[2026-08-10 17:54:23] Warning Category: MultiSeat.Service.Sessions.SeatManager
EventId: 0

Seat 7aa76b01-c5f5-42bf-a22e-fbbe8275a0b7: skipping display isolation — DisplayDevicePath is unset, TermService CPU may be elevated

[2026-08-10 17:54:45] Information Service stopped successfully.
[2026-08-10 17:55:35] Information Service started successfully.
[2026-08-10 17:55:48] Warning Category: MultiSeat.Service.Streaming.ApolloManager
EventId: 0

No SudoVDA display in Apollo log: 1 display(s) enumerated and the only 1000Hz match was the session's primary display — that is the RDP surface, not a virtual display. Apollo created no virtual display for this seat.

[2026-08-10 17:55:48] Warning Category: MultiSeat.Service.Sessions.SeatManager
EventId: 0

Seat 641bd25e-3048-42f1-b119-b54f7db4b12d: SudoVDA display not found in Apollo log — streaming will capture primary monitor instead of virtual display

[2026-08-10 17:56:53] Information Service stopped successfully.
[2026-08-11 03:20:00] Information Service started successfully.
[2026-08-11 03:20:01] Error Category: MultiSeat.Service.Sessions.RdpWrapper
EventId: 0

rdpwrap.ini has no [10.0.26100.8737] section, so it carries no offsets for the termsrv.dll installed on this machine — multi-session will not work. Update rdpwrap.ini from https://github.com/sebaxakerhtc/rdpwrap.ini and restart TermService. (Note: termsrv.dll's FileVersion STRING may report a different, stale version — 10.0.26100.8737 is from the binary version fields.)

[2026-08-11 03:20:01] Error Category: MultiSeat.Service.MultiSeatWorker
EventId: 0

RDP Wrapper multi-session patch not detected. Concurrent sessions will not work. Install RDP Wrapper Library and restart.

[2026-08-11 03:24:16] Error Category: MultiSeat.Service.Sessions.RdpWrapper
EventId: 0
SpanId: 2196b289cba225ad
TraceId: 87152fb01ec9508eba1588f6c8077791
ParentId: 0000000000000000

rdpwrap.ini has no [10.0.26100.8737] section, so it carries no offsets for the termsrv.dll installed on this machine — multi-session will not work. Update rdpwrap.ini from https://github.com/sebaxakerhtc/rdpwrap.ini and restart TermService. (Note: termsrv.dll's FileVersion STRING may report a different, stale version — 10.0.26100.8737 is from the binary version fields.)

[2026-08-11 03:24:21] Error Category: MultiSeat.Service.Sessions.RdpWrapper
EventId: 0
SpanId: cdde09df961e8f21
TraceId: 20a3c25ddf9c59c7dafc538a7034e566
ParentId: 0000000000000000

rdpwrap.ini has no [10.0.26100.8737] section, so it carries no offsets for the termsrv.dll installed on this machine — multi-session will not work. Update rdpwrap.ini from https://github.com/sebaxakerhtc/rdpwrap.ini and restart TermService. (Note: termsrv.dll's FileVersion STRING may report a different, stale version — 10.0.26100.8737 is from the binary version fields.)

[2026-08-11 03:24:26] Error Category: MultiSeat.Service.Sessions.RdpWrapper
EventId: 0
SpanId: 0b0d50c3b7664e35
TraceId: 66b1ac8005dfc1c274fa5519f246d509
ParentId: 0000000000000000

rdpwrap.ini has no [10.0.26100.8737] section, so it carries no offsets for the termsrv.dll installed on this machine — multi-session will not work. Update rdpwrap.ini from https://github.com/sebaxakerhtc/rdpwrap.ini and restart TermService. (Note: termsrv.dll's FileVersion STRING may report a different, stale version — 10.0.26100.8737 is from the binary version fields.)

[2026-08-11 03:25:11] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0
SpanId: 04ece7be77ed72b1
TraceId: 43b9327e55b7d0e6b58929fdf4e69e2d
ParentId: 0000000000000000

Session for Emulation timed out after 15490ms — mstsc is still running. RDP Wrapper multi-session patch may not be active — the connection may have reconnected an existing session instead of creating a new one. Check RDPConf.exe (Listener state should be 'Listening [fully supported]').

[2026-08-11 03:25:11] Error Category: MultiSeat.Service.Sessions.SeatManager
EventId: 0
SpanId: 04ece7be77ed72b1
TraceId: 43b9327e55b7d0e6b58929fdf4e69e2d
ParentId: 0000000000000000

Seat cdab095c-2a97-4ddc-8301-5558009c138a: provisioning failed at Provisioning

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142

[2026-08-11 03:26:43] Warning Category: MultiSeat.Service.Sessions.SessionLauncher
EventId: 0
SpanId: 0be2f1640e72f997
TraceId: 58ad32afd13ebd014ae52b007885fb1d
ParentId: 0000000000000000

Session for Emulation timed out after 15220ms — mstsc is still running. RDP Wrapper multi-session patch may not be active — the connection may have reconnected an existing session instead of creating a new one. Check RDPConf.exe (Listener state should be 'Listening [fully supported]').

[2026-08-11 03:26:43] Error Category: MultiSeat.Service.Sessions.SeatManager
EventId: 0
SpanId: 0be2f1640e72f997
TraceId: 58ad32afd13ebd014ae52b007885fb1d
ParentId: 0000000000000000

Seat a7ea1eae-7bd1-444c-b006-79f7c5503533: provisioning failed at Provisioning

Exception:
System.InvalidOperationException: RDP loopback session for 'Emulation' did not appear within timeout. Check the service log for the mstsc exit code logged above. Steps to diagnose: (1) Re-run prerequisites\install-prerequisites.ps1 to refresh rdpwrap.ini for your Windows build. (2) Open RDPConf.exe and verify Listener state is 'Listening [fully supported]'. (3) Manually run: mstsc /v:127.0.0.2 and log in as the seat account to verify RDP works. (4) Check HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp: UserAuthentication must be 0.
at MultiSeat.Service.Sessions.SessionLauncher.CreateSessionViaRdpLoopbackAsync(String accountName, String password, CancellationToken ct) in C:\Users\Jezza\Desktop\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 505
at MultiSeat.Service.Sessions.SessionLauncher.LaunchSessionAsync(String accountName, CancellationToken ct) in C:\Users\Jezza\Desktop\MultiSeat\src\MultiSeat.Service\Sessions\SessionLauncher.cs:line 166
at MultiSeat.Service.Sessions.SeatManager.ProvisionSeatAsync(SeatRequest request, CancellationToken ct) in C:\Users\Jezza\Desktop\MultiSeat\src\MultiSeat.Service\Sessions\SeatManager.cs:line 142

[2026-08-11 03:28:58] Information Service started successfully.
[2026-08-11 03:30:04] Warning Category: MultiSeat.Service.Streaming.ApolloConfigBuilder
EventId: 0
SpanId: fc3998ffb6d332e7
TraceId: 63f069e89936681605008b5d0fe8c129
ParentId: 0000000000000000

No shared credentials found at C:\ProgramData\MultiSeat\apollo\shared_credentials.json. Visit the Apollo web UI after provisioning a seat to create credentials, then the file will persist for future seats.

[2026-08-11 03:30:12] Warning Category: MultiSeat.Service.Streaming.ApolloManager
EventId: 0
SpanId: fc3998ffb6d332e7
TraceId: 63f069e89936681605008b5d0fe8c129
ParentId: 0000000000000000

No SudoVDA display in Apollo log: 1 display(s) enumerated and the only 1000Hz match was the session's primary display — that is the RDP surface, not a virtual display. Apollo created no virtual display for this seat.

[2026-08-11 03:30:12] Warning Category: MultiSeat.Service.Sessions.SeatManager
EventId: 0
SpanId: fc3998ffb6d332e7
TraceId: 63f069e89936681605008b5d0fe8c129
ParentId: 0000000000000000

Seat 254df40b-5a5d-4072-ac4d-61c7876d8d18: SudoVDA display not found in Apollo log — streaming will capture primary monitor instead of virtual display

=== Helper log files in C:\ProgramData\MultiSeat\logs ===
audio-helper.log (08/11/2026 03:30:04)

--- Last 80 lines of audio-helper.log ---
[2026-08-11 03:30:04.831 +10:00] SetDefaultAudioDevice deviceId={0.0.1.00000000}.{3be81bc8-a4a0-4337-9d79-df9d8975a0f2}
SessionId=2 User=JEZZASPC\Emulation
role=0 HRESULT=0x00000000 OK
role=1 HRESULT=0x00000000 OK
role=2 HRESULT=0x00000000 OK
Result=SUCCESS

=== Per-seat Apollo logs (pass a path to Get-Content to read one) ===
C:\ProgramData\MultiSeat\apollo\Emulation\apollo.log (08/11/2026 03:30:42)

[vibesoftwarecoder]

Sorry for the wait. Several things you have been hitting are now fixed, and one of them is a warning
that has been actively wasting your time — I'll start there, because it changes what you should be
chasing.

Stop chasing the SudoVDA warnings. They describe normal behaviour.

These two, which appear on every provision in your logs:

No SudoVDA display in Apollo log: 1 display(s) enumerated and the only 1000Hz match was
the session's primary display — that is the RDP surface, not a virtual display.
Seat …: SudoVDA display not found in Apollo log — streaming will capture primary monitor
instead of virtual display

A seat never gets its own virtual display, on any host, including mine. Windows does not let a
virtual display created in the console session join an RDP session's topology — the monitor is
created, it attaches to the console desktop, and the seat enumerates zero. @jmlopezdona measured
this properly in #15 with a control that makes it conclusive, and it is worth reading if you want the
detail.

So your Get-PnpDevice output showing SudoMaker Virtual Display Adapter ROOT\DISPLAY\0001 is
correct, SudoVDA is installed on your machine, and it changes nothing. The second warning claimed a
fault where there is none; it cost José two days, and from your logs I think it has been costing you
too. That is on me. It is fixed in 094d51b
— the message is now accurate and no longer a warning, and REQUIREMENTS.md no longer implies a seat
will get its own display.

The same goes for skipping display isolation — DisplayDevicePath is unset: downstream of the same
thing, and not a fault you can fix by reinstalling drivers.

What this means for your resolution symptom: the seat streams its RDP session surface, so the
resolution you get is the geometry mstsc connected with. It cannot be changed from inside the
session — Apollo's [1610] failed to set display mode! is that, not a driver problem. José has a
working approach in #15 (set desktopwidth/desktopheight + DPI in the .rdp file, driven on
connect). MultiSeat does not do that yet; it is the next thing I want to land.

Your actual blocker: rdpwrap.ini has no offsets for your termsrv.dll

This is in your log at every service start, and everything else follows from it:

rdpwrap.ini has no [10.0.26100.8737] section, so it carries no offsets for the termsrv.dll
installed on this machine — multi-session will not work.
RDP loopback session for 'Emulation' did not appear within timeout

Without the patch Windows will not create a second session, so mstsc reconnects the existing one
and provisioning times out. The fix is to replace rdpwrap.ini with the current one from
sebaxakerhtc/rdpwrap.ini — it carries 10.0.26100.8737
and a good deal beyond it — then restart TermService:

Stop-Service TermService -Force
# back up and replace C:\Program Files\RDP Wrapper\rdpwrap.ini with the upstream one
Start-Service TermService

For what it is worth, this is not something you did wrong and it is not rare: the same break has hit
me twice more since we last spoke, most recently when a Windows update moved my termsrv.dll to
10.0.26100.8972. It recurs every time servicing touches that binary.

If you would rather stop fighting it permanently, José swapped RDP Wrapper for
TermWrap, which finds the offsets by disassembling termsrv.dll
instead of reading them from an ini, and it survived a build bump on his host with no intervention.
MultiSeat now detects it properly — see below.

Fixes shipped since your last post

• 474553d — patch detection no
  longer requires the literal string rdpwrap in TermService's ServiceDll, so TermWrap is
  recognised instead of being reported as "patch not detected" while sessions are running. Also
  fixes a race you have in your logs: Service started successfully at 03:20:00 and patch not detected at 03:20:01 — MultiSeat is auto-start and was judging TermService before it had
  finished starting. It now waits for it.
• 094d51b — the misleading display
  warnings above.
• bc445ee — seats no longer inherit
  "virtual-display": true from the console's apps.json, which was making Apollo attempt a display
  creation on every connect and leave a phantom monitor behind in the console user's display list
  each time.
• 8962efb — per-session audio,
  which is probably relevant to the "sound not working on host or client" you reported. Setting
  "AudioMode": "PerSession" in appsettings.json drops VB-CABLE and VoiceMeeter from the picture
  entirely: the RDP session keeps its own audio endpoint and Apollo captures that. Two things to know
  — the Moonlight client's "Play audio on host PC" must be ON for this mode (the opposite of the
  default mode), and there is no microphone support in it. Default is unchanged, so you have to
  opt in.

One more thing, about the logs you have been sending me

Every LogInformation the service wrote was being silently discarded — AddWindowsService() pins the
Event Log provider to Warning and above, and the setting that was supposed to override it did not,
because provider-specific filter rules outrank category ones. You can see it in your own pastes:
every MultiSeat.Service entry is a Warning or an Error, and the only Information lines come from the
service-lifecycle source.

So the logs you sent were structurally missing the startup sequence, the patch detection detail, the
per-seat provisioning steps, the ports, and the audio mode — all the context that makes the failures
legible. That was my end, not yours, and it is fixed in
1857e0b. Pull master and redeploy
and the next show-logs.ps1 will be far more useful.

Suggested order: fix rdpwrap.ini first and confirm a seat actually provisions (a second Active
session in query session), then redeploy master, then try AudioMode: PerSession if sound is
still wrong. The display warnings you can now ignore entirely.