vmms.exe

Windows ProcessMicrosoft Corporation

Also called vmms, hyper-v virtual machine management, vmms service

WindowsSystem Component

Hyper-V Virtual Machine Management Service. It manages Hyper-V VMs on SKUs that include Hyper-V. It is not WSL's wslservice.exe.

What you need to know

vmms is Hyper-V management, not WSL's wslservice.

vmms.exe is Virtual Machine Management Service. Hyper-V Manager talks here. wslservice.exe coordinates WSL distributions. vmcompute.exe is Host Compute Service. Ending vmms does not shut down Ubuntu the way `wsl --shutdown` does.

Safe?: Yes, when Hyper-V is installed
Same as wslservice?: No. This is Hyper-V management
Should I end it?: Hyper-V VMs lose management

Feex says

If I see vmms on a SKU with Hyper-V, I treat it as VM management. I do not look for Ubuntu in this process, and I do not end wslservice to stop Hyper-V Manager.

What is vmms.exe?

vmms is Hyper-V management, not WSL's wslservice. It is the Virtual Machine Management Service. wslservice.exe only coordinates WSL. Swapping those names is wrong.

What does it do?

It creates, starts, and configures Hyper-V VMs. Worker processes are vmwp.exe, one per running VM. It does not host `wsl -l -v`.

Why is it running?

Hyper-V is installed and something opened the management stack. Home SKUs without Hyper-V should not show a normal System32 vmms.

Is it safe?

Usually safe

System32 vmms.exe is Hyper-V VMMS. A vmms.exe in Downloads is not. This is still not WslService.

A legitimate copy normally runs from:

C:\Windows\System32\vmms.exe

Service: Hyper-V Virtual Machine Management
Workers: vmwp.exe, one per VM
Not wslservice.exe

Can I end it?

Hyper-V management drops

Ending vmms.exe disconnects Hyper-V Manager and can stall VM control. Running vmwp copies may linger. That is not `wsl --shutdown`.

Can I remove it?

Remove the Hyper-V role, not the file

Turn Hyper-V off from Windows features if you do not want VMMS. Do not delete System32\vmms.exe. Uninstalling WSL does not remove this service.

Should it start with Windows?

The vmms service starts when Hyper-V needs management. It is not a WSL Startup entry.

Normal resource behavior

These are contextual labels, not universal averages.

CPU: Low unless many VMs are changing state
Memory: Moderate for the management service
Disk: Config and VHD access through workers
Network: Live migration and management, not mstsc by itself

File information

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

Common problems

People stop WslService to close Hyper-V Manager

Hyper-V Manager talks to vmms. WSL has its own service. Two consoles, two processes.

VMs still run after they ended vmms

vmwp.exe is the per-VM worker. Management died. The guest may still be on the worker.

Troubleshooting

Diagnose before you change anything destructive.

Hyper-V Manager and services.msc: Virtual Machine Management

If that snap-in fails, this service is the article. wsl -l -v failing is wslservice, not vmms.

Do not disable Host Compute Service to "fix Hyper-V"

vmcompute is HCS. Repair or restart vmms for classic VMs. Leave System32 files in place.

Technical details

vmms.exe technical details
Image name	vmms.exe
Service	Hyper-V Virtual Machine Management

Sources and verification

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

Microsoft Learn: Hyper-V technology · Hyper-V Virtual Machine Management Service
Microsoft Learn: manage Hyper-V · vmms manages VMs, workers run them
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.