Tag Archives: Can’t Power On/Off

Can’t power on VM in Workstation 10 after Windows 8.1 October Rollup KB2995388

This issue has been fixed with the release of VMware Workstation 10.0.4.  VMware recommends that if you made changes to the config.ini that you remove the entry or change the value to “FALSE”.  The Workstation download can be found here.

When powering on a VM in Workstation 10 after rollup KB2995388 I see the following.


VMware is aware of the issue it would seem and there are three workarounds so far.  VMware official blog has this about it.

1.  Uninstall KB2995388 (This is an optional update).
2.  Edit the config.ini found in C:\ProgramData\VMware\VMware Workstation         and add the line:  vmmon.disableHostParameters = “TRUE”
3.  This is untested by me but it is reported that if you open Workstation in                   administrative mode (with admin rights), that it won’t have the problem.

Reboot your computer and your VMs should work again.

I did notice after making the change that the first time I start my VMs I get:
devicenotavailable notrespondingdevice

I chose “No” on both and the VMs now boot without issue.

Can’t power off/on a VM — VM is stuck

We had an issue the other day with our filers and because of it, some our machines orphaned themselves and VMware didn’t know what to do with them.  If I tried to power off the machine I would get the error,


Basically, I don’t even think the machine was on, but my vCenter server showed it as being powered on.  Luckily I found a KB article that deals with this.    http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1014165.

SSH into the host that the VM is said to be running from.  Then run the command:

esxcli vm process list

This gives you a list of all the running VMs, and the important piece you want is the World ID.  Copy that, and then run the command:

esxcli vm process kill –type=[soft,hard,force] –world-id=WorldNumber

Note: Three power-off methods are available. Soft is the most graceful, hard performs an immediate shutdown, and force should be used as a last resort.

As you can see, I ran this command and it killed the VM.  After doing this, I was able to power on the VM without issue.  I used soft and it worked.


That’s all I have for today.