Faulting application name: msrdc.exe, version: 1.2.6424.0, time stamp: 0x64ff8f26 Faulting module name: ntdll.dll, version: 10.0.26100.4061, time stamp: 0x1d4ecf98

Hi. Does the crash occur only with specific RemoteApps, or does it affect all AVD connections, including full desktop sessions? Also, is your system running any third-party antivirus, endpoint protection, or security policies such as AppLocker or Windows Defender Application Control that could be interfering with system files or Remote Desktop components?

If you have not tried this yet, begin by checking for system file corruption or misconfigurations:

1. Open Command Prompt as Administrator
2. Run: sfc /scannow
3. Then run: dism /online /cleanup-image /restorehealth

These commands will scan your Windows installation for damaged or missing system files, including core components like ntdll.dll, and attempt to repair them.

Hi ArunDaniel R (BLR IT)

Based on the faulting module and exception code, it appears that the Remote Desktop client (msrdc.exe) is encountering a structured exception (0xc0000409) within ntdll.dll, which typically indicates a stack buffer overrun or corruption in low-level system calls.

Preliminary Analysis

The fault offset in ntdll.dll and the absence of a faulting package suggest this is a system-level crash, not tied to a specific UWP container. This kind of failure can be triggered by:

• Incompatible or corrupted system files

Conflicts with third-party security or graphics software

Issues with the Remote Desktop client version itself

Recommended Steps to Resolve

Repair or Reinstall Remote Desktop Client Uninstall the current version of the Remote Desktop client and reinstall the latest stable release from Microsoft's official site.

1. Run System File Checker Open an elevated Command Prompt and run: sfc /scannow This will scan and repair any corrupted system files, including ntdll.dll. Check for OS Updates Ensure the system is fully updated via Windows Update. The faulting module version (10.0.26100.4061) suggests a recent build—verify that cumulative updates have been applied cleanly. Review Third-Party Interference Temporarily disable or uninstall third-party antivirus, endpoint protection, or overlay software that may hook into system DLLs. Collect Crash Dump for Deeper Analysis If the issue persists, enable crash dumps for msrdc.exe via registry and analyze the dump using WinDbg to pinpoint the failing call stack.

I hope these steps are useful for you.

Best regards,

Quinnie Quoc.