MKS: too many socket attempts after upgrading to 14.1.3 build-9474260

[neckTwi]

None of the answers at

Workstation 14 Player MKS: too many socket attempts

worked

[neckTwi]

when creating a new virtual machine, upon finish, one of the parameters is invalid, dialog pops up.

I am using a physical disc with one of the partitions as hard disk

[JohandeKlerk]

I also got that error after upgrading.

Also see: View the full discussion

I think it is related.

[Zongmin]

Can you try to run VMware Workstation Pro as  Administrator and see if this problem can still be reproduced?

[akoppel]

Same for me on two different Systems:
One Power-Workstation that's running quite well for a long time (Windows 10/64)
One Microsoft Surface Book (the biggest one)
I have received these mysterious errors "MKS to many socket attempts". I have tried all the suggestions found in the net, have tried the vmservices (all of them are running), have tried a new install, have removed the tab, running it in the background and opened it again, changed firewall settings, changed virus-scanning, have tried running vmware as an admin. Nothing has helped.
But there was a strange behavior:
While running my Linux-vm, I got the mysterious error. Running one of my old XP-VMs using the same WMWare-Workstation-build, everything is running quite well.
There is nothing special with my Linux-VM, I have used since several years now.

Now I have completely uninstalled the new version and I have installed an old 14.1.1 ... everything is running as expected.
I have used the 14.1.1 because I did not have a 14.1.2. I have used 14.1.2. since it was build and it also works quite well. version,

Looks like there is a big bug in the new build.

My suggestion to solve the problem is: Uninstall the new version and install an old one until the bug was fixed with a new version.

[bonnie201110141]

Did your Linux VM use physical disk? Any special setting with your Linux VM? Normally running Workstation as admin should resolve the issue if the VM has a physical disk configured. Please upload ui log (check ui log location from Help > About VMware Workstation) and vmware.log under your VM directory. Thanks a lot!

[akoppel]

I did not use a physical disk!
I have looked into *ui.log.
There is an entry concerning the authd:
Vix: [21940 foundryVMPowerOps.c:5947]: Error VIX_E_HOST_TCP_SOCKET_ERROR in FoundryVMOpenSocketToVMXThroughAuthd(): unable to contact authd: Failed to read vmware-authd port number: Cannot connect to VMX: D:\vmware\Invep9\blabla.vmx
(blabla.vmx ist by virtual system)

I have checked the system. authd was running quite well (the same for all the other daemons), any firewall and virus checker was switched of (ignoring the windows-10-warnings)
Using an old vmware-build (14.1), the same configuration runs without any problems.
By the way, the virtual Linux system itself is running quite well. I am able to login to the system using ssh. The only thing not working is the display (black screen, producing the error of this thread).

If I try to power of the virtual system (hard power off) restarting it (power on) I even did not get any vmware-bios-boot-message and no grub-loader-info was shown. Simply nothing, the screen is completely black. If I pause the virtual system, a correct snapshot of the (black/non visible) screen was made and a thumb was generated showing a correct screen of what has to be seen.
There is nothing special with my configuration, it was created for maximum compatibility and I am using it for more than three years with several vmware-workstations without any problems. The first time I run into trouble is using the image with build 14.1.3

[bonnie201110141]

Will you please upload ui log and vmware.log? Please enable debug mode for vmware.log from vm settings > Options > Advanced > Gether debugging information to full. Thanks very much!

[akoppel]

I have attached the log files requested.

[bonnie201110141]

Thanks! We will investigate ASAP.