"Error detecting OS: OS type not recognized"
Additonal logging can be used with the command:
minikube start --vm-driver hyperv --v=7
This indicates the problem is that it can't connect to the server.
Additional research indicates that the Hyper-V guest is not contactable because it has the wrong Hyper-V switch configured.
HyperV driver
Hyper-v users may need to create a new external network switch as described here. This step may prevent a problem in which
minikube start hangs indefinitely, unable to ssh into the minikube virtual machine. In this add, add the --hyperv-virtual-switch=switch-name argument to the minikube start command.