Installed worked great! Windows updates (25H2) and then a restart has never worked again. Tried troubleshooting. And then downloaded 24H2
and did a clean fresh install getting rid of all files and system settings. Was on a work call so some windows updates got installed before I could pause the windows update. Downloaded Duo again and installed but still can't seem to get it to work again. It just sees the AMD GPU and 1 display. While the sunshine by LizardByte sees both Displays and then the RdpIdd creates a phantom instead of using Display 1 or Display 2. It never goes back to Session 2 like when it worked. Always 3>4>5>6>7>8 etc.
Display 1 is using Display Port Fueran 4k dummy plug. Connects faster than the TV/Monitor so it automatically gets assigned Display 1.
Display 2 is My TV/Monitor for work.
Tried all different display resolutions. 1920x1080 all the way upto 2560x1440 all at 60
System
CPU/GPU: Ryzen AI 9 HX 370, AMD Radeon 890M iGPU ONLY (gfx1150/RDNA 3.5, Device ID 0x150E, Vendor 0x1002, no discrete GPU)
OS: Windows 11 24H2 Build 26100
Duo version: 1.5.6
AMD driver: 32.0.23027.2005
Display: FUERAN 4K dummy plug → DISPLAY1 (DisplayPort, primary)
Error (Gamer.log)
Debug: Failed to find device for \.\DISPLAY1!
Error: Failed to locate an adapter, restarting sunshine
This repeats for every encoder tried: nvenc → quicksync → amdvce → software. All fail identically.
Phantom second AMD adapter instance in session 2
Using Sunshine's dxgi-info.exe tool, enumerated DXGI adapters from both sessions via scheduled task:
Session 1 (console):
====== ADAPTER =====
Device Name : AMD Radeon(TM) 890M Graphics
Device ID : 0x0000150E
Output: \.\DISPLAY1 AttachedToDesktop: yes 2560x1440
Output: \.\DISPLAY2 AttachedToDesktop: yes 2560x1440
====== ADAPTER =====
Device Name : Microsoft Basic Render Driver
→ Single AMD instance, both physical displays visible ✅
Session 2 (Gamer RDP session):
====== ADAPTER =====
Device Name : AMD Radeon(TM) 890M Graphics ← CORRECT INSTANCE
Device ID : 0x0000150E
Output: \.\DISPLAY1 AttachedToDesktop: yes 1920x1080 ✅
====== ADAPTER =====
Device Name : AMD Radeon(TM) 890M Graphics ← PHANTOM INSTANCE (identical name)
Device ID : 0x0000150E
(no outputs) ❌
====== ADAPTER =====
Device Name : Microsoft Basic Render Driver
The AMD 890M appears TWICE in session 2 with identical names, identical device IDs, and no way to distinguish them by name. The phantom second instance is created by RdpIdd.dll when the RDP session initializes. Duo's sunshine consistently selects the phantom instance (no outputs) for encoder initialization, which fails with "Failed to locate an adapter."
What Was Tried (Exhaustive... Nothing Worked)
adapter_name = AMD Radeon(TM) 890M Graphics — both instances have identical names, picks wrong one
adapter_name = PCI\VEN_1002&DEV_150E&SUBSYS_00301F66&REV_C1\4&26C18D87&0&0041 — PNP path not recognized
output_name = {bfb911d1-c758-53cb-a9a2-a52a39313b78} (device GUID) — GUID is dynamic per session, fails
output_name = \.\DISPLAY1 — fails, "Failed to find device"
No output_name — adapter search fails without output anchor
capture = wgc and capture = ddx — fail identically
encoder = amdvce / encoder = software — all fail at adapter lookup before encoding starts
DisableOverlays = 1 sessions 1–8
Group Policy: bEnumerateHWBeforeSW=1, fEnableWddmDriver=1, AVC444ModePreferred=1, AVCHardwareEncodePreferred=1
TdrLevel = 0, Memory Integrity disabled
VDD (IddSampleDriver / MttVDD) as DISPLAY6 — same result
Windows 11 24H2 repair install + full Reset This PC
Fresh AMD driver install
RenderAdapter = AMD Radeon(TM) 890M Graphics in instance registry — same name collision problem
Sandboxed mode — Failed.
So, I hope this helps. If needed I can show the updates that slipped by me. If you have any other troubleshooting steps let me know. Oh and even if I switched it to Display2 it was the same error couldn't find adapter. But I did notice they swapped spots the first time around. Display 1 became Display 2 and visa versa but it was working. I just remembered that as I was about to submit.
Installed worked great! Windows updates (25H2) and then a restart has never worked again. Tried troubleshooting. And then downloaded 24H2
and did a clean fresh install getting rid of all files and system settings. Was on a work call so some windows updates got installed before I could pause the windows update. Downloaded Duo again and installed but still can't seem to get it to work again. It just sees the AMD GPU and 1 display. While the sunshine by LizardByte sees both Displays and then the RdpIdd creates a phantom instead of using Display 1 or Display 2. It never goes back to Session 2 like when it worked. Always 3>4>5>6>7>8 etc.
Display 1 is using Display Port Fueran 4k dummy plug. Connects faster than the TV/Monitor so it automatically gets assigned Display 1.
Display 2 is My TV/Monitor for work.
Tried all different display resolutions. 1920x1080 all the way upto 2560x1440 all at 60
System
CPU/GPU: Ryzen AI 9 HX 370, AMD Radeon 890M iGPU ONLY (gfx1150/RDNA 3.5, Device ID 0x150E, Vendor 0x1002, no discrete GPU)
OS: Windows 11 24H2 Build 26100
Duo version: 1.5.6
AMD driver: 32.0.23027.2005
Display: FUERAN 4K dummy plug → DISPLAY1 (DisplayPort, primary)
Error (Gamer.log)
Debug: Failed to find device for \.\DISPLAY1!
Error: Failed to locate an adapter, restarting sunshine
This repeats for every encoder tried: nvenc → quicksync → amdvce → software. All fail identically.
Phantom second AMD adapter instance in session 2
Using Sunshine's dxgi-info.exe tool, enumerated DXGI adapters from both sessions via scheduled task:
Session 1 (console):
====== ADAPTER =====
Device Name : AMD Radeon(TM) 890M Graphics
Device ID : 0x0000150E
Output: \.\DISPLAY1 AttachedToDesktop: yes 2560x1440
Output: \.\DISPLAY2 AttachedToDesktop: yes 2560x1440
====== ADAPTER =====
Device Name : Microsoft Basic Render Driver
→ Single AMD instance, both physical displays visible ✅
Session 2 (Gamer RDP session):
====== ADAPTER =====
Device Name : AMD Radeon(TM) 890M Graphics ← CORRECT INSTANCE
Device ID : 0x0000150E
Output: \.\DISPLAY1 AttachedToDesktop: yes 1920x1080 ✅
====== ADAPTER =====
Device Name : AMD Radeon(TM) 890M Graphics ← PHANTOM INSTANCE (identical name)
Device ID : 0x0000150E
(no outputs) ❌
====== ADAPTER =====
Device Name : Microsoft Basic Render Driver
The AMD 890M appears TWICE in session 2 with identical names, identical device IDs, and no way to distinguish them by name. The phantom second instance is created by RdpIdd.dll when the RDP session initializes. Duo's sunshine consistently selects the phantom instance (no outputs) for encoder initialization, which fails with "Failed to locate an adapter."
What Was Tried (Exhaustive... Nothing Worked)
adapter_name = AMD Radeon(TM) 890M Graphics — both instances have identical names, picks wrong one
adapter_name = PCI\VEN_1002&DEV_150E&SUBSYS_00301F66&REV_C1\4&26C18D87&0&0041 — PNP path not recognized
output_name = {bfb911d1-c758-53cb-a9a2-a52a39313b78} (device GUID) — GUID is dynamic per session, fails
output_name = \.\DISPLAY1 — fails, "Failed to find device"
No output_name — adapter search fails without output anchor
capture = wgc and capture = ddx — fail identically
encoder = amdvce / encoder = software — all fail at adapter lookup before encoding starts
DisableOverlays = 1 sessions 1–8
Group Policy: bEnumerateHWBeforeSW=1, fEnableWddmDriver=1, AVC444ModePreferred=1, AVCHardwareEncodePreferred=1
TdrLevel = 0, Memory Integrity disabled
VDD (IddSampleDriver / MttVDD) as DISPLAY6 — same result
Windows 11 24H2 repair install + full Reset This PC
Fresh AMD driver install
RenderAdapter = AMD Radeon(TM) 890M Graphics in instance registry — same name collision problem
Sandboxed mode — Failed.
So, I hope this helps. If needed I can show the updates that slipped by me. If you have any other troubleshooting steps let me know. Oh and even if I switched it to Display2 it was the same error couldn't find adapter. But I did notice they swapped spots the first time around. Display 1 became Display 2 and visa versa but it was working. I just remembered that as I was about to submit.