Skip go content

msdtc.exe

Windows ProcessMicrosoft Corporation

Awọn iwe-aṣẹ wiwa iwe-aṣẹ msdtc, distributed transaction coordinator, dtc

WindowsSystem Component

Microsoft Distributed Transaction Coordinator. E dey coordinate atomic transactions across resource managers. E no be Hyper-V and e no be WSL.

Wetin you need know

msdtc dey coordinate distributed transactions, no be Hyper-V and no be WSL.

msdtc.exe na Distributed Transaction Coordinator. Databases, COM+, and clustered apps dey use am for two-phase commit. vmms.exe dey manage Hyper-V VMs. wslservice.exe dey coordinate distributions. To end MSDTC no dey shut down VM.

E safe?
Check the running file path, signature, and publisher. Name alone no fit confirm say e safe.
Shey na Hyper-V?
No. E dey coordinate transactions
I suppose end am?
Distributed commits wey dey run fit fail
Feex tok say
If I see msdtc near SQL or COM+ app, I dey treat am as transactions. I no dey open Hyper-V Manager, and I no dey run wsl --shutdown make DTC for keep quiet.

Wetin be msdtc.exe?

msdtc dey coordinate distributed transactions, no be Hyper-V and no be WSL. The service na Distributed Transaction Coordinator. vmms.exe na VM management. wslservice.exe na WSL.

Wetin e dey do?

E dey enlist resource managers and commit or abort distributed transaction. E no dey run Ubuntu and e no dey host VM dem.

Wetin make am dey run?

SQL Server, COM+, or another enlisted app start distributed transaction, or dem set the service to Automatic. PC wey no get dat kind apps fit still get the service installed.

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 'msdtc.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

System32 msdtc.exe na Microsoft DTC. Any msdtc.exe inside Temp no be am. Dis one still no be vmms and e no be WslService.

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

C:\Windows\System32\msdtc.exe

  • Service: Distributed Transaction Coordinator
  • No be Hyper-V vmms.exe
  • No be wslservice.exe

I fit end am?

Distributed commits fit fail

To end msdtc.exe dey abort DTC work wey dey run. Hyper-V VMs and WSL go continue to run. Restart Distributed Transaction Coordinator if dose apps need am.

I fit comot am?

No

No delete msdtc.exe. Set the service to Manual only if you know say no enlisted app need DTC. No disable Hyper-V or WSL to "comot MSDTC."

E suppose start with Windows?

The MSDTC service fit dey Automatic. Dat one no be Hyper-V or WSL Startup entry.

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

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

Common wahala dem

Filename mills dey call any "vm" or "service" virtualization

DTC na transactions. High CPU here na enlisted apps, no be vmmemWSL.

Pesin disable vmms to stop msdtc network ports

Wrong service. DTC security and firewall na Component Services, no be Hyper-V Manager.

How to troubleshoot

Diagnose before you change anything wey fit scatter things.

Component Services > Computers > My Computer > Distributed Transaction Coordinator

Dat snap-in na dis article. Hyper-V Manager and wsl -l -v no go show DTC logs.

Restart MSDTC afta log reset, no replace vmms.exe

Follow Microsoft DTC repair. Leave System32\msdtc.exe for where e dey.

Technical details

Technical details
msdtc.exe technical details
Image name msdtc.exe
Service Distributed Transaction Coordinator

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?