getting this on new 6.0.1

[darkjezza]

RDP loopback session for 'GuestJezza' 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.

in system

it says RDP Wrapper inactive — multi-session unavailable

RDP Wrapper inactive

ApiBindLoopbackOnly = True <- appsettings.json
ApiKey = (empty) <- appsettings.json
ApiPort = 9550 <- appsettings.json
ApolloConfigDir = C:\ProgramData\MultiSeat\apollo <- appsettings.json
ApolloExePath = C:\Program Files\ApolloVibe\sunshine.exe <- appsettings.json
ApolloLogLevel = info (default - no config file set it)
AudioMode = PerSession <- appsettings.json
AutoAssignControllers = True <- appsettings.json
CorsOrigins = (empty) <- appsettings.json
EnableEmulatorNetplay = True <- appsettings.json
EnableHdr = False (default - no config file set it)
EnableHidHideCloaking = False <- appsettings.json
EnableKeyboardMouseIsolation = False <- appsettings.json
EnablePadRulePreWrite = False <- appsettings.json
EnableSharedGameLibrary = True <- appsettings.json
EnableViGEmController = False (default - no config file set it)
Encoder = nvenc (default - no config file set it)
FollowClientResolution = False (default - no config file set it)
GrantSeatAdministrator = False (default - no config file set it)
HealthCheckIntervalMs = 5000 <- appsettings.json
HidHideCliPath = C:\Program Files\Nefarius Software Solutions\HidHide\x64\HidHideCLI.exe <- appsettings.json
InputHookDllPath = MultiSeatInputHook.dll <- appsettings.json
KeepaliveOnSeparateDesktop = True (default - no config file set it)
KillLaunchOnConnectAppsOnDisconnect = False <- appsettings.json
LaunchOnConnect = (empty) <- appsettings.json
LaunchOnConnectDelayMs = 4000 <- appsettings.json
MaxSeats = 4 <- appsettings.json
NvencPreset = 4 <- appsettings.json
PortBase = 48100 <- appsettings.json
ProcessLaunchTimeoutMs = 10000 <- appsettings.json
RetroArchConfigPath = (empty) <- appsettings.json
RotateSharedSeatTls = False (default - no config file set it)
SeatPadDevicePaths = (empty) <- appsettings.json
SeedRetroArchNetplayConfig = False <- appsettings.json
SessionConnectTimeoutMs = 15000 <- appsettings.json
SharedGameLibraryDir = C:\MultiSeatGames <- appsettings.json
SourceDir = (empty) (default - no config file set it)
VacCableCount = 4 <- appsettings.json
VerifyHidHideJail = True <- appsettings.json

[vibesoftwarecoder]

The line that matters in your paste is not the timeout, it's this one:

RDP Wrapper inactive — multi-session unavailable

Every MultiSeat seat is an RDP session, so while RDPWrap is inactive no seat can start at all. The timeout and the four diagnostic steps above it are aimed a level below the real cause. Your --config output looks fine otherwise — nothing misconfigured there.

Two things produce that message: the prerequisite installer never ran, or it ran but rdpwrap.ini has no section for your Windows build. This one command tells us which, and it's already in the zip you downloaded:

.\scripts\check-rdpwrap-offsets.ps1

Run it from the extracted 0.6.1 folder and paste the output. If it reports your build as uncovered, -Generate will compute the offsets locally and -Apply will merge them in, so you are not waiting on anyone else's release.

Also worth knowing: if you installed from the zip and ran only install-service.ps1, the drivers step is separate and still required —

.\prerequisites\install-prerequisites.ps1

That is the script that installs RDPWrap and keeps rdpwrap.ini current. Thanks for the report — install-service.ps1 currently checks for SudoVDA and the audio cables but not for RDPWrap, which is the one thing nothing works without. That's a gap on our side and I'm fixing it.

[vibesoftwarecoder]

We hit this ourselves, on our own machine, a few hours after answering you — and it was the second of the two causes.

A Windows update replaced termsrv.dll and moved it to a build the RDP Wrapper config had no entry for. RDP Wrapper was still installed and still looked fine; it just silently stopped patching. Every seat on that host had been unable to start for two days and nothing said so.

That is very likely what you are looking at. The version number will differ on your machine — ours was 10.0.26100.9444 — but the shape is the same: an update lands, the offsets move, rdpwrap.ini no longer covers the running build, and every seat dies with it because a seat is an RDP session.

The fix, which we ran and confirmed works:

.\scripts\check-rdpwrap-offsets.ps1

If it reports your build as not covered, this repairs it:

.\scripts\check-rdpwrap-offsets.ps1 -Apply

That computes the correct offsets from your own termsrv.dll, backs up rdpwrap.ini before changing it, merges the new section in, and restarts the Terminal Services service. It does not wait for the community config to catch up, which is the part that used to leave people stuck for days.

On our host that took about ten seconds, and a seat provisioned immediately afterwards. If it does not fix yours, paste the output of the first command and we will take it from there — a backup path is printed if you need to undo it.

One thing worth knowing about the version number: termsrv.dll reports two different versions and only one of them is the one RDP Wrapper uses. The script reads the correct one. If you have been comparing versions by hand, that is a good way to conclude you are covered when you are not.

0.6.2 makes this visible instead of silent. The installer now checks RDP Wrapper before it finishes and says outright that no seat will start if it is inactive, and the seat timeout you hit now names this as the cause rather than listing it as one suggestion among four. That change exists because of your report.