vmcompute.exe

Windows ProcessMicrosoft Corporation

Also called vmcompute, host compute service, hcs

WindowsSystem Component

Host Compute Service (HCS). It runs containers and the WSL2 utility VM compute path. It is not Hyper-V Virtual Machine Management (vmms.exe).

What you need to know

vmcompute is HCS, not Hyper-V vmms.exe.

vmcompute.exe hosts the Host Compute Service. WSL2 and Windows containers use this compute plane. vmms.exe is Hyper-V Virtual Machine Management for SKUs that run full Hyper-V VMs. Ending HCS does not stop vmms, and the reverse is also true.

Safe?: Yes, in System32
Same as vmms?: No. This is HCS, not Hyper-V VMMS
Should I end it?: Containers and WSL2 compute can drop

Feex says

If WSL2 or a container is up, I expect vmcompute. I do not open Hyper-V Manager and treat vmms as this service.

What is vmcompute.exe?

vmcompute is HCS, not Hyper-V vmms.exe. Host Compute Service runs utility VMs and containers. vmms.exe manages classic Hyper-V virtual machines on SKUs that include that role.

What does it do?

It answers HCS calls to create and run compute systems. It does not open Hyper-V Manager and it does not replace wsl.exe.

Why is it running?

WSL2, docker, or another HCS client started a utility VM or container. No such workload often means this service should be idle.

Is it safe?

Usually safe

System32 vmcompute.exe is Host Compute Service. A vmcompute.exe in Temp is not. Seeing this file is not proof that vmms.exe is "the same process."

A legitimate copy normally runs from:

C:\Windows\System32\vmcompute.exe

Service: Host Compute Service (vmcompute)
Used by WSL2 and containers
Not vmms.exe (Hyper-V management)

Can I end it?

HCS workloads drop

Ending vmcompute.exe can stop containers and the WSL2 compute path. Hyper-V VMs managed by vmms.exe are a different stack. Restart Host Compute Service if those workloads should return.

Can I remove it?

Do not delete vmcompute.exe. Turn off unused optional virtualization features from Windows, not Explorer. Disabling vmms does not remove HCS.

Should it start with Windows?

Host Compute Service starts on demand. It is not Startup Apps and it is not vmms.

Normal resource behavior

These are contextual labels, not universal averages.

CPU: Follows container or utility-VM activity
Memory: Service is small. Guest RAM is vmmem
Disk: Image and VHDX I/O on the workload
Network: Container and VM networking, not RDP

File information

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

Common problems

People disable Hyper-V Manager thinking they stopped HCS

vmms is the management service. WSL2 can still use vmcompute. Two names, two jobs.

Containers fail after someone ended vmcompute to "free RAM"

Restart Host Compute Service. The RAM you wanted is usually vmmem, not this host.

Troubleshooting

Diagnose before you change anything destructive.

services.msc: Host Compute Service, not Virtual Machine Management

vmcompute is HCS. vmms is Hyper-V VMMS. Restart the one that matches the workload.

For WSL2 RAM, use wsl --shutdown, not an HCS file replace

vmmemWSL is the working set. This exe is the compute service. Leave System32 alone.

Technical details

vmcompute.exe technical details
Image name	vmcompute.exe
Service	Host Compute Service

Sources and verification

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

Microsoft Learn: Host Compute Service · HCS is vmcompute, the compute API for containers and utility VMs
Microsoft Learn: Hyper-V isolation containers · Containers use the compute service, not vmms as the HCS host
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.