Version 1.2.3004 of the Windows Desktop client for AVD has been released to all users!


This morning we released the March update of the Windows Desktop client (MSRDC) to all users. Check out What’s New in this release and as always, appreciate any feedback.

12 Replies

After upgrading to version 1.2.3004, I have several users that are no longer getting to login prompt when trying to connect to the azure virtual desktop. When you click it on, nothing happens. Any ideas? Reverting to a previous version seems to resolve the issue.
Hello - thank you for your message. Can you tell me the last time you had this issue? We added a fix yesterday and want to make sure this isn't something different. Thank you.
It started today (4/5/2022) after we pushed the 1.2.3004 client upgrade. We have several users that are no longer getting the login prompt when trying to connect to the azure virtual desktop. I'm still getting reports.
Thanks for the information. I am checking into this for you.
After some initial investigation the Dev team has asked if you could open a ticket so they can collect additional information to help them debug.
Would this be a case through our azure subscription or O365 subscription?
When you open the case make sure to attach the client traces from : %temp%\diagoutputdir\rdclientautotrace
Thanks !

Thanks, we will include the client traces in our case. Our workaround is to revert back to version 2927. Looking into the application logs, we found this error and it seems to be associated with the problem.

Faulting application name: msrdc.exe, version: 1.2.3004.0, time stamp: 0x623e5b83
Faulting module name: ntdll.dll, version: 10.0.19041.1566, time stamp: 0x1be73aa8
Exception code: 0xc0000409
Fault offset: 0x00000000000a1251
Faulting process id: 0xee0
Faulting application start time: 0x01d84937b1f899f9
Faulting application path: C:\Program Files\Remote Desktop\msrdc.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 312ec92d-6028-4c6f-9364-9be8e3d421b7
Faulting package full name:
Faulting package-relative application ID:


My organization has also had a few users experience this failure to launch with 3004.

Updating to 3128 resolved one but not the others.

Has there been a fix determined?

@kjak5150 we have the exact same problem. not everyone in our organisation, but many of them cant connect via the desktop app - downgrading works

@ChristopherRoosi Can you open a support case with the process crash dump (msrdc.exe crashing on start) for us to look at?  Here are instructions for collecting user-mode dumps.  


Thank you.