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

Question

question

varjsh asked May 6, '22 varjsh commented Aug 2, '22

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

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

azure-virtual-desktop remote-desktop-client

· 3

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

GlenWhitley-0578 · May 26 at 06:46 PM

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.

0 ·

JasonChapman-2829 · Jun 01 at 05:31 PM

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.

0 ·

varjsh JasonChapman-2829 · Jun 01 at 05:56 PM

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

0 ·

Answer 1 · 2022-05-06T16:59:05.943Z

deherman-MSFT answered May 6, '22 varjsh commented Aug 2, '22

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

· 5

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

varjsh · May 06 at 05:03 PM

Thanks for your quick response.

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

0 ·

Matt-0985 · Jun 09 at 12:46 PM

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.

0 ·

inkedmicrosoftteams-image-3-li.jpg (882.0 KiB)

LeeStaley-9925 · Jun 29 at 03:09 PM

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.

0 ·

ChristopherOleson-0546 · Aug 02 at 09:57 PM

We are still experiencing this problem. Has there been any resolution?

0 ·

varjsh ChristopherOleson-0546 · Aug 02 at 10:04 PM

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.

0 ·

Answer 2 · 2022-06-30T18:36:16.033Z

varjsh answered Jun 30, '22

TSPrint from Right Network causing this issue. Uninstalled it.

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

question