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
Is your issue present in the latest beta/pre-release?
This issue is present in the latest pre-release
Describe the Bug
The Moonlight client (Apple TV 4K) consistently fails to connect with the host (windows 11 24h2), eventually displaying the message to check if the display is plugged in and turned on. On the Sunshine webUI, I get two errors:
Fatal: Unable to find display or encoder during startup.
Fatal: Please ensure your manually chosen GPU and monitor are connected and powered on.
The only fix is to MANUALLY restart Sunshine from the host (Delayed start on the Sunshine Service doesn't work)
Expected Behavior
I expect moonlight client to be able to connect with the Windows 11 24h2 host. I have reliably used Moonlight + Sunshine for years, and nothing has changed except for updating to Windows 11 24H2 and using the Nvidia App
Additional Context
Steps I have tried (but no dice!):
re-installed windows 11 24h2 thrice
tried manually setting up sunshine as a startup app, disabling the service
tried delayed start on the Sunshine service
NOTE: As always I have been using Nonary's Resolution Automation v3.0. The issues persists without Nonary's mod.
The only fix is to manually restart moonlight. Fix works consistently.
Hey there, so the problem is with the Sunshine Service. Not sure how things work on the Ubuntu end but with Windows the problem goes away as long as the Sunshine service is delayed a start from a cold boot (this is becoming impossible to accomplish as the AutoDelayedStart reg edit seems to be broken on Windows 11).
The only recourse is to use a remote setup like Unified Remote to do a system restart (NOT a shutdown-startup, but a restart EACH time you cold start your machine)
TL;DR: post cold start, try restarting your system using a remote restart utility as that seems to work on Windows 11. The problem is with the Sunshine Service which starts too soon on cold boots and has no way of delaying its start (Delayed Start will not work).
A painful but working workaround I have had success with is using Remmina. Log into a RDP session, and start/restart sunshine from the RDP session. If you have trouble connecting with the name of the computer in Remmina, you can use moonlight to get the IP of the computer, put that in the server field of Remmina, connect, restart sunshine, exit RDP, connect via moonlight.
Is there an existing issue for this?
Is your issue described in the documentation?
Is your issue present in the latest beta/pre-release?
This issue is present in the latest pre-release
Describe the Bug
The Moonlight client (Apple TV 4K) consistently fails to connect with the host (windows 11 24h2), eventually displaying the message to check if the display is plugged in and turned on. On the Sunshine webUI, I get two errors:
Fatal: Unable to find display or encoder during startup.
Fatal: Please ensure your manually chosen GPU and monitor are connected and powered on.
The only fix is to MANUALLY restart Sunshine from the host (Delayed start on the Sunshine Service doesn't work)
Expected Behavior
I expect moonlight client to be able to connect with the Windows 11 24h2 host. I have reliably used Moonlight + Sunshine for years, and nothing has changed except for updating to Windows 11 24H2 and using the Nvidia App
Additional Context
Steps I have tried (but no dice!):
NOTE: As always I have been using Nonary's Resolution Automation v3.0. The issues persists without Nonary's mod.
The only fix is to manually restart moonlight. Fix works consistently.
Host Operating System
Windows
Operating System Version
24H2 (OS Build 26100.2605)
Architecture
amd64/x86_64
Sunshine commit or version
v2024.1211.191744
Package
Windows - installer (recommended)
GPU Type
NVIDIA
GPU Model
GeForce RTX 4090
GPU Driver/Mesa Version
566.36
Capture Method
None
Config
Apps
No response
Relevant log output
The text was updated successfully, but these errors were encountered: