Forum Discussion
Microsoft Remote Desktop Client crashes when connecting
Using "newer" versions of the Microsoft Remote Desktop Client (client versions newer than 1.2.29) the msrdc.exe app crashed upon starting the connection to the resource. Version 1.2.29XXX connects just fine but anything newer and it starts having issues. I have only seen this on what seems to be random machines across several different clients/tenants/hostpools making it especially tough to narrow down what the underlying issue is.
The subscribe process authenticates successfully and shows the resources in the feed properly but upon launching the Remote Desktop connection the msrdc.exe crashes right away.
The only commonality is that i see this event id on all the machines (both win10 and win11 workstations):
Faulting application name: msrdc.exe, version: 1.2.4159.0, time stamp: 0x645938cf
Faulting module name: ntdll.dll, version: 10.0.22621.1485, time stamp: 0xb7f0154a
Exception code: 0xc0000409
Fault offset: 0x00000000000a3346
Faulting process id: 0x0x3554
Faulting application start time: 0x0x1D9844F7F5FB6DF
Faulting application path: C:\Program Files\Remote Desktop\msrdc.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 3dd4c0a1-bc99-4a24-a859-b7a5cda39e3b
Faulting package full name:
Faulting package-relative application ID:
7 Replies
- OleevrCopper Contributor
Salut, grace à vos réponses, j'ai pu identifier que l'appli TSSCAN version 3.5.0.4 posait ce problème sur certains de nos PC. Plus de crashe de Remote Desktop au chargement d'une application !
- GWhitleyCopper Contributor
I know this is an old post but has anyone found a solution for this. With the transition to the new Windows App we have found it fails to work with TS Print, with is necessary for QB Right Networks. Using the old version of the client is still our workaround but no idea how long that will continue to work.
- mlinsleyCopper Contributor
I have users now getting that same error. Except msrdc.exe version is 1.2.5559.0 and the ntdll.dll version is 10.0.19041.4522, Faulting process id is 0x4990. They are on Windows 10. I have uninstalled and re-installed MSRD, When I try to repair it, it says that it cannot find the location to repair. So, it looks like it's not installing correctly? Even though I uninstalled and reinstalled. Any new ideas of what it could be?
- pbear25Copper Contributor
pbear25 We have TSPrint and TSScan installed on almost every workstation that connects to AVD host pools using the RDClient app (https://aka.ms/avdclient) but it's only a few random ones that show this crashing behavior.
I worked with Microsoft support on this a few months back and after a couple hours of troubleshooting their solution/workaround was to just use the 1.2.29 version. I havent come across any new cases in the last month or more but i think all of our workstations that had issues are using the older version still.
- rePellCopper Contributor
In our case, the culprit was TSScan and/or TSPrint, which we had installed due to some other Remote Desktop hosting provider.
- kspringerCopper ContributorThis fix my issue but I don't understand why is having a a conflict
- lkeltner_the20Copper ContributorThis fixed it for us today after removing those apps. Any workarounds found to keep them installed and not conflicting?