Windows: updater loop with update-failure despite network reachable (updates.discord.com TLS handshake issues through virtual adapter)

[ZhaoSQ-CH]

Summary

Discord on Windows enters an endless update loop (checking-for-updates -> update-failure) even after clean reinstall.

Environment

• OS: Windows 11 (10.0.22631)
• App: Discord stable 1.0.9227
• New updater logs show updater_client (reqwest/hyper)

What was tried

1. Full uninstall/reinstall (including cache and Squirrel temp cleanup)
2. Verified Update.exe and packages/RELEASES exist
3. Switched VPN modes/nodes and tested both direct/proxy paths
4. Tested WinHTTP/system proxy combinations

Network diagnostics

• Test-NetConnection updates.discord.com -Port 443 can be TcpTestSucceeded=True
• But updater still intermittently fails with
  etwork_error and timeout in logs
• In failing state, logs repeatedly show:
  • updater_client: ... host: updates.discord.com ... tcp connect error ... code: 10060
  • splash status loop: checking-for-updates -> update-failure

Relevant log excerpt

ERROR [updater_client]: Failed ... reqwest::Error ... host: Some(Domain("updates.discord.com")) ... ConnectError("tcp connect error", Os { code: 10060 ... })

Expected behavior

Updater should honor active network route/proxy path consistently and stop retry loop once endpoint is reachable.

Actual behavior

Updater keeps retrying in a loop and blocks startup flow with repeated update failures.

Notes

This appears related to updater network-path/proxy handling under virtual adapters/VPN route changes on Windows.

[infinitestory]

Hi! This is not the place for general bug reports; please contact support for general client bugs.