Remote Desktop Protocol Client (msrdc.exe) v1.2.7391 Crashes at an Increasing Rate

ControlUp has identified an upward crash trend affecting msrdc.exe, the modern Remote Desktop Protocol client used for Azure Virtual Desktop (AVD), Windows 365 Cloud PCs, and RemoteApp scenarios.

During September 2026, both the daily number of crashes and the number of affected devices increased significantly. This increase is almost exclusively associated with msrdc.exe client build 1.2.7391.

As of September 27, 2026, approximately 1,500 client devices were affected across more than 180 organizations, representing more than a twofold increase relative to the August baseline.

This behavior has been observed across more than 180 organizations and is classified as medium severity.

Crashes of msrdc.exe may immediately disrupt active remote sessions. Affected users may see a “Your session has ended” modal, an unhandled msrdc.exe crash dialog, or experience active remote session windows freezing and closing abruptly.

Potential user impact includes immediate loss of connectivity to Azure Virtual Desktop or Windows 365 Cloud PC sessions, unsaved data loss in seamless RemoteApp container instances, and termination of local peripheral virtual channel redirection.

Microsoft has issued an out-of-band update for a related Remote Desktop Services (RDS) server-side issue introduced by the September 2026 Windows security update.

The recent increase in msrdc.exe client crashes may relate to issues introduced by recent RDS server-side changes, but it may also stem from factors specific to the recent msrdc.exe v1.2.7391 client build.

Organizations experiencing this crash pattern should investigate msrdc.exe crash details in their environment, validate whether relevant server-side updates have been applied, and review whether affected users are connecting through AVD, Windows 365, or RemoteApp workflows.

Microsoft’s September 2026 RDS issue involved Remote Desktop Services instability after the September Windows security update, including RDP connection failures after several minutes, sign-in issues, and servers hanging at “Please wait for the Remote Desktop Configuration.”

Microsoft’s bulletin also notes that the specific RDS server-side issue does not affect Windows 365 or Azure Virtual Desktop. Because this finding concerns client-side msrdc.exe crashes observed in AVD, Windows 365, and RemoteApp usage patterns, organizations should avoid assuming the Microsoft RDS server-side bulletin fully explains all affected cases.

View Microsoft’s RDS resolved issue bulletin

ControlUp will continue monitoring this crash pattern to determine whether it correlates with specific client versions, server-side patch levels, or Microsoft Remote Desktop service changes.