Host not Responding - Hyper-v Virtual Machine Management service in Stopping state

Question

_{Wednesday, April 13, 2016 1:25 PM}

Hello,

I have recently encountered a situation in which the Hyper-v Virtual Machine Management service (vmms) was stuck in Stopping state on a hyper-v host and all the VMs on that host were showing as Host not Responding in VMM. Some of the VMs were hung, but most we running.

Efforts to force stop vmms, either through Process Explorer and taskkill, were not successful. Got access denied. Ultimately the host had to be rebooted, but I'd like to avoid having to restart the host in the future. Vmms has RPC and WMI as dependencies.

Does anyone know what could be the reason for Access Denied when trying to force kill the process, or a way to kill it without restarting the host?

Regards,

ttwa

All replies (3)

_{Saturday, April 16, 2016 2:32 AM}

TTwa:

i did that method using process explorer on sysinternals to kill the process instead of restarting the hosts server, which my is application critical on the production. You can try it.

https://community.spiceworks.com/how_to/528-killing-ending-a-hyper-v-virtual-machine-that-is-stuck

_{Monday, April 25, 2016 4:45 PM}

Answer unproposed as I had already tried killing the service with process explorer and taskkill and that didn't work. The question is why didn't it work. Maybe there's something that keeps the service from being restarted? Any ideas would be appreciated.

Regards,

ttwa

TTwa

_{Tuesday, May 9, 2017 4:03 AM}

did you solve this yet? I met this also.