vmwp.exe

Windows ProcessMicrosoft Corporation

Also called vmwp, vm worker process, virtual machine worker

WindowsSystem Component

Hyper-V VM Worker Process. Windows starts one per running Hyper-V virtual machine. It is not the management service vmms.exe.

What you need to know

vmwp is a VM worker, not the management service vmms.

vmwp.exe is the worker that runs one Hyper-V VM. vmms.exe only manages. vmmemWSL is WSL2 guest memory, not this worker. Ending a worker stops that VM, not Hyper-V Manager.

Safe?: Yes, for a running Hyper-V VM
Same as vmms?: No. This is a VM worker
Many copies?: One per running Hyper-V VM

Feex says

If I see three vmwp copies, I count three running Hyper-V VMs. I do not end vmms to stop one guest, and I do not treat vmmemWSL as a vmwp.

What is vmwp.exe?

vmwp is a VM worker, not the management service vmms. One vmwp.exe is one running Hyper-V VM. vmmemWSL is the WSL2 working set, not this worker.

What does it do?

It hosts that guest's compute on the host. It does not draw Hyper-V Manager and it does not launch `wsl.exe`.

Why is it running?

A Hyper-V virtual machine is running. Saved or off VMs should not keep a worker. WSL2 memory is a different row.

Why are there multiple copies?

Several vmwp.exe copies are several running Hyper-V VMs. That is not several vmms.exe management services and not several vmmemWSL rows.

Is it safe?

Usually safe

System32 vmwp.exe is a Hyper-V worker. A vmwp.exe in Downloads is not. This is still not vmms and not vmmemWSL.

A legitimate copy normally runs from:

C:\Windows\System32\vmwp.exe

One worker per running Hyper-V VM
Management sibling: vmms.exe
Not vmmemWSL (WSL2 working set)

Can I end it?

That VM stops

Ending vmwp.exe is a hard stop of that guest. Prefer Hyper-V Manager or Stop-VM. Ending vmms.exe only drops management. Ending vmmemWSL is the wrong name for this worker.

Can I remove it?

Do not delete vmwp.exe. Turn the VM off or remove the Hyper-V role. Do not delete System32. Uninstalling WSL does not remove Hyper-V workers.

Should it start with Windows?

A running VM starts a worker. Automatic start is a Hyper-V VM setting, not Startup Apps.

Normal resource behavior

These are contextual labels, not universal averages.

CPU: Follows that guest
Memory: Guest RAM can appear as vmmem next to the worker
Disk: That VM's VHDX
Network: That VM's virtual NIC

File information

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

Common problems

People end vmms and wonder why the guest is still hot

The worker is this file. Management can die while the VM keeps running on vmwp.

WSL RAM blamed on a Hyper-V worker

vmmemWSL is the WSL2 utility VM working set. A named Hyper-V VM is this worker plus vmmem.

Troubleshooting

Diagnose before you change anything destructive.

Hyper-V Manager: which VM is Running

Match count to vmwp copies. A WSL-only PC should not need this worker for Ubuntu.

Shut down the VM from Hyper-V, not from a vmmemWSL hunt

If you meant WSL, use wsl --shutdown. This exe is a Hyper-V worker.

Technical details

vmwp.exe technical details
Image name	vmwp.exe
Role	Hyper-V virtual machine worker

Sources and verification

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

Microsoft Learn: Hyper-V technology · Hyper-V runs each VM with a worker process
Microsoft Learn: manage Hyper-V VMs · Management is vmms, running VMs have workers
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.