Skip go content

msrdc.exe

Application ProcessMicrosoft Corporation

Awọn iwe-aṣẹ wiwa iwe-aṣẹ msrdc, microsoft remote desktop client, avd client, windows app rdp

WindowsApplication

Remote Desktop client from di Store / MSRDC stack (Azure Virtual Desktop and di newer Remote Desktop app). E no be mstsc.exe.

Wetin you need know

msrdc na di newer Remote Desktop client, no be mstsc.exe.

msrdc.exe na MSRDC, di client wey di Store Remote Desktop app, Windows App, and Azure Virtual Desktop dey use. mstsc.exe na di normal inbox Remote Desktop Connection wey dey inside System32. To end msrdc no dey remove mstsc. rdpclip.exe still dey inside di remote session.

E safe?
Check the running file path, signature, and publisher. Name alone no fit confirm say e safe.
E be di same thing as mstsc?
No. Dis na di newer client
I fit end am?
Dat Store/AVD window go close
Feex tok say
If na me open di Store Remote Desktop or Windows App, na msrdc I go look for. I no dey go troubleshoot System32\mstsc for dat window.

Wetin be msrdc.exe?

msrdc na di newer Remote Desktop client, no be mstsc.exe. Inbox Remote Desktop Connection still be System32\mstsc.exe. Dis image na di Store / AVD / Windows App client.

Wetin e dey do?

E dey connect to AVD, Windows 365, and workspace feeds wey di old mstsc UI no dey fit host di same way. E no dey accept incoming RDP like TermService.

Wetin make am dey run?

You open Windows App, Remote Desktop from Store, or AVD feed. Any .rdp file wey still dey show Remote Desktop Connection na often mstsc instead.

Inspect the running instance

Inside Windows PowerShell, this read-only query show matching process IDs, creation times and executable paths on this PC. (pcm)

Get-CimInstance -ClassName Win32_Process | Where-Object { $_.Name -eq 'msrdc.exe' } | Select-Object ProcessId, ParentProcessId, CreationDate, Name, ExecutablePath | Format-List

No result or a path we no fit access is inconclusive. Protected processes fit restrict access, and process IDs fit be reused. Keep personal paths local. (pcm)

Use the file-identity guide to compare signatures and product metadata. A filename alone no fit establish safety. (pcm)

E dey safe?

Check dis running file

Msrdc wey Microsoft sign wey dey under Program Files\Remote Desktop or WindowsApps na di newer client. Any msrdc.exe inside Temp no be am. Dis one still no be mstsc.

Compare the recorded location with the actual file. A familiar folder alone no fit establish identity. (pcm)

C:\Program Files\Remote Desktop\msrdc.exe

  • Dem still dey see am under WindowsApps for di Store package
  • Inbox sibling: System32\mstsc.exe
  • Publisher: Microsoft Corporation

I fit end am?

E dey close dat newer client

To end msrdc.exe dey close Windows App / Remote Desktop connections wey use MSRDC. System32\mstsc.exe fit remain. TermService on top host machine no go change.

I fit comot am?

Uninstall di app, no be mstsc

Uninstall Remote Desktop or Windows App from Apps. No delete System32\mstsc.exe say you wan "remove MSRDC." No delete System32.

E suppose start with Windows?

Na di Store app or workspace shortcut dey start am. Inbox mstsc get im own shortcuts.

Measure resource use

Measure the current process rather than assume a universal baseline
CPU and memory Compare several observations for the same PID and workload. This entry get no independently measured universal baseline. (pcm)
Disk and network Attribute activity to the actual process and current task; a filename alone no fit establish expected destinations or transfer volume. (pcm)

File information

msrdc.exe file information
Executable name msrdc.exe
Recorded installation path C:\Program Files\Remote Desktop\msrdc.exe
Publisher Microsoft Corporation
Signature check Inspect the actual file; this entry no dey certify its certificate identity. (pcm)

Common wahala dem

Helpdesk talk say "open mstsc" and di user go open Windows App

Different exe. Subscribe to workspace here. Classic computer-name box na mstsc.

Clipboard break, dem dey repair mstsc

rdpclip still be di session redirector. To repair inbox Remote Desktop Connection no dey replace msrdc.

How to troubleshoot

Diagnose before you change anything wey fit scatter things.

Open file location on di connected client

Program Files\Remote Desktop or WindowsApps na for dis article. System32\mstsc.exe na Remote Desktop Connection.

Update Windows App / Remote Desktop from Store

AVD feeds need dis client make e dey updated. No go replace mstsc.exe from forum zip make you take fix MSRDC.

Technical details

Technical details
msrdc.exe technical details
Image name msrdc.exe
Role MSRDC / Azure Virtual Desktop client

Check the identity of running file

A filename alone no fit establish safety. Verify the actual path, signature and product identity. (pcm)

Sources and verification

Recorded source label: August 2026. Dis label no establish independent verification. How we dey do research.

Dis article make sense to you?

Yes or no dey enough. Choose reason if you want, or add short note.

Dis article make sense to you?