Darrek

The reason I'm not building a binary is to avoid any unexpected distribution license issues. I may take another stab at a PR for VSock into upstream with just the minimal changes without the build environment changes. The upstream repo did try to take my changes, but the changes to support a Docker build environment was a massive change and it broke too many things for many people. At least I've found I can keep pulling DLLs and using them with the old EXE I built and everything has been working...

Simon, The VSock stuff has been merged to master but is not released yet. Look in HOW_TO_BUILD.txt to see how to build your own...

That means something else is already using port 6000 which is the default port for display 0. netstat -abn will help you identify the program already on that port.

Try running netstat with VcXSrv not running. Maybe something else is already listening on port 6000...

And if you run these commands from Windows wsl ip addr add 192.168.250.2/24 broadcast 192.168.250.255 dev eth0:1 netsh interface ip add address "vEthernet (WSL)" 192.168.250.1 255.255.255.0 you are guaranteed to always have the same IP address available between host and guest.

Select a display setting other than "Multiple Windows" and then use Open a session via XDMCP. Will likely need to modify xdm settings on your Ubuntu to allow the external connection.

IDK. Looks like it is listening on 6000 as it should and made connections to itself.

Release files including the installer have not been created yet. You will have to check out and build yourself from master for the time being.