[ERROR] Fatal: Unable to find display or encoder during startup (Windows 24H2)

Is there an existing issue for this?

• I have searched the existing issues

Is your issue described in the documentation?

• I have read 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!):

• 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.

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

[2024-12-12 15:44:00.733]: Info: Sunshine version: v2024.1211.191744
[2024-12-12 15:44:00.733]: Info: Package Publisher: LizardByte
[2024-12-12 15:44:00.733]: Info: Publisher Website: https://app.lizardbyte.dev
[2024-12-12 15:44:00.733]: Info: Get support: https://app.lizardbyte.dev/support
[2024-12-12 15:44:00.733]: Info: Provided workaround settings for SettingsManager:
{
  "hdr_blank_delay": null
}
[2024-12-12 15:44:00.737]: Info: Currently available display devices:
[
  {
    "device_id": "{c394926f-1c13-5779-952b-e85e03c58c61}",
    "display_name": "\\\\.\\DISPLAY5",
    "friendly_name": "EP-HDMI-RX",
    "info": {
      "hdr_state": "Disabled",
      "origin_point": {
        "x": 7680,
        "y": 0
      },
      "primary": false,
      "refresh_rate": {
        "type": "rational",
        "value": {
          "denominator": 1001,
          "numerator": 60000
        }
      },
      "resolution": {
        "height": 720,
        "width": 1280
      },
      "resolution_scale": {
        "type": "rational",
        "value": {
          "denominator": 100,
          "numerator": 100
        }
      }
    }
  },
  {
    "device_id": "{fa234220-b6e3-5a0f-8558-e6a9629492ab}",
    "display_name": "\\\\.\\DISPLAY1",
    "friendly_name": "Odyssey G95NC",
    "info": {
      "hdr_state": "Enabled",
      "origin_point": {
        "x": 0,
        "y": 0
      },
      "primary": true,
      "refresh_rate": {
        "type": "rational",
        "value": {
          "denominator": 1000,
          "numerator": 119997
        }
      },
      "resolution": {
        "height": 2160,
        "width": 7680
      },
      "resolution_scale": {
        "type": "rational",
        "value": {
          "denominator": 100,
          "numerator": 200
        }
      }
    }
  }
]
[2024-12-12 15:44:00.875]: Info: nvprefs: No need to modify application profile settings
[2024-12-12 15:44:00.875]: Info: nvprefs: Changed OGL_CPL_PREFER_DXPRESENT to OGL_CPL_PREFER_DXPRESENT_PREFER_ENABLED for base profile
[2024-12-12 15:44:00.898]: Info: Compiling shaders...
[2024-12-12 15:44:00.909]: Warning: include/base_vs.hlsl(28,13-36): warning X3556: integer modulus may be much slower, try using uints if possible.
[2024-12-12 15:44:00.924]: Warning: include/base_vs.hlsl(28,13-36): warning X3556: integer modulus may be much slower, try using uints if possible.
[2024-12-12 15:44:00.933]: Warning: include/base_vs.hlsl(28,13-36): warning X3556: integer modulus may be much slower, try using uints if possible.
[2024-12-12 15:44:00.939]: Warning: include/base_vs.hlsl(28,13-36): warning X3556: integer modulus may be much slower, try using uints if possible.
[2024-12-12 15:44:00.956]: Warning: include/base_vs.hlsl(28,13-36): warning X3556: integer modulus may be much slower, try using uints if possible.
[2024-12-12 15:44:00.960]: Warning: include/base_vs.hlsl(28,13-36): warning X3556: integer modulus may be much slower, try using uints if possible.
[2024-12-12 15:44:00.960]: Info: Compiled shaders
[2024-12-12 15:44:00.974]: Error: Couldn't get default audio endpoint [0x80070490]
[2024-12-12 15:44:00.985]: Info: Trying encoder [nvenc]
[2024-12-12 15:44:01.009]: Info: ddprobe.exe 1 \\.\DISPLAY1 --verify-frame-capture returned 0x00000000
[2024-12-12 15:44:01.009]: Info: Set GPU preference: 1
[2024-12-12 15:44:01.525]: Error: Failed to locate an output device
[2024-12-12 15:44:02.033]: Error: Failed to locate an output device
[2024-12-12 15:44:02.742]: Error: Failed to locate an output device
[2024-12-12 15:44:03.248]: Error: Failed to locate an output device
[2024-12-12 15:44:03.454]: Info: Encoder [nvenc] failed
[2024-12-12 15:44:03.454]: Error: Couldn't find any working encoder matching [nvenc]
[2024-12-12 15:44:03.454]: Info: // Testing for available encoders, this may generate errors. You can safely ignore those errors. //
[2024-12-13 01:49:10.173]: Info: Trying encoder [quicksync]
[2024-12-13 01:49:11.234]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:12.195]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:12.203]: Error: Failed to locate an output device
[2024-12-13 01:49:12.637]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:12.789]: Info: System tray created
[2024-12-13 01:49:13.651]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:13.659]: Error: Failed to locate an output device
[2024-12-13 01:49:14.315]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:15.276]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:15.285]: Error: Failed to locate an output device
[2024-12-13 01:49:15.718]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:16.677]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:16.684]: Error: Failed to locate an output device
[2024-12-13 01:49:16.897]: Info: Encoder [quicksync] failed
[2024-12-13 01:49:16.897]: Info: Trying encoder [amdvce]
[2024-12-13 01:49:17.338]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:18.284]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:18.290]: Error: Failed to locate an output device
[2024-12-13 01:49:18.726]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:19.673]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:19.680]: Error: Failed to locate an output device
[2024-12-13 01:49:20.333]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:21.277]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:21.283]: Error: Failed to locate an output device
[2024-12-13 01:49:21.716]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:22.648]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:22.654]: Error: Failed to locate an output device
[2024-12-13 01:49:22.854]: Info: Encoder [amdvce] failed
[2024-12-13 01:49:22.854]: Info: Trying encoder [software]
[2024-12-13 01:49:23.281]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:24.240]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:24.247]: Error: Failed to locate an output device
[2024-12-13 01:49:24.680]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:25.634]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:25.641]: Error: Failed to locate an output device
[2024-12-13 01:49:26.286]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:27.236]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:27.243]: Error: Failed to locate an output device
[2024-12-13 01:49:27.670]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:28.628]: Error: DuplicateOutput() test failed [0x887A0004]
[2024-12-13 01:49:28.634]: Error: Failed to locate an output device
[2024-12-13 01:49:28.836]: Info: Encoder [software] failed
[2024-12-13 01:49:28.836]: Error: Couldn't find any working encoder that meets HEVC/AV1 requirements
[2024-12-13 01:49:28.836]: Fatal: Unable to find display or encoder during startup.
[2024-12-13 01:49:28.836]: Fatal: Please ensure your manually chosen GPU and monitor are connected and powered on.
[2024-12-13 01:49:28.836]: Error: Video failed to find working encoder
[2024-12-13 01:49:28.846]: Info: Configuration UI available at [https://localhost:47990]
[2024-12-13 01:49:29.623]: Info: Registered Sunshine mDNS service
[2024-12-13 01:49:30.916]: Error: Failed to map TCP 48010: 718
[2024-12-13 01:49:30.924]: Error: Failed to map UDP 47998: 718
[2024-12-13 01:49:30.932]: Error: Failed to map UDP 48000: 718
[2024-12-13 01:49:30.939]: Error: Failed to map UDP 47999: 718
[2024-12-13 01:49:30.947]: Error: Failed to map TCP 47989: 718
[2024-12-13 01:49:30.954]: Error: Failed to map TCP 47984: 718
[2024-12-13 01:49:30.964]: Info: Completed UPnP port mappings to 192.168.1.237 via http://192.168.1.1:37089/rootDesc.xml
[2024-12-13 01:49:44.037]: Info: Opening UI from system tray
[2024-12-13 01:49:44.043]: Info: Resolved user-provided command 'https://localhost:47990' to '"C:\Users\sinmu\AppData\Local\Mozilla Firefox\firefox.exe" -osint -url "https://localhost:47990"'
[2024-12-13 01:49:44.047]: Info: https://localhost:47990 running with PID 17716
[2024-12-13 01:49:44.047]: Info: Opened url [https://localhost:47990]
[2024-12-13 01:49:44.116]: Info: Web UI: [127.0.0.1] -- not authorized
[2024-12-13 01:51:49.108]: Error: Failed to map TCP 48010: 718
[2024-12-13 01:51:49.116]: Error: Failed to map UDP 47998: 718
[2024-12-13 01:51:49.125]: Error: Failed to map UDP 48000: 718
[2024-12-13 01:51:49.134]: Error: Failed to map UDP 47999: 718
[2024-12-13 01:51:49.142]: Error: Failed to map TCP 47989: 718
[2024-12-13 01:51:49.149]: Error: Failed to map TCP 47984: 718
[2024-12-13 01:54:07.305]: Error: Failed to map TCP 48010: 718
[2024-12-13 01:54:07.312]: Error: Failed to map UDP 47998: 718
[2024-12-13 01:54:07.320]: Error: Failed to map UDP 48000: 718
[2024-12-13 01:54:07.327]: Error: Failed to map UDP 47999: 718
[2024-12-13 01:54:07.335]: Error: Failed to map TCP 47989: 718
[2024-12-13 01:54:07.345]: Error: Failed to map TCP 47984: 718
[2024-12-13 01:56:25.502]: Error: Failed to map TCP 48010: 718
[2024-12-13 01:56:25.510]: Error: Failed to map UDP 47998: 718
[2024-12-13 01:56:25.518]: Error: Failed to map UDP 48000: 718
[2024-12-13 01:56:25.526]: Error: Failed to map UDP 47999: 718
[2024-12-13 01:56:25.533]: Error: Failed to map TCP 47989: 718
[2024-12-13 01:56:25.541]: Error: Failed to map TCP 47984: 718
[2024-12-13 01:58:43.694]: Error: Failed to map TCP 48010: 718
[2024-12-13 01:58:43.702]: Error: Failed to map UDP 47998: 718
[2024-12-13 01:58:43.710]: Error: Failed to map UDP 48000: 718
[2024-12-13 01:58:43.717]: Error: Failed to map UDP 47999: 718
[2024-12-13 01:58:43.725]: Error: Failed to map TCP 47989: 718
[2024-12-13 01:58:43.733]: Error: Failed to map TCP 47984: 718

[joeldevelops]

Having this issue on Ubuntu 24.04.1 LTS

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).

[erwan-privat]

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.

[eduardoibarra960]

Same issue on Windows 11 Pro 24H2.

[Nonary]

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.

[erwan-privat]

Just for info I'm running Windows 11 Pro 21H2 and I too have this issue.

[Nonary]

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.

[erwan-privat]

Hm, if you're sure that's good to know.
I'm not using a laptop (server side), but I will open a new issue if I can gather more useful diagnostic info. I have had trouble updating windows and NVIDIA drivers recently, might be linked.

[Nonary]

Hm, if you're sure that's good to know.

I'm not using a laptop (server side), but I will open a new issue if I can gather more useful diagnostic info. I have had trouble updating windows and NVIDIA drivers recently, might be linked.

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.

[erwan-privat]

Hm, if you're sure that's good to know.
I'm not using a laptop (server side), but I will open a new issue if I can gather more useful diagnostic info. I have had trouble updating windows and NVIDIA drivers recently, might be linked.

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.

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.

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:

• installed a bunch of startup programs and pray for Sunshine Service to get delayed during startup… and it worked! Streams at first request. I noticed that the Sunshine icon would pop up a bit later in the tray, even at cold start (previously, sunshine icon was the first or second icon to pop up in the tray. Curiously this behavior doesn’t pop up when you simply restart a system. The Sunshien icon appears as either the last or second last icon)

• went back to my original lean configuration (windows reinstall); issue returned at cold start. This time around I began using Unified Remote to remotely restart the system.

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.

[ReenigneArcher]

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.

[Nonary]

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.

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:

• installed a bunch of startup programs and pray for Sunshine Service to get delayed during startup… and it worked! Streams at first request. I noticed that the Sunshine icon would pop up a bit later in the tray, even at cold start (previously, sunshine icon was the first or second icon to pop up in the tray. Curiously this behavior doesn’t pop up when you simply restart a system. The Sunshien icon appears as either the last or second last icon)
• went back to my original lean configuration (windows reinstall); issue returned at cold start. This time around I began using Unified Remote to remotely restart the system.

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.

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.

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 tried this. Here is what happens:

• you make Sunshine Service manual, schedule a task with a delay of 15/30/60/… and it magically still starts right before everything else on a cold boot! Absolute mystery. The most rogue, eager-to-start service I ever dealt with hah

• you disable Sunshine Service, launch sunshine through a scheduled task (sunshine.exe) and you get a cmd prompt window infinitely waiting for Sunshine Web UI to launch.

• you do not install Sunshine Service, and Sunshine refuses to launch.

• you try launching Sunshine as an .exe and you get a cmd prompt lecturing you to let Sunshine launch through its Service (I could be misremembering a bit about the message that appears).