title: Same module different casing. Why?
body: <p>There is a bit of a problem going on with minikube and docker-machine on windows, determining if hyper-v module is available. For more information:</p>
  
  <ul>
  <li><a href="https://github.com/kubernetes/minikube/issues/2634" rel="nofollow noreferrer">https://github.com/kubernetes/minikube/issues/2634</a></li>
  <li><a href="https://github.com/docker/machine/issues/4424" rel="nofollow noreferrer">https://github.com/docker/machine/issues/4424</a></li>
  </ul>
  
  <p>but this is not essential.</p>
  
  <p>What is, that on two Windows 10 machines, both up-to-date, both with WMF 5.1 (PSVersion 5.1.16299.251) When running <code>Get-Command hyper-v\get-vm</code> we get different results.</p>
  
  <p>Let me demonstrate:</p>
  
  <p><a href="https://i.stack.imgur.com/yZ5TP.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/yZ5TP.png" alt="enter image description here"></a></p>
  
  <p><a href="https://i.stack.imgur.com/d8nAv.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/d8nAv.png" alt="enter image description here"></a></p>
  
  <p>The difference is that the module name differs. It's "hyper-v" vs "Hyper-V".
  I compared byte-for-byte files inside <code>C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Hyper-V</code>. They are the same, and the path name have the same casing.</p>
  
  <p>So why is the difference?</p>