September 20, 2025

What is RDP Multipath and How to deploy it with Windows Registry, PowerShell, Intune or Ansible

Today marks a monumental step forward in the evolution of remote desktop technology. In a world where hybrid work and cloud computing are the new normal, the reliability and performance of virtual desktop infrastructure (VDI) have never been more critical. The experience is only as good as the network connection supporting it. That is why the general availability of Remote Desktop Protocol (RDP) Multipath for Azure Virtual Desktop (AVD) and Windows 365 is not just an update, it’s a revolution in connectivity.

For years, IT professionals and end-users have grappled with the inherent fragility of remote connections. A momentary drop in Wi-Fi signal, a sudden surge in home network traffic, or a change in internet routing could spell disaster for a productive work session, leading to frustrating disconnects and poor quality of experience (QoE). RDP Multipath directly confronts this challenge, delivering a desktop experience so smooth and resilient it fundamentally changes the definition of “working remotely.”

The Single-Path Pitfall: Why We Needed a Change

To truly appreciate the genius of RDP Multipath, one must understand the limitations of the traditional RDP architecture. Historically, a Remote Desktop session relied predominantly on a single, primary network connection, often TCP (Transmission Control Protocol), and more recently, an optional UDP-based path for better performance. While these single-path connections worked well under ideal, stable conditions, they represented a single point of failure.

Imagine this scenario: you are working on a critical presentation in your Cloud PC. The connection is stable, but your primary path, the TCP connection, suddenly experiences a brief interruption—perhaps a quick change in the network firewall’s state or a transient issue with the local router. The session freezes. If the path fails entirely, you are dropped, losing precious time and context while the client attempts to reconnect. The single-path approach meant that the entire session was at the mercy of the weakest link in that one connection. Performance was dictated by the single path with the worst current latency or highest packet loss. This volatility was a significant barrier to achieving true desktop parity with an on-premises machine.

Introducing Intelligent Connectivity: What RDP Multipath Does

RDP Multipath fundamentally re-engineers the connection architecture by allowing the RDP session to utilize multiple, concurrent network paths between the client and the session host or Cloud PC. These paths can include traditional TCP, the high-performance UDP/QUIC transport, or other future-proof network technologies.

The key innovation, however, is not simply having multiple paths—it’s the intelligent management of those paths. RDP Multipath does not just run them side-by-side; it constantly monitors the health, latency, and packet loss of each available path in real-time. It then dynamically and seamlessly selects the best-performing path for data transmission. This advanced intelligence transforms a brittle single connection into a resilient, adaptive network fabric.

The primary benefit is a radical improvement in reliability and performance.

Unprecedented Reliability: The Power of Seamless Failover

The most immediate and impactful benefit of RDP Multipath is the introduction of seamless failover. This feature directly addresses the frustrating disconnects that plague remote users. With Multipath enabled, if the session’s currently active path degrades or fails entirely (e.g., the primary UDP path sees a sharp increase in packet loss), the RDP engine does not panic. Instead, it instantly and transparently switches the session’s traffic to another healthy, available path—such as a backup TCP connection—all without the user even noticing.

The following diagram illustrates how RDP Multipath works with Azure Virtual Desktop. In this user scenario, the primary active path is the connection of UDP via STUN, supplemented by two redundant UDP connections through a TURN server:

This is the magic that transforms a freezing, disconnected screen into a minor network event handled entirely in the background. For the end-user, the connection appears continuous and robust, maintaining a high quality of experience even when the underlying network is unstable. The context of the user’s work is preserved, eliminating the time-consuming and productivity-killing cycle of disconnection, application reset, and reconnection. This is a game-changer for workers operating on home Wi-Fi networks, mobile hotspots, or in locations with notoriously variable internet service.

Sustained Performance: Dynamic Path Selection

Reliability is only one side of the coin; performance is the other. RDP Multipath excels here too by ensuring that the RDP data is always transmitted over the *best* available path at any given moment.

In traditional setups, if the main path became saturated or experienced high latency, the user experience suffered until the condition resolved. With Multipath, the system is continuously performing dynamic load balancing and assessment. If a previously-dormant path suddenly offers significantly lower latency, the session can intelligently leverage that path to transmit the most performance-sensitive data, such as audio, video, or input commands. This dynamic selection capability guarantees that the user consistently receives the fastest possible screen updates and the lowest input latency, regardless of external network conditions. The result is a highly responsive, near-local computing feel that is essential for power users, developers, and creatives.

General Availability: A Milestone for AVD and Windows 365

The general availability of RDP Multipath is a major milestone specifically for the users and administrators of Azure Virtual Desktop and Windows 365. These platforms are Microsoft’s flagship offerings for cloud-hosted desktops, and their success hinges entirely on delivering an impeccable remote experience. By natively integrating RDP Multipath into the RDP clients and session hosts, Microsoft is ensuring that the investment in cloud PCs provides a superior, more predictable experience than ever before.

For IT administrators, this means fewer support calls related to connection issues and a higher rate of user satisfaction. For the business, it translates into sustained productivity across a globally distributed workforce. The current phased rollout ensures a smooth deployment, allowing an increasing percentage of connections to gradually benefit from this incredible technology as Microsoft continues its deployment. This measured approach guarantees stability while the ecosystem fully integrates the new capabilities.

Next Steps

RDP Multipath is more than just a feature; it’s a foundational improvement that sets the stage for the next generation of remote computing. It addresses the inherent instability of the public internet by making the RDP connection smarter, more adaptive, and vastly more resilient. By intelligently managing and utilizing multiple network paths, it removes the single greatest point of friction in the remote desktop experience, delivering seamless failover and optimal performance to users of Azure Virtual Desktop and Windows 365.

The promise of the cloud is the ability to work from anywhere, on any device, with the power of a modern desktop. With RDP Multipath, that promise is now a stable, continuous reality. If you are an administrator or user of AVD or Windows 365, the days of unpredictable, jittery connections are fading fast.

Users can check the connection status of a remote session from the connection bar, which shows RDP Multipath is enabled, as shown in the following example screenshot:

Azure Virtual Desktop administrators can view connection reliability information in Azure Virtual Desktop Insights. For more information, see the connection reliability use case for Azure Virtual Desktop Insights.

If you find some connections aren’t using RDP Multipath, check that a firewall or other network restrictions doesn’t block RDP Shortpath connections. A connection using STUN or TURN protocols is required.

RDP Multipath Implementation by changes in Windows Registry

To enable RDP Multipath please add the below Registry Entry:

reg add “HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RdpCloudStackSettings” /v SmilesV3ActivationThreshold /t REG_DWORD /d 100 /f

To disable RDP Multipath please add the below Registry Entry:

reg add “HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RdpCloudStackSettings” /v SmilesV3ActivationThreshold /t REG_DWORD /d 0 /f

Important Context and Prerequisites

Location: These changes must be applied to the Session Host VM (or Cloud PC), not the local client machine.
Effect: For the change to take effect, the user must disconnect and reconnect to the session host. A full VM reboot is generally not required.
Prerequisite: RDP Shortpath: RDP Multipath requires that RDP Shortpath is configured and working on your network. Multipath builds on the foundation of Shortpath (the UDP connection) by keeping a reliable path (like TCP) active for seamless failover.
Client Version: You must be using a supported RDP client version, such as the Windows App (version 2.0.559.0 or later) or the Remote Desktop client (version 1.2.6353 or later).
RDP Multipath Implementation with Intune

This method for applying custom configurations to Windows devices.

A. Prepare the Script

Write the PowerShell Script (.ps1 file): Create your script. For example, to enable the RDP Multipath setting for Azure Virtual Desktop (AVD), which requires setting a registry key this is the script which I have written.

# PowerShell script to set the RDP Multipath registry key

$registryPath = “HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\RdpCloudStackSettings”$valueName = “SmilesV3ActivationThreshold”

$valueData = 100 # 100 to force-enable (opt-in)

# Check if the path exists, and create it if it doesn’t

if (-not (Test-Path $registryPath)) {

New-Item -Path $registryPath -Force | Out-Null

}

# Set the registry value (REG_DWORD)

Set-ItemProperty -Path $registryPath -Name $valueName -Value $valueData -Type DWord -Force

Write-Output “RDP Multipath registry setting deployed successfully.”

exit 0 # Exit code 0 indicates success

Save the Script: Save the file as a .ps1 file (e.g., Enable-RdpMultipath.ps1).

B. Upload and Configure in Intune

Sign in to the Microsoft Intune admin center.
Navigate to Devices > Windows > PowerShell scripts (or Scripts and Remediations > Platform Scripts).
Click + Add.
Set the Script Settings:
- Script location: Browse and upload your .ps1 file.
- Run this script using the logged on credentials: Usually No (to run as the powerful System account for HKLM changes).
- Enforce script signature check: Usually No, unless your scripts are digitally signed.
- Run script in 64-bit PowerShell host: Usually Yes for system-level changes on 64-bit Windows.
Click Next.
Assign the script to the required security groups (users or devices) that contain your target machines.
Click Next and Create.
Deploy RDP Multipath with Ansible Playbook