A cool start would be a Chocolatey package so Windows users can easily install it.
As I've made the choco package for the other driver I adjusted the package code and it already works:
PS C:\> choco install -y vmwareworkstation docker docker-machine
PS C:\> choco install docker-machine-vmware -pre -source .
Chocolatey v0.10.11
Installing the following packages:
docker-machine-vmware
By installing you accept licenses for the packages.
docker-machine-vmware v0.1.0
docker-machine-vmware package files install completed. Performing other installation steps.
The package docker-machine-vmware wants to run 'chocolateyinstall.ps1'.
Note: If you don't run this script, the installation will fail.
Note: To confirm automatically next time, use '-y' or consider:
choco feature enable -n allowGlobalConfirmation
Do you want to run the script?([Y]es/[N]o/[P]rint): y
C:\ProgramData\chocolatey\lib\docker-machine-vmware\bin
Downloading docker-machine-vmware 64 bit
from 'https://github.com/machine-drivers/docker-machine-driver-vmware/releases/download/v0.1.0/docker-machine-driver-vmware_windows_amd64.exe'
Progress: 100% - Completed download of C:\ProgramData\chocolatey\lib\docker-machine-vmware\bin\docker-machine-driver-vmware.exe (6.87 MB).
Download of docker-machine-driver-vmware.exe (6.87 MB) completed.
Hashes match.
C:\ProgramData\chocolatey\lib\docker-machine-vmware\bin\docker-machine-driver-vmware.exe
ShimGen has successfully created a shim for docker-machine-driver-vmware.exe
The install of docker-machine-vmware was successful.
Software install location not explicitly set, could be in package or
default install location if installer.
Chocolatey installed 1/1 packages.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
Did you know the proceeds of Pro (and some proceeds from other
licensed editions) go into bettering the community infrastructure?
Your support ensures an active community, keeps Chocolatey tip top,
plus it nets you some awesome features!
https://chocolatey.org/compare
PS C:\vagrant\choco-docker-machine-vmware> docker-machine create -d vmware default
Creating CA: C:\Users\vagrant\.docker\machine\certs\ca.pem
Creating client certificate: C:\Users\vagrant\.docker\machine\certs\cert.pem
Running pre-create checks...
(default) Image cache directory does not exist, creating it at C:\Users\vagrant\.docker\machine\cache...
(default) No default Boot2Docker ISO found locally, downloading the latest release...
(default) Latest release for github.com/boot2docker/boot2docker is v18.06.0-ce
(default) Downloading C:\Users\vagrant\.docker\machine\cache\boot2docker.iso from https://github.com/boot2docker/boot2docker/releases/download/v18.06.0-ce/boot2docker.iso...
(default) 0%....10%....20%....30%....40%....50%....60%....70%....80%....90%....100%
Creating machine...
(default) Copying C:\Users\vagrant\.docker\machine\cache\boot2docker.iso to C:\Users\vagrant\.docker\machine\machines\default\boot2docker.iso...
(default) Creating SSH key...
(default) Creating VM...
(default) Starting default...
(default) Waiting for VM to come online...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with boot2docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Docker is up and running!
To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: C:\ProgramData\chocolatey\lib\docker-machine\bin\docker-machine.exe env default
PS C:\> docker-machine env | iex
PS C:\> docker version
Client:
Version: 17.10.0-ce
API version: 1.33
Go version: go1.8.3
Git commit: f4ffd25
Built: Tue Oct 17 19:00:02 2017
OS/Arch: windows/amd64
Server:
Version: 18.06.0-ce
API version: 1.38 (minimum version 1.12)
Go version: go1.10.3
Git commit: 0ffa825
Built: Wed Jul 18 19:13:39 2018
OS/Arch: linux/amd64
Experimental: false
Do you want to take over the choco package sources into this repo so it can be added to a release step to build and push the choco package eg. from an AppVeyor CI build.