msdtc.exe

Windows ProcessMicrosoft Corporation

Also called msdtc, distributed transaction coordinator, dtc

WindowsSystem Component

Microsoft Distributed Transaction Coordinator. It coordinates atomic transactions across resource managers. It is not Hyper-V and it is not WSL.

What you need to know

msdtc coordinates distributed transactions, not Hyper-V and not WSL.

msdtc.exe is the Distributed Transaction Coordinator. Databases, COM+, and clustered apps use it for two-phase commit. vmms.exe manages Hyper-V VMs. wslservice.exe coordinates distributions. Ending MSDTC does not shut down a VM.

Safe?: Yes, in System32
Is it Hyper-V?: No. It coordinates transactions
Should I end it?: In-flight distributed commits can fail

Feex says

If I see msdtc next to SQL or a COM+ app, I treat it as transactions. I do not open Hyper-V Manager, and I do not run wsl --shutdown to quiet DTC.

What is msdtc.exe?

msdtc coordinates distributed transactions, not Hyper-V and not WSL. The service is Distributed Transaction Coordinator. vmms.exe is VM management. wslservice.exe is WSL.

What does it do?

It enlists resource managers and commits or aborts a distributed transaction. It does not run Ubuntu and it does not host VMs.

Why is it running?

SQL Server, COM+, or another enlisted app started a distributed transaction, or the service is set to Automatic. A PC with no such apps can still have the service installed.

Is it safe?

Usually safe

System32 msdtc.exe is Microsoft DTC. An msdtc.exe in Temp is not. This is still not vmms and not WslService.

A legitimate copy normally runs from:

C:\Windows\System32\msdtc.exe

Service: Distributed Transaction Coordinator
Not Hyper-V vmms.exe
Not wslservice.exe

Can I end it?

Distributed commits can fail

Ending msdtc.exe aborts in-flight DTC work. Hyper-V VMs and WSL keep running. Restart Distributed Transaction Coordinator if those apps need it.

Can I remove it?

Do not delete msdtc.exe. Set the service to Manual only if you know no enlisted app needs DTC. Do not disable Hyper-V or WSL to "remove MSDTC."

Should it start with Windows?

The MSDTC service can be Automatic. That is not a Hyper-V or WSL Startup entry.

Normal resource behavior

These are contextual labels, not universal averages.

CPU: Follows transaction rate
Memory: Small to moderate
Disk: MSDTC log under MSDTC
Network: DTC traffic to other resource managers

File information

msdtc.exe file information
Executable name	msdtc.exe
Common legitimate path	C:\Windows\System32\msdtc.exe
Publisher	Microsoft Corporation
Signature expectation	Signed by Microsoft Windows

Common problems

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

DTC is transactions. High CPU here is enlisted apps, not vmmemWSL.

Someone disabled vmms to stop msdtc network ports

Wrong service. DTC security and firewall are Component Services, not Hyper-V Manager.

Troubleshooting

Diagnose before you change anything destructive.

Component Services > Computers > My Computer > Distributed Transaction Coordinator

That snap-in is this article. Hyper-V Manager and wsl -l -v will not show DTC logs.

Restart MSDTC after a log reset, do not replace vmms.exe

Follow Microsoft DTC repair. Leave System32\msdtc.exe in place.

Technical details

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

Sources and verification

Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. How we research.

Microsoft Learn: MSDTC · Distributed Transaction Coordinator
Microsoft Learn: MSDTC troubleshooting · Transaction coordination, not virtualization
Foxhole process map · First-party samples on Windows PCs. Not a lab benchmark.

Was this article useful?

A yes or no is enough. Pick a reason if you want, or add a short note.