Windows Desktop client can't connect to azure virtual desktop with 1.2.3004 and 1.2.3128

Question

Windows Desktop client can't connect to azure virtual desktop with 1.2.3004 and 1.2.3128

Vardhan Joshi 56

I have azure VM and Workspace, and only one user-facing this issue to connect VM after WVD client update it works fine with 1.2.2927 (old) version.

Event Log:

Faulting application name: msrdc.exe, version: 1.2.3128.0, time stamp: 0x62634ce9

Faulting module name: ntdll.dll, version: 10.0.19041.1682, time stamp: 0x7b5414ec

Exception code: 0xc0000409

Fault offset: 0x00000000000a1221

Faulting process id: 0x4aac

Faulting application start time: 0x01d8615557275792

Faulting application path: C:\Users\User\AppData\Local\Apps\Remote Desktop\msrdc.exe

Faulting module path: C:\windows\SYSTEM32\ntdll.dll

Report Id: ea1bf897-db2d-4bfd-9561-540f6eea5409

Glen Whitley 1 Reputation point

2022-05-26T18:46:42.657+00:00

We are also seeing the same issue with about 5 out of 300 clients. If you find a solution Please update. Thanks

Users click on the app they wish to launch, a screen pops up saying connecting, then disappears.
Rolling the client back before .3004 resolves the issue.
Event Viewer shows the following error:
Faulting application name: msrdc.exe, version: 1.2.3130.0, time stamp: 0x62758931
Faulting module name: ntdll.dll, version: 10.0.19041.1682, time stamp: 0x7b5414ec
Exception code: 0xc0000409
Fault offset: 0x00000000000a1221
Faulting process id: 0x3600
Faulting application start time: 0x01d87127ed246c11

We have run SFC check, DSIM scans, multiple reinstalls of versions after .3004 but still have had no luck.
Jason Chapman 1 Reputation point

2022-06-01T17:31:04.017+00:00

I'm also having this exact issue on two of four machines. A pair of HP desktops are fine. A pair of Lenovo laptops, however, have this problem with .3128 and .3130.
Vardhan Joshi 56 Reputation points

2022-06-01T17:56:28.597+00:00

I am using AVD client from Microsoft store as workaround. Still Microsoft collecting logs but no luck.

2 answers

Your answer

Glen Whitley 1 Reputation point

2022-05-26T18:46:42.657+00:00

We are also seeing the same issue with about 5 out of 300 clients. If you find a solution Please update. Thanks

Users click on the app they wish to launch, a screen pops up saying connecting, then disappears.
Rolling the client back before .3004 resolves the issue.
Event Viewer shows the following error:
Faulting application name: msrdc.exe, version: 1.2.3130.0, time stamp: 0x62758931
Faulting module name: ntdll.dll, version: 10.0.19041.1682, time stamp: 0x7b5414ec
Exception code: 0xc0000409
Fault offset: 0x00000000000a1221
Faulting process id: 0x3600
Faulting application start time: 0x01d87127ed246c11

We have run SFC check, DSIM scans, multiple reinstalls of versions after .3004 but still have had no luck.
Jason Chapman 1 Reputation point

2022-06-01T17:31:04.017+00:00

I'm also having this exact issue on two of four machines. A pair of HP desktops are fine. A pair of Lenovo laptops, however, have this problem with .3128 and .3130.
Vardhan Joshi 56 Reputation points

2022-06-01T17:56:28.597+00:00

I am using AVD client from Microsoft store as workaround. Still Microsoft collecting logs but no luck.

Answer 1

Vardhan Joshi 56

TSPrint from Right Network causing this issue. Uninstalled it.

VF 0 Reputation points

2024-10-22T15:22:04.4133333+00:00

This was actually my issue. THANK YOU!

Had already spent over an hour running sfc, dism, reinstalling the app, restarting and troubleshooting. Was going to reinstall Windows next lol.

Answer 2

deherman-MSFT 38,021 Microsoft Employee Moderator

@Vardhan Joshi Sorry to hear you are experiencing issues. I am reaching out privately so we can work with you directly.

Vardhan Joshi 56 Reputation points

2022-05-06T17:03:34.09+00:00

Thanks for your quick response.

Please let me know what should be the troubleshooting steps or how you would like to process further.
Matt 1 Reputation point

2022-06-09T12:46:37.92+00:00

We too have been experiencing this issue since 1.2.3004 with about 20 machines out of 1500. Only work arounds so far have been reverting back to a 1.2.2 version which is no longer becoming acceptable due to security vulnerabilities. Any help would be greatly appreciated.
Lee Staley 1 Reputation point

2022-06-29T15:09:57.28+00:00

This is still happening with version 1.2.3213.0 do you have a fix that can be posted here? We have run SFC check, DSIM scans, multiple reinstalls but no fix so far. Thank you.
Christopher Oleson 1 Reputation point

2022-08-02T21:57:37.197+00:00

We are still experiencing this problem. Has there been any resolution?
Vardhan Joshi 56 Reputation points

2022-08-02T22:04:50.29+00:00

TSPrint from Right Network was causing this issue. We have uninstalled it and works fine.

Check VPN or other applications that can interrupt the connection.
Mike Kulin 1 Reputation point

2022-11-08T20:31:23.21+00:00

Hi @deherman-MSFT

We are seeing this same problem 11/8/22022

Reinstalling msrdc.exe did not help, we can connect from another computer without issue. (also tried basics like restarting, subscribe/unsubscribe)

Some diagnostic info:

Faulting application name: msrdc.exe, version: 1.2.3577.0, time stamp: 0x63447348 Faulting module name: ntdll.dll, version: 10.0.19041.1682, time stamp: 0x7b5414ec Exception code: 0xc0000409 Fault offset: 0x00000000000a1221 Faulting process id: 0x3a90 Faulting application start time: 0x01d8f3addb95c90b Faulting application path: C:\Program Files\Remote Desktop\msrdc.exe

Share via

Windows Desktop client can't connect to azure virtual desktop with 1.2.3004 and 1.2.3128

2 answers

Your answer