The same module is different housing. What for?

Question

The problem with the minicub and docker machine in Windows occurs if you determine if the hyper-v module is available. For more information:

• https://github.com/kubernetes/minikube/issues/2634
• https://github.com/docker/machine/issues/4424

but it is not essential.

What is it that on two Windows 10 machines, both modern and WMF 5.1 (PSVersion 5.1.16299.251) At startup, Get-Command hyper-v\get-vmwe get different results.

Let me demonstrate:

The difference is that the module name is different. This is "hyper-v" versus "hyper-v". I compared byte files inside C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Hyper-V. They are the same, and the path name has the same corpus.

So why is the difference?

Answer 1

, , :

Import-Module Hyper-v
(Get-Command hyper-v\get-vm).Module.Name

Hyper-v.

:

@(Get-Module -ListAvailable hyper-v).Name | Get-Unique

, PowerShell Build Windows.

: :

. , Get-Module -ListAvailable. , Windows ? , Windows 10, . ( ).