You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Can't connect after computer reboot if there's global_prep_cmd set #6024
Is your issue present in the latest beta/pre-release?
This issue is present in the latest pre-release
Describe the Bug
When the computer is at the login screen after a reboot (so nobody had logged in yet), starting "Desktop" via Moonlight fails with "Failed to start the specified application (Error 0)" (it's probably -1 but Moonlight displays it wrongly). This used to work fine before, I only notice it now after updating to own build made from d0b4a88 (#5782).
When I clear the global_prep_cmd in sunshine.conf then I'm able to connect. This worked before by ignoring the failed execution of prep command.
Expected Behavior
Moonlight connects to the computer that rebooted and is at login screen, and has global_prep_cmd populated in sunshine.conf
Before it, child.wait() didn't take an error argument and the exit code check skipped permission_denied, so the leftover permission error from the prep command that never started was ignored and the launch continued.
Host Operating System
Windows
Operating System Version
10 22H2 19045.7807
Architecture
amd64/x86_64
Package
other (self built)
GPU Type
NVIDIA
GPU Model
1050 ti
GPU Driver/Mesa Version
582.78
Capture Method
None
Apps
Log output
Debug: QueryUserToken failed, this would prevent commands from launching under the users profile.
Error: Couldn't run [c:\scripts\ss_start.bat]: System: Permission deniedError: [c:\scripts\ss_start.bat] wait failed with error code [generic:13]
Activity
ReenigneArcher commentedon Oct 31, 2026
Can you actually replicate this in our latest stable or beta?
bgr commentedon Oct 31, 2026
Yes.
ReenigneArcher commentedon Nov 2, 2026
Can you test if the issue is resolved with #6030 ?
bgr commentedon Nov 2, 2026
Tested, works fine now. I cherry-picked the fix onto my branch and made sure that no users are signed in, it connected: