1.18.1 stable 2 can not connect

[Mark25dkm]

Bug Symptoms

I got this in the log: Warning: WSASendMsg() failed: 10022
connection always failed with udc

Expected Behavior

Should be able to connect

Windows Version

25H2

Package

Windows - exe installer

GPU Type

NVIDIA

GPU Model

5060

GPU Driver Version

NVIDIA

Capture Method

Desktop Duplication API (Windows)

Apps

Logs (Optional but Recommended)

No response

Screenshot (Optional)

[github-actions]

Thank you for the report. We need logs in order to troubleshoot this issue.

Please collect them from Vibepollo:

1. Open the system tray icon for Apollo.
2. Click Open Vibepollo.
3. If required, log into the Web UI.
4. Open the Troubleshooting tab.
5. Click Export Logs.
6. Upload the resulting logs archive or crash bundle to this issue.

For automation purposes, please do not rename the exported logs or crash bundle after downloading them.

Once logs or a crash bundle are attached, they will be reviewed. If no logs or a crash bundle are provided within 2 weeks, this issue will be closed for lack of information provided.

[TravisMWeaver]

I have the same issue running a 4090 with an AMD 7950x3d on latest Windows 11 release. Rolling back to 1.18.0 fixed the issues for me.

[coffeepotkiller]

I also run into connection issues with v1.18.1-stable2, I do not encounter the issue with v1.18.0 or v1.18.3-beta.6 so seems like fix was already implemented in latest beta builds.

[Nonary]

Thanks for confirming that 1.18.3-beta.6 works. We compared the released source for 1.18.0, 1.18.1-stable.2, and beta.6. The Windows WSASendMsg path and UDP/RTSP socket-family selection are identical, so there is no networking commit we can responsibly identify as the fix from error 10022 alone.

Please attach an A/B diagnostic set using the same PC, Moonlight client, app, and network:

1. The complete Vibepollo host log from service startup through one failed stable.2 connection.
2. The complete host log from service startup through one successful beta.6 connection.
3. The matching Moonlight client logs and exact attempt times.
4. The configured address_family, bind_address, and frame-limiter/RTSS settings, plus whether Moonlight connects using an IPv4 address, IPv6 address, or hostname.

Please include the lines before the WSASendMsg warning. We need to determine whether the first failure is an Initial Ping Timeout, delayed RTSP response, capture/startup stall, or the UDP send itself. The item is returning to Backlog pending that evidence.

[coffeepotkiller]

The complete Vibepollo host log from service startup through one failed stable.2 connection.
The complete host log from service startup through one successful beta.6 connection.

Okay I just did a successful stream with v1.18.3-beta.6, then I downgraded to v1.18.1-stable.2 and reproduced the failure.

Here is rough timeline
2026-07-29
09:38-09:39 - Connected successfully to v1.18.3-beta.6
09:43-09:44 - downgraded to v1.18.1-stable.2, then tried to connect to Desktop and then Steam, reproduced issue each time

Here are a few more details on symptoms of failure:
-The client completes the RTSP handshake but afterwards a black screen is only displayed, the audio does work though (I can hear the Steam Desktop startup sound on my client)
-After about ~10 seconds it disconnects and I get the error:

Connection Terminated
No video received from host.
Check your firewall and port forwarding rules for port(s):
UDP 47998
UDP 48000

-When I click OK I get kicked back to the app list within Artemis
-the session is not closed and I'm able to click the play button to try to resume - same symptoms happen....black screen for 10s then connection terminated

I exported Vibeshine logs, hopefully that captures everything you need there for both tests:
vibeshine_logs-20260729-094514.zip

The matching Moonlight client logs and exact attempt times.

I've never exported these logs before, need to figure out how to do that, my client is Odin 2 Portal running Artemis

The configured address_family, bind_address, and frame-limiter/RTSS settings, plus whether Moonlight connects using an IPv4 address, IPv6 address, or hostname.

Address Family = Ipv4 only
Bind address = blank

and here are the only values in my sunshine.conf, everything else I left at default
dd_use_sunshine_virtual_display_driver = enabled
frame_limiter_enable = true

I connect to my host via a IPv4 address

[github-actions]

Logs or a crash bundle were detected, so the logs requested label was removed and this issue can be reviewed.

[se7zer]

I can confirm 1.18.1 stable 2 cannot connect on windows moonlight, but can connect on iOS moonlight.

Moving to v1.18.3-beta.6 windows moonlight can connect again.