There's a limitation in Windows which will sometimes be hit when an instance of VMware Workstation tries to manage lots of VMs simultaneously. If the Workstation UI hits that architectural limit (which can happen at around 28 VMs), the UI will crash.
Earlier versions of Workstation had a check in place to prevent this from happening, but that check was mistakenly omitted from recent versions, allowing you to possibly open a few more VMs, but introducing the risk of a crash. Workstation 12 reinstates the check. In some future version Workstation will hopefully end up being restructured to avoid the underlying limitation altogether, but we're not there yet.
This particular limitation does not relate to the total number of VMs which are running on the host, so (as the message suggests) you should be able to just open a second instance of VMware Workstation and run more VMs in that second instance. If I remember correctly, I think we have a hard limit of 64 concurrently running VMs on Windows hosts.
Hope this helps!
Can you tell us more on the underlying Windows limitation?
Is there any tuning possibility?
VMware Workstation 10 let me open more than 60 VMs without any problem.
I can understand that "running" many VMs simultaneously will hit some resource limitation, but here the error pops up when selecting the VM in the library (just clicking on the VM in the left pane).
The limitation is enforce by Windows API WaitForMultipleObjects. The workaround is to open another instance of Workstation.
Greetings I'm seeing the same error with VM Workstation 15.0.2
I have 33 VMs setup, but get the error when as few as five or six VMs are actually running.
Have been able to run 25 concurrent VMs but latest Version (15.0.2) seems to have some issues..
Any fixes planned for 15.0.3 ?
VM15 Bug.JPG 76.4 K
According to Davius 's comments, the limitation does not relate to the number of VMs running on the host, but the number of VMs that are opened (i.e., a tab of the VM is opened). Please close VMs that are not being used. Or run another instance of VMware Workstation.
Your answer worked for me, regarding this posts error.
What I did was to close the open tabs above the Virtual Machine display window of VMWare Workstation Pro 15.0.2
I was then able to open the Virtual Machines with red X on them, without removing, as suggested by the error window.
A very simple Fix, when you know how.
Very simple indeed, thank you for the hint !
I had to tick the Menu>View>Customize>Tabs option in order to make the tabs visible - and then I had to close each one. Never did have a clue that all these were "open" in some way. Then it was possible to click on the new VM (my 29th) and the red x just went away.
In case someone needs more than 30 machines in a single UI.
VMWare Workstation keeps its configs separated for each Windows user.
So I've created a second user account and now can launch second VMW window as another user (Shift+RMB>launch as another user).
I've also found it useful for VMWares that I've installed on external SSD. I'll keep them now on a different user profile so they don't mess up with the list when SSD disconnected.
I also added .lnk file to the desktop
Create>New shortcut>Runas /savecred /user:USERNAME "C:\Program Files (x86)\VMware\VMware Workstation\vmware.exe"