Minikube 0.26.0 fails to find hyper-v CLI tools

[ghost]

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Bug report.

I'm attempting to use minikube for the first time, and am not sure why it's failing.

The output:

PS C:\WINDOWS\system32> minikube start
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
E0416 18:13:49.089653    2828 start.go:159] Error starting host: Error creating host: Error executing step: Running precreate checks.
: Hyper-V PowerShell Module is not available.

 Retrying.
E0416 18:13:49.091657    2828 start.go:165] Error starting host:  Error creating host: Error executing step: Running precreate checks.
: Hyper-V PowerShell Module is not available
================================================================================
An error has occurred. Would you like to opt in to sending anonymized crash
information to minikube to help prevent future errors?
To opt out of these messages, run the command:
        minikube config set WantReportErrorPrompt false
================================================================================
Please enter your response [Y/n]:
E0416 18:13:50.527989    2828 util.go:161] EOF

I'm not particularly familiar with the docker machine codebase or golang, but from what I can tell, that particular precheck calls hypervAvailable(), which in turn runs (Get-Module -ListAvailable hyper-v).Name | Get-Unique and then checks to see if the string "Hyper-V" is present in stdout.

PS C:\WINDOWS\system32> (Get-Module -ListAvailable hyper-v).Name | Get-Unique
Hyper-V

It seems that it should be passing. I've also verified that the hyper-v powershell module is working through more practical tests.

Please provide the following details:

Environment:

Minikube version : 0.26.0

• OS : Windows 10, build 16299, Powershell version 5.1.16299.251
• VM Driver : hyperv
• ISO version: N/A
• Install tools:
• Others: installed via chocolatey, though I tried downloading the executable as well.

What happened: The install fails a precheck and does not attempt to proceed.

What you expected to happen: I would expect the install to continue, because hyper-v and the related powershell module are both available.

Anything else do we need to know: I am unsure of what other data may be useful, or how to determine if this is somehow an issue with my machine—it seems like a pretty straightforward precheck, and it should clearly be passing. The powershell module is not newly installed, but I've tried rebooting and relaunching powershell just for kicks, no change in behavior.

[ghost]

I just found #2634, apologies, closing.