[ERROR] Fatal: Unable to find display or encoder during startup (Windows 24H2) #3447
Comments
|
Having this issue on Ubuntu 24.04.1 LTS |
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. |
|
Same issue on Windows 11 Pro 24H2. |
ReenigneArcher
changed the title
|
Can confirm this issue is exclusive to 24H2, for the moment it is struggling with being able to stream from a Lock Screen. I’m honestly not sure what can be done to fix this issue for now other than to suggest users to revert back to 23H2 for the time being. Sunshine uses the windows API to capture the screen, therefore if it is broken, it would need to be fixed on Microsoft’s side. As far as I’m aware they have not published any new guidelines for DXGI for developers. |
|
Just for info I'm running Windows 11 Pro 21H2 and I too have this issue. |
Likely not the same issue. This issue can also happen on laptops with hybrid graphics, but it’s not the same. |
|
Hm, if you're sure that's good to know. |
Don't open a new issue, post the logs and question on either the sunshine discord or moonlight one in sunshine channel. Issues are meant for confirmed bugs essentially, as opposed to technical support. |
Duly noted, thanks. |
Hi Nonary, I use many of your tools! THANK YOU! I want to stress that mine isn’t a lock-screen issue. I use Autologon bypassing lockscreen. This seems to be a sunshine service issue, and specifically at COLD START. A restart right after a cold start fixes the issue. NOTE: Delaying a service and task scheduler is fundamentally broken in 24H2 so there is no ready fix. However, I tried a bunch of unorthodox things to zero down to the Sunshine Service. Here is what I tried:
TL;DR: this issue has something to do with the Sunshine Service and the way it starts at cold boots (win 11 24H2). I think it is loading before any dependencies at cold start. For some reason this behavior is not repeated when the system is restarted. For those experiencing this issue, use Unified Remote to initiate a restart following a complete cold boot. |
|
An easier solution is probably a scheduled task that restarts the service automatically once the computer boots up (even before login is complete) would probably work. Or have a scheduled task start the service, instead having it start automatically. |
I've seen the issue occur even after restarting the service shortly after a cold boot, sometimes leading to errors like 0x887A0005 (access denied)—especially when it's at the lock screen. Honestly, I’m not sure how to fix this since DXGI is part of the Windows API. Microsoft will likely address these issues over time or release documentation for developers on how to handle or work around them (if there's a new intended method going forward). For now, if you need maximum stability, I recommend reverting back to 23H2 as soon as possible. |
I tried this. Here is what happens:
|
|
Updating this thread with a fix: Turn off Fast boot. cold boot works fine consistently. Tried it numerous times. DISREGARD previous fixes. Further (non-scientific) testing shows that SunshineService’s uber-aggressive startup behavior causes issues at cold boot. 24H2 may have changed some fast boot parameters which don’t work well with SunshineService at cold boot. Suggestion: put some sort of a startup timer option in Sunshine app. Seems like this issue has been discussed on Reddit as well, way before 24H2 so happens with certain software/hardware setups. @erwan-privat tagging you here as your solution was downright painful. Hope this works for you. |
|
@Sinmurv Cold boot doesn't actually free RAM from loaded NT kernel and other important things for Windows. A restart on the other hand is the actual HARD RESET for the system. |
This is very interesting! Switching off fast boot fixed the issue for me. Is that related to what you are saying? My uneducated guess would be that it does, and that’s why it fixed my cold boot Sunshine woes |
|
I am not really convinced it has anything to do with fast boot or services, I still think it is DXGI bugs and the issue is likely to return |
I have been testing this for the last 36 hours. It is the service, and there are threads on Reddit pre-dating 23H2 talking about either same or similar problems. The service was also the culprit then in those cases. Again, this is very much system dependent so YMMV. I turn on fast boot, the issue comes back with every cold boot without fail. I turn off fast boot, the issue goes away and the system streams happily. Both ways the result is 100% consistent. The tip off for me was that at cold boot, with fast boot on, the Sunshine service despite being set to manual would be one of the first services to turn on completely circumventing the task scheduler delay parameters of 60 seconds. Fast boot, on or off, doesn’t affect restarts so the behavior with restart was consistent either way. Task scheduler would work fine and Sunshine would start and streaming would be possible. Unsurprisingly turning off fast boot fixed all issues. I do agree with you that 24H2 changed something that affected the fast boot parameters and in my specific case Sunshine didn’t like it. I also agree that the Lock Screen issue is there as well which is related to DXGI limitation as per you. But this specific issue in my case was Sunshine Service related and I hope that a built-in startup delay feature, especially as the service functions with Fast boot, should be considered. EDIT: cleaned up some wording. |
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
output_name = {fa234220-b6e3-5a0f-8558-e6a9629492ab} upnp = enabled address_family = both origin_web_ui_allowed = wan external_ip = 73.37.173.199 wan_encryption_mode = 0 hevc_mode = 3 av1_mode = 3 encoder = nvenc global_prep_cmd = [{"do":"powershell.exe -executionpolicy bypass -file \"C:\\Program Files\\Sunshine\\ResolutionAutomation\\StreamMonitor.ps1\" -n ResolutionMatcher","elevated":"false","undo":"powershell.exe -executionpolicy bypass -file \"C:\\Program Files\\Sunshine\\ResolutionAutomation\\Helpers.ps1\" -n ResolutionMatcher -t 1"}]Apps
No response
Relevant log output
The text was updated successfully, but these errors were encountered: