How To End a Hyper-V Virtual Machine that is Stuck


Have you ever had a Hyper-V virtual server get stuck?  My Hyper-V got stuck and I could not get it to move.  And, I couldn’t stop it or delete it.  I am running Windows 10 Pro Version 1607, so I thought perhaps it was my Windows version. 

I went to Google for help and found this great article at Spiceworks Community article was written in 2009 by Christopher O,  and worked for me today.

He suggests four easy steps.  I have listed his steps and then added my comments. 

1.  Download Process Explorer from Microsoft Sysinternals.  I used this link that is good as of Feb 2016.  — I had to run as Administrator.  Mark Russinovich wrote the article on  Process Explorer v16.12 which explains what Process Explorer does.  You can use it to solve other issues on .exe files or on DLL files.

2.  Find the GUID for your VM.  Look in the Virtual Machines folder where your VM resides. There should be an XML file and a folder both labelled with the same GUID. Remember or write down at least the first couple and last few characters of the guid – you’re going to need to match this.  —  For me, the beginning and end of my Hyper-V server was 186AFF9D…….137128.

3.  Find the GUID that’s running. Run Process Explorer (you may need to right-click and Run As Administrator if you get Access Denied messages) and look for a bunch of VMWP.EXE files running. Open the properties on one, go to the Image tab, and look under Command Line. As a parameter on the command will be the GUID from the Virtual Machines folder. Keep looking until you find the one with the same GUID!   — This may be a daunting task because so much information comes up.  I used the binoculars to FIND the first part of my server name.  I entered 186AFF9D.

4. Kill it!  After finding it, hit OK to the Properties window, then right-click on that VMWP.EXE and Kill Process! The Virtual Machine should immediately turn off.  — You need to close the find window, and then you should see the VWMP.EXE highlighted.  Right mouse click to select “Kill it”. 

Now, you can go back to your virtual machines directory – mine was under Documents>Virtual Machines – and delete the directory.

Big thanks to Christopher O and Spiceworks!