I recently did some updates to a Server 2016 box which acts as a Hyper-V Hypervisor. After performing the updates the server was hanging at "Shutting down service: Hyper-V Virtual Machine Management". It was in this state for quite a while so I gave the server a little nudge by restarting it (I know – I'm an idiot).
When the machine came back up it was hanging at the Windows symbol with the spinner. I restarted again and ran into several issues (such as the OS not booting at all). I removed a disk that was (software) mirroring the boot drive from my RAID array, and now the machine is showing some signs of life. It booted and did some "Working on updates" things, but now it is stuck at "Shutting down service: Hyper-V Virtual Machine Management" again.
What's my best course of action here? Is it just to leave it or to force a restart?
Best Answer
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'.