Server 2016 Running Hyper-V Stuck in "Shutting down service: Hyper-V Virtual Machine Management"

In my case, I removed all the network cables from physical server and the server shutdown was quick. Its not a solution, could be a work around for quick resrart.

As this is still an issue in 2020 - I might have found a solution for at least some cases (happened to me just yesterday/today at the end of an already loooong workday, when I had no more patience to wait any longer before starting my 2 hour ride home after midnight):

After about an hour of waiting and no reaction whatsoever i tried pinging all the VMs running on the stuck HyperV. Eventually one DID answer the ping (damn them Exchange-Servers...). I tried to shut the VM in question down forcefully with "shutdown /i" (CMD) which just resulted in a "permission denied" message (could have to do with the reason the HyperV had issues putting it to hypernation/pause). I then tried to connect me to the server via RDP which worked like a charm. I manually shut the server down within it's own gui and just a few minutes later the HyperV was successfully rebooted. Only had to restart the trolling VM in HyperV and everything was alife and kickin' again.

May have been a fluke, still have to verify next time (or better shut down the VMs beforhand anyway...), but hey, I would have loved that straw yesterday...

All the best to all admins-pals out there,

Arno

I have seen many users (myself included) experience this problem if the pagefile is on a different volume from the VM's boot volume with Windows Server 2016 as the OS running on the VM. I'm not sure if that's consistent with your situation, but if it is, that could be the cause for your problem.

For me, the fix (filled with its own problems) was to move the pagefile to the C drive on the VM. Before that, the VM could NEVER completely shut down. After then it shut down properly every time.

I have read that for many people, it was able to shut down properly with the pagefile on a different volume the first 1-3 times, then stopped working after that. That's probably true in my case also, but I don't recall that part with certainty.

Leave it and it normally eventually shuts down nicely (could be hours).

I have found that I see this issue on new, or quite new server builds. Something happens with some Windows updates that come down while the system is young, then this situation arises. I have seen this on Server 2008, 2012 and now 2016 (would be nice to have a 'fix' Microsoft, or at least a better message 'Shutting down Virtual Machine Management, please do not turn off your computer, this could take an extended amount of time'.