Share via

AVD disconnects SSL_ERR_HANDSHAKE_FAILED (519)

Bobby Gross 0 Reputation points
2026-05-05T19:42:40.3566667+00:00

We have an AVD environment configured we a few host pools. All pools are using Windows 11 multi-session vms. Occasionally we see disconnects from AVD with this error SSL_ERR_HANDSHAKE_FAILED (519). Our client devices are Dell thin clients running ThinOS 10 2511 and using Microsoft AVD 3.3.384. What could be causing this issue?

Azure Virtual Desktop
Azure Virtual Desktop

A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.


1 answer

Sort by: Most helpful
  1. Nikhil Duserla 9,775 Reputation points Microsoft External Staff Moderator
    2026-05-19T09:46:25.04+00:00

    Hey Bobby, it sounds like your Dell ThinOS devices are intermittently failing the TLS handshake with your AVD gateway, hence the SSL_ERR_HANDSHAKE_FAILED (519) error. Here’s a quick checklist of the most common culprits and what to do:

    1. SSL/TLS inspection on the network
      • Many firewalls, proxies or Zscaler appliances will break AVD’s end-to-end encryption if they try to inspect the traffic.
      • Action: Work with your network team to bypass all Azure Virtual Desktop FQDNs (control plane + gateway) from SSL inspection.
    2. Missing or outdated root/intermediate CA on the ThinOS client
      • If ThinOS doesn’t trust the Microsoft-issued certificates (especially after cert rotations), the handshake will fail.
      • Action: Use Wyse Management Suite (WMS) to push the “DigiCert Global Root CA” and “Microsoft RSA Root Certificate Authority 2017” into the device trust store.
    3. ThinOS / Microsoft AVD package bugs
      • Even though you’re on ThinOS 10 2511 with AVD 3.3.384, there have been mid-cycle patches to address session crashes & handshake failures.
      • Action: Check Dell’s release notes/community thread for any hotfixes, collect WMS logs (wlogd) around the disconnect time, and open a case with Dell if needed.
    4. Narrow down client vs. host network issues
      • Try connecting from a Windows PC on the same network segment. If Windows works fine, it definitely points to ThinOS or your network path.
      • Look for patterns: wired vs. Wi-Fi, specific site or VPN, time of day, etc.
    5. Gather diagnostics
      • Pull ThinOS logs via WMS (Troubleshooting > Request Log File).
      • Use Azure Network Watcher or the AVD Required URL Check tool to validate connectivity to all required FQDNs/URLs.
      • Review AVD Insights (Connection Reliability tab) to see if there’s a spike in TCP vs. UDP transport or licensing timeouts.

    Hope that helps you get to the bottom of those random 519 disconnects!

    Reference list

    Note: This content was drafted with the help of an AI system. Please verify the information before relying on it for decision-making.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.