I am using the VMware Pro 12. I created a VM that I shared and configured to start automatically.
Now I have the following problem:
Whenever the host is restarted for any reason, the shared VM doesn't start because I got a message that the VMware Workstation Server is disabled and that I need to activate it in Edit ----> Preferences.
Is there a way to always keep it enabled like the previous versions?
Thanks for reporting the issue. I tried it on Ubuntu 14.04.3 host and didn't encounter the problem. After host is restarted, the shared VM is up automatically.
Can you please let me know your host, and upload ui & hostd log? Thanks.
did you checked the vmware workstation server service setting.
1. it should be on Automatic.
2. recovery Tab options should settings need to be restart service.
Find the screenshot for reference.
This didn't correct it for me. Now I have the service running but Shared VMs still needs to be enabled. When I enable it, I get an error "VMware Workstation failed to connect to the Workstation Server.".
Yes, I'm having exactly the same issue, but I suspect it only/always occurs after Windows Updates are applied. That's typically the only time I reboot. I'm in the Windows Insider (Fast) program so updates occur more frequently. But that's also why I enabled Shared Mode because I want access to my VMs after reboots...
I second this issue. Fast ring on Win 10 x64 Ent, on a domain. Every time I reboot, the Shared VM setting is disabled. The 4 services are all set to Automatic, Local System is the user, and Allow service to Interact with desktop is not checked. These are all default values; I haven't touched anything. My user is a domain admin as well as a local admin.
Solved this. The problem is that even with the "VMware Workstation Server" service set to Automatic, it doesn't actually start with Windows like it used to. Without this service the autostart shared VMs are disabled. The solution is to force the service to start with Windows.
Important... the user selected on the "General" tab cannot be "System".
In steps 8 and 9, above, the combined command to enter should be either net start "VMware Workstation Server" (with quotes around the name of the service), net start vmwarehostd, or sc start vmwarehostd.
However, none of those things actually work for me to solve the problem. While any of those commands works for me manually once I've logged in, the service still does not start automatically.
I fixed it, using a similar process that allows me to run programs with administrator rights from shell:startup when I login:
(In actuality, c:\directory, above, is named something else on my system.) I would not be surprised if either both steps 2 and 3, or just step 2, can be omitted and Task Scheduler can simply run the batch file task with administrator rights directly—but I didn't feel like rebooting my computer yet again to test the theory. (Note: It's steps 1-3, with similarly structured files in shell:startup, that allow me to run programs with administrator rights when I login.)
Let me also say that I hate whatever Microsoft has done with Windows 10 to require these gymnastics. (But, then again, the fact that vmwarehostd is not behaving the same as every other process that does start automatically is partly VMware's fault.)
I've found a simple solution, not sure why it works though. I noticed that the "VMWare Workstation Server" service doesn't start on one of my computers (but starts perfectly well on another one, oddly enough). I changed the "VMWare Workstation Server" service start option from "Automatic" to "Automatic (Delayed)", which solved the problem.
I have no idea why this works, but it does.