I went to perform a regular task of checkign a setting on a VM, did a right click and the Hyper-V Manager hung, i have a popuo 'Microsoft Management Console' with the loading progress bar, but I cannot close it, nor close the Hyper-V Manager

I tried launching a new instance of Hyper-V Manager, which worked, but anything I do in it just hangs it again.

All VM's are working as normal.

I'd like to close the instance of MMC that is running from within Task Manager, but this is a production server and I really do not want to lose the VM's that are running if I do so, as all VM's are working perfectly despite this issue.

I'm unsure of what may happen in this scenario by force closing MMC from within Task Manager... Are the VM's likely to impacted if I do this?

Other than that, the only thing I can think of is to schedule planned maintenance and do it an an agreed time and risk having to lose the VM's or, at worst, reboot the host.

Just wondering if anyone had seen same behaviour and what the likely impact of force quitting the 'Microsoft Management Console' from within Task Manager might do to the operation of the working VM's.

The host is Windows Server 2016.



You can close the MMC from task manager and the VMs will keep running.

You can also restart the Virtual Machine Management service as well. I've had to do that once or twice when I've had an issue with the management console.

enter image description here

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.