If your virtual machine running on Hyper-V is stuck for some reason, stopped to respond and doesn’t start/stop/reset after clicking the corresponding buttons in the Hyper-V console, the only way out to fix this is to forcibly kill the process responsible for this VM on the host OS. We’ll show you how to force restart stuck Hyper-V VMs running on Windows Server 2016/2019 without rebooting the entire host and all running VMs (if you do not have a Hyper-V HA cluster and Live-Migration).
Hyper-V VM Stuck in the “Stopping/Starting” State
Suppose, that one of your Hyper-V VMs is stuck in the Stopping (Stopping-Critical) or Starting (Starting x%) state.
The guest OS doesn’t respond and “Turn Off”, “Shut Down” and “Reset” buttons in the Hyper-V Manager either are unavailable, or return the following error when pressed:
Failed to change state.
The operation cannot be performed while the object is in its current state.
Hyper-V Manager Stuck on “Connecting to Virtual Machine Management Service”
If your Hyper-V does not show virtual machines in the Hyper-V Manager console, and returns the “Connecting to Virtual Machine Management service” error, you need to restart the vmms.exe (Hyper-V Virtual Machine Management service) process. This is a safe operation and will not interrupt the running VMs. The easiest way to restart the vmms.exe process is through the vmms service using the services.msc console or with the PowerShell service management cmdlets:
Get-Service vmms | Restart-Service
How to Kill a Hung VM Process in Task Manager?
The only way to force shutdown restart such a stuck VM without rebooting the whole Hyper-V host is to end its running workflow in the guest OS. All VMs on the Hyper-V host are started using the vmwp.exe process (Virtual Machine Worker Process). To search for a process, you need to find out the GUID of the virtual machine.
You can get the VM GUID through the Hyper-V Manager console. Open the Hyper-V server settings. In the Server section, the location of the VM configuration files is shown (in our case it is D:\VMStore).
Open this directory in File Explorer and find the folder with the same name as your virtual machine has. Copy the GUID that is specified in the name of the VM configuration file with the *.vmcx extension.
Run the Task Manager and go to the Details tab. All virtual machines are running in their own instance of vmwp.exe. To determine which process is responsible for your VM, you need the GUID of the hung-up VM you obtained earlier. Locate the process vmwp.exe that has the GUID of your VM in the User name column. Kill this process (End Task).
The virtual machine will be forced to stop. Now you can do anything with it.
Killing a Frozen Hyper-VM using PowerShell
It is much easier to find and kill the process of the hung-up virtual machine using the PowerShell CLI. Run the PowerShell console with the administrator privileges (your account must be added to the local “Hyper-V administrators” group).
Stop-VM -Force
command, it also freezes. Obviously awaiting a response from the VM.You also need to kill the VM process by its GUID. You can get the VM GUID by its name. For example, to get the GUID of the VM with the name SVM-GUARDEDHOST1, run the command:
$VMGUID = (Get-VM "SVM-GUARDEDHOST1").ID
If you don’t want to type the full name of the VM, you can list all the VMs registered on this Hyper-V host:
Get-VM | Select Name, Id
Copy your VM GUID from the resulting list.
Find the vmwp.exe process identifier (PID) for this VMGUID:
$VMWMProc = (Get-WmiObject Win32_Process | ? {$_.Name -match 'VMWP' -and $_.CommandLine -match $VMGUID})
Then, using the Stop-Process command, you must force-terminate this process:
Stop-Process ($VMWMProc.ProcessId) –Force
This is the easy way to forcefully terminate the working process of a hung-up Hyper-V virtual machine.
Hyper-V: Failed to Change VM State
Sometimes it happens that even after killing a hung-up VM process, you cannot turn on the VM. Moreover, it freezes in the Starting state with an error:
Virtual Machine Connection Failed to Change State.
In this case, check the following options:
- Check that there is sufficient free space on the disk on which the Hyper-V VM files are stored;
- If an ISO image is connected in the VM settings, check its availability;
- Check the network adapter settings of the VM. Virtual network adapters must be connected to an existing Hyper-V virtual switch (there must be no status Network Adapter – Configuration Error for any NIC);
- Check that the Hyper-V Virtual Management Service (VMMS) is running and didn’t stuck in the Stopping state;
- Make sure that your antivirus software doesn’t block access to VM files. Add paths to the VM directory to the antivirus exclusions (please, check how to add exclusions to the built-in Windows Defender antivirus on Windows Server 2016);
- Check for Hyper-V related errors in the Event Viewer -> Applications and Services Logs -> Microsoft -> Windows -> Hyper-V-Worker.
11 comments
It’s easy to kill VM but it doesn’t start anymore if you do this. You have to restart host.
I tried to kill the VM this way and it said access denied, even though I was logged in as the administrator!
Ensure that your account is a member of the local group Hyper-V administrators and you have started elevated PoSh console.
Killing vmwp.exe intermittently works. User is member or hyperv admins, powershell started as admin. Killing process initially accepted but the proem was doesn’t die. Further attempts result in access denied errors.
Sometimes it’ll die on the first attempt to kill. If it doesn’t die then further attempts become pointless and hose restart is required.
Never had luck with this on Server 2012r2. I always end up rebooting the host to fix the issue.
[…] 下記の海外サイトで、プロセスを特定して停止させようとするケースは、VMが起動しているが、 反応がないフリーズした状態の時のみ有効のようです。 http://woshub.com/how-to-stop-a-hung-virtual-machine-on-hyper-v-2016/ […]
If Its Windows 10 pro Test environment machines , Just remove the feature restart host system and add Hyper v feature again your VM will be showing in saved state just Add Virtual switch and add to the VMs for those you were facing problem in startup.Now delete the save state and start the VM you will get your machine ready.
Thank You – was just about to throw my host machine out the window 🙂
This procesdure saved my life multiple-times on 2016 and on 2012R2 also. As soon as I killed the proccess, the VM restarted it self and booted back to normal
Thanks, thanks, thanks!
I’ve had a CPU usage of about 15/20% for a while, just because a VM was hanging shutting down. I had all the Hyper-V processed stopped, but still.
Following your guide forced the VM to stop and the vmmem process stopped using the CPU!
Thanks a lot. I was trying wsl –shutdown from one day but it was not working. As last your GUI based solution solved my problem.