<p>I had created a Virtual switch with the name "Minikube2" . Previously I had created  Virtual switch with the name "minikube" ,but deleted it later as there was config issue. </p>

<p>Did all the required configuration -"sharing on ethernet .." </p>

<p>Now when I try to run  </p>

<p>minikube start --kubernetes-version="v1.10.3" --vm-driver="hyperv" --hyperv-virtual-switch="minikube2"</p>

<p>it downloads the ISO , but fails to configure the switch -</p>

<p>it says vswitch "minikube2" not found</p>

Dinesh Tripathi
<p>Short answer is to delete <code>C:\Users\%USERNAME%\.minikube</code> and try again.
Below is my investigation:</p>

<p>First I have created Virtual Switch "minikube", started the cluster and it worked as expected. 
Then I stopped minikube, created new "Minikube2" switch and started minikube</p>

<pre><code>minikube start --kubernetes-version="v1.10.3" --vm-driver="hyperv" --hyperv-virtual-switch="minikube2" --v=9
</code></pre>

<p>Appeared issue:</p>

<blockquote>
  <p>Starting local Kubernetes v1.10.3 cluster... Starting VM... [executing
  ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Hyper-V\Get-VM minikube ).state [stdout =====>] : Off</p>
  
  <p>[stderr =====>] : [executing ==>] :
  C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile
  -NonInteractive Hyper-V\Start-VM minikube [stdout =====>] : [stderr =====>] : Hyper-V\Start-VM : 'minikube' failed to start. Synthetic Ethernet Port (Instance ID AF9D08DC-2625-4F24-93E5-E09BAD904899):
  Error 'Insufficient system resources exist to complete the requested
  service.'. Failed to allocate resources while connecting to a virtual
  network. The Ethernet switch may not exist. 'minikube' failed to
  start. (Virtual machine ID 863D6558-78EC-4648-B712-C1FDFC907588)
  'minikube' Synthetic Ethernet Port: Failed to finish reserving
  resources with Error 'Insufficient system resources exist to complete
  the requested service.' (0x800705AA). (Virtual machine ID
  863D6558-78EC-4648-B712-C1FDFC907588) 'minikube' failed to allocate
  resources while connecting to a virtual network: Insufficient system
  resources exist to complete the requested service. (0x800705AA)
  (Virtual Machine ID 863D6558-78EC-4648-B712-C1FDFC907588). The
  Ethernet switch may not exist. Could not find Ethernet switch
  'minikube'. At line:1 char:1
  + Hyper-V\Start-VM minikube
  + ~~~~~~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo          : NotSpecified: (:) [Start-VM], VirtualizationException
      + FullyQualifiedErrorId : Unspecified,Microsoft.HyperV.PowerShell.Commands.StartVM</p>
  
  <p>E1022 12:50:43.384867    6216 start.go:168] Error starting host: Error
  starting stopped host: exit status 1.</p>
  
  <p>Retrying. E1022 12:50:43.398832    6216 start.go:174] Error starting
  host:  Error starting stopped host: exit status 1 PS
  C:\Windows\system32></p>
</blockquote>

<p>Then I deleted <code>C:\Users\%USERNAME%\.minikube</code> , minikube vm inside Hyper-V and started again:</p>

<pre><code>C:\Windows\system32&gt; minikube start --kubernetes-version="v1.10.3" --vm-driver="hyperv" --hyperv-virtual-switch="minikube2" --v=9
</code></pre>

<p>Result:</p>

<blockquote>
  <p>Starting local Kubernetes v1.10.3 cluster... Starting VM...</p>
  
  <p>Downloading Minikube ISO</p>
  
  <p>170.78 MB / 170.78 MB [============================================] 100.00% 0s 
  Creating CA: C:\Users\Vitalii.minikube\certs\ca.pem </p>
  
  <p>Creating client certificate: C:\Users\Vitalii.minikube\certs\cert.pem</p>
  
  <p>----- [stderr =====>] : Using switch "Minikube2"</p>
  
  <p>----- Moving files into cluster... </p>
  
  <p>Downloading kubeadm v1.10.3 </p>
  
  <p>Downloading kubelet v1.10.3 Finished </p>
  
  <p>Downloading kubeadm v1.10.3 Finished</p>
  
  <p>Finished Downloading kubelet v1.10.3 </p>
  
  <p>Setting up certs... Connecting to</p>
  
  <p>cluster... Setting up kubeconfig... </p>
  
  <p>Starting cluster components...</p>
  
  <p>Kubectl is now configured to use the cluster.</p>
</blockquote>

<pre><code>PS C:\Windows\system32&gt; kubectl get pods --all-namespaces
NAMESPACE     NAME                                    READY     STATUS    RESTARTS   AGE
kube-system   coredns-c4cffd6dc-cjzsm                 1/1       Running   0          1m
kube-system   etcd-minikube                           1/1       Running   0          56s
kube-system   kube-addon-manager-minikube             1/1       Running   0          13s
kube-system   kube-apiserver-minikube                 1/1       Running   0          41s
kube-system   kube-controller-manager-minikube        1/1       Running   0          1m
kube-system   kube-dns-86f4d74b45-w62rv               2/3       Running   0          1m
kube-system   kube-proxy-psgss                        1/1       Running   0          1m
kube-system   kube-scheduler-minikube                 1/1       Running   0          21s
kube-system   kubernetes-dashboard-6f4cfc5d87-jz266   1/1       Running   0          1m
kube-system   storage-provisioner                     1/1       Running   0          1m
</code></pre>
