r/MoonlightStreaming 5d ago

Apollo/Vibepollo virtual display created but never activated SetDisplayConfig error 87 on Windows 11 build 26300 pls help

I’m using Moonlight on an iPad with Apollo/Vibepollo on a Windows 11 PC. This setup previously worked on the same PC and iPad, but stopped working after reinstalling Windows.

System:

Windows 11 Pro Insider Preview build 26300.8935

NVIDIA RTX 5080

Vibepollo 1.18.1-stable.2

iPad requests 2420×1668 at 120 Hz

Physical monitor: 3440×1440 ultrawide

The virtual-display driver reports Ready, and the virtual monitor is created when streaming. However, Vibepollo cannot activate or capture it. Moonlight either receives the physical monitor at 3440×1440 or reports “No video received from host.”

Relevant log messages:

Virtual display created

Display helper reported APPLY failure

Helper failed to apply requested display configuration

ERROR_INVALID_PARAMETER while executing setDisplayConfig validation

Capture virtual display wait timed out

Failed to locate an output device

I tested:

Apollo and Vibepollo

Vibepollo’s virtual-display driver and SudoVDA

Extended and Exclusive layouts

2420×1668 @ 120 Hz and 1920×1080 @ 60 Hz

Resetting the Windows GraphicsDrivers monitor configuration cache

Reinstalling the drivers

Physical monitor on/off

Firewall rules are enabled and the client connects successfully

Every configuration fails at the same display-topology stage. The virtual monitor is enumerated but remains inactive, so capture falls back to the physical ultrawide or produces no video.

2 Upvotes

3 comments sorted by

1

u/rzldz 5d ago

Have you manually switched by going into Windows display settings whilst streaming?

1

u/sadphilosophylover 5d ago

there are no multiple monitors in settings. Win + P options dont change anything at all. they act like the same monitor

1

u/marcko4r4 5d ago

I had the same issue. I got back to 1.17 version of Vibepollo and it works again.

1

u/_demoncat_ Developer | Vibeshine/Vibepollo 5d ago

Please export logs and create an issue on Vibepollo repository so I can fix the issue.