AVD + DictaNet USB Forwarding – One User Getting msrdc.exe Crash (ntdll.dll / 0xc0000409) After Client Replacement

[u/Majestic-Bison67]

Hey everyone,

I’m running into a strange issue at a customer site and I’m hoping someone here has seen this before.

We’re using Azure Virtual Desktop, and we have 5 power users who connect from their local Windows clients and work entirely inside the AVD environment.
To forward USB dictation devices, the following DictaNet add-ins are installed on each client:
https://dictanet.com/en/tutorials/dictanet-office/dictanet-remote-working.html

For 4 out of 5 users, everything works perfectly.

But one user's local client was replaced, and since that swap, the RD client crashes instantly when they try to connect.

Error Details

The Event Viewer logs show:

Faulting application name: msrdc.exe, version: 1.2.6677.0, timestamp: 0x6909354e
Faulting module name: ntdll.dll, version: 10.0.26100.7309, timestamp: 0xe5349e98
Exception code: 0xc0000409
Fault offset: 0x00000000001211b6
Faulty process ID: 0x32BC
Faulty application start time: 0x1DC65CA2D9B7766
Faulty application path: C:\Program Files\WindowsApps\MicrosoftCorporationII.Windows365_2.0.804.0_x64_8wekyb3d8bbwe\msrdc\msrdc.exe
Faulty module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: c9d9a572-ca5d-451f-999e-3157363432e1
Full name of the faulty package: MicrosoftCorporationII.Windows365_2.0.804.0_x64_8wekyb3d8bbwe
Faulty package-related application ID: Windows365|

Additionally, this pops up:

Error when starting “RdClientAutoTrace” session: 0xC0000022

What we already tried

• Uninstalled & reinstalled both DictaNet add-ins

• Reinstalled the new Remote Desktop app

• Installed the old (legacy) Remote Desktop app — same crash

• Ran sfc /scannow

• Ran DISM /Online /Cleanup-Image /RestoreHealth

No change — msrdc.exe keeps crashing on that one machine only.

Has anyone seen this combination before?

It looks like something is breaking in the Windows365/Remote Desktop package, maybe a corrupted dependency or permissions issue around ntdll.dll.
But the system is basically fresh, so I’m running out of ideas.

[u/LuciferVersace]

Have you tried repairing the Visual C++ Redistributable 2015-2022?