Remote Users Connection Timeout Launching VM on Windows App.

david aguilar 0 Reputation points
2026-11-18T21:37:09.4433333+00:00

Hello All,

I am currently having this issue where users from a different state are attempting to launch their work space VM (session desktop) from their logged in Windows app, and it will constantly load until it says connection timeout. When I log in as their user account on the Windows app and the workspace launches almost instantly.

Azure Virtual Desktop
Azure Virtual Desktop

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

0 comments No comments

1 answer

Sort by: Oldest
  1. AI answer

    2026-11-18T21:39:02.42+00:00

    The same account working from another location makes the affected users’ client device or local network path the first boundary to isolate, rather than changing the Azure Virtual Desktop host pool.

    1. Run two isolation tests from the affected location

    Before each test, record:

    • UTC timestamp
    • Exact error code and message
    • Activity or Correlation ID, if displayed
    • Windows App version
    • Windows version and recently installed updates

    Then:

    1. Open the organization’s Azure Virtual Desktop web-client URL in a browser and launch the same session desktop. Microsoft recommends comparing Windows App with its browser client when diagnosing connection failures.^1^
    2. Connect the affected computer through a different internet path, such as a mobile hotspot, and retry Windows App.

    Interpret the results:

    Result Most useful next action
    Web client and Windows App work on the hotspot Investigate the original site’s firewall, proxy, DNS, SSL inspection, VPN, or secure web gateway.
    Web client works, but installed Windows App fails on both networks Update or repair the Windows App client; also check the conditional Windows-update issue below.
    Both clients fail on the original network but work elsewhere Validate the original network against the complete AVD end-user endpoint list.
    Both clients fail even on the hotspot Review AVD connection diagnostics, authentication policy, and service health; the location alone has not isolated the cause.

    Also check Azure Status and Azure Service Health before deeper troubleshooting.^2^

    2. Validate the affected location’s network

    A network administrator should compare the firewall/proxy allowlist with the complete current end-user-device table for the Azure cloud being used. For public Azure, important entries include:

    • *.wvd.microsoft.com — TCP 443
    • *.service.windows.cloud.microsoft — TCP 443
    • *.windows.cloud.microsoft — TCP 443
    • login.microsoftonline.com — TCP 443
    • [IP Address]/16 — UDP 3478 for relayed DS connectivity

    This is only a diagnostic subset; apply the full documented table rather than treating it as a complete allowlist. Government and other sovereign-cloud endpoints differ.^3^

    Check particularly for:

    • HTTPS/SSL inspection affecting AVD traffic.
    • Proxy or PAC differences between states/offices.
    • DNS filtering or failure to resolve the required FQDNs.
    • VPN or endpoint-security software intercepting traffic.
    • UDP 3478 restrictions.

    AVD normally attempts UDP and falls back to TCP reverse connect if UDP cannot be established, so blocked UDP can degrade the path but should not automatically be assumed to explain a total connection failure.^4^ Keep TURN enabled; Microsoft recommends it as the reliable relayed path when direct UDP cannot be established.^5^

    3. Query AVD diagnostics for the failed attempt

    This requires access to the configured Log Analytics workspace:

    1. Azure portal → Log Analytics workspaces → select the AVD workspace → Logs.
    2. Run a query around the captured UTC time and ID. AVD diagnostic tables use the WVD prefix.^6^
    union isfuzzy=true WVDConnections, WVDCheckpoints, WVDErrors
    | extend DiagnosticId = tostring(column_ifexists("CorrelationId", "")),
             ActivityId = tostring(column_ifexists("ActivityId", "")),
             User = tostring(column_ifexists("UserName", "")),
             Error = tostring(column_ifexists("CodeSymbolic", "")),
             IsServiceError = tostring(column_ifexists("ServiceError", ""))
    | where TimeGenerated between (datetime(2026-11-18T12:00:00Z) .. datetime(2026-11-18T12:15:00Z))
    | where DiagnosticId == "<correlation-id>" or ActivityId == "<activity-id>"
    | project TimeGenerated, Type, User, DiagnosticId, ActivityId, Error, IsServiceError
    | order by TimeGenerated asc
    

    Replace the time range and IDs. If no event appears, that suggests the failure might occur before a completed diagnostic event reaches the broker, but it does not prove a client/network cause: events are sent when completed, and client information can sometimes be absent. If ServiceError is true, escalate to Microsoft with the Correlation ID.^6^

    Conditional checks

    • If Windows App reports 0x80080005 while the web client works: check whether client update KB5074109 is installed. Matching reports identify an issue corrected by OOB update KB5077744 and later Windows updates. Apply the current applicable superseding Windows update; avoid remaining on an unpatched rollback.^7^
    • If the session host shows Needs assistance/Unavailable: inspect Event Viewer → Windows Logs → Application for WVD-Agent, WVD-Agent-Updater, RDAgentBootLoader, and MsiInstaller. This host-side branch is appropriate only when host health or diagnostics implicate the agent.^8^
    • If the issue remains unresolved: open an Azure support request for Azure Virtual Desktop and attach the UTC timestamp, Activity/Correlation ID, exact error, client versions, test matrix, Windows App diagnostics, and network traces.^2^

    References

    1. Basic troubleshooting for Windows App
    2. Troubleshooting overview, feedback, and support for Azure Virtual Desktop
    3. Required FQDNs and endpoints for Azure Virtual Desktop
    4. DS Shortpath for Azure Virtual Desktop
    5. Configure DS Shortpath for Azure Virtual Desktop
    6. Send diagnostic data to Log Analytics for Azure Virtual Desktop
    7. Azure Virtual Desktop RemoteApp fails in Windows App with 0x80080005 for one user, but Web Client RemoteApp works - Microsoft Q&A
    8. Troubleshoot common Azure Virtual Desktop Agent issues
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.