0

Today, this is a second time recently when while trying to restart Windows Server 2016 host machine, it gets stuck on "Shutting down service: Hyper-V Virtual Machine Management" (yes, the virtual machine had been stuck, I saw it in the Hyper-V manager) for already some 20 minutes - I do not want to hard-reset the host.

Where can this too-long timeout be adjusted, please? Thanks! I would like to set it to some reasonable time (e.g. 20 minutes)

1 Answer 1

0

This same problem is evoked in the post Server 2016 Running Hyper-V Stuck in "Shutting down service: Hyper-V Virtual Machine Management".

The summary of the answers :

  • This can happen after a Windows Update to the VM. Wait for it to finish, even if it takes hours.

  • RDP or SSH into the VM and use the shutdown command.

Some other answer in this post were not included here, because of low pertinence.

3
  • Thanks for the summary, unfortunately, it does not solve anything. 1) I can't "wait hours" just because of some stuck update - there are users to work on the machine... I may wait at night, but not during work hours... 2) You cannot RDP into a machine which is already in shutting down process... So my question remains unanswered. Thanks for reply, though.
    – crysman
    Commented Jul 2, 2022 at 19:20
  • If waiting doesn't help, and RDP is not working, then I hope that you have a backup for the VM. You may forcefully stop it and restart, and perhaps Windows Update will recover/undo the update.
    – harrymc
    Commented Jul 2, 2022 at 19:44
  • Yes, but this requires manual intervention, not optimal.
    – crysman
    Commented Jul 6, 2022 at 17:11

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .