Hyper-V PowerShell Module is not available

[SatyaSaladi]

What Happened?

Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows PS C:\Windows\system32> $oldPath = [Environment]::GetEnvironmentVariable('Path', [EnvironmentVariableTarget]::Machine) PS C:\Windows\system32> if ($oldPath.Split(';') -inotcontains 'C:\minikube'){ >> [Environment]::SetEnvironmentVariable('Path', $('{0};C:\minikube' -f $oldPath), [EnvironmentVariableTarget]::Machine)

}
PS C:\Windows\system32> minikube start
W1130 15:30:33.353717 16184 main.go:291] Unable to resolve the current Docker CLI context "default": context "default": context not found: open C:\Users\satya.docker\contexts\meta\37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f\meta.json: The system cannot find the path specified.

• minikube v1.32.0 on Microsoft Windows 11 Home Single Language 10.0.22621.2715 Build 22621.2715
• Using the hyperv driver based on existing profile
• Starting control plane node minikube in cluster minikube
• Creating hyperv VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
  ! StartHost failed, but will try again: creating host: create: precreate: Hyper-V PowerShell Module is not available
• Creating hyperv VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
• Failed to start hyperv VM. Running "minikube delete" may fix it: creating host: create: precreate: Hyper-V PowerShell Module is not available

X Exiting due to PR_HYPERV_MODULE_NOT_INSTALLED: Failed to start host: creating host: create: precreate: Hyper-V PowerShell Module is not available

• Suggestion: Run: 'Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Tools-All -All'
• Documentation: https://www.altaro.com/hyper-v/install-hyper-v-powershell-module/
• Related issue: error provisioning host: Hyper-V PowerShell Module is not available #9040

PS C:\Windows\system32> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Tools-All -All
Enable-WindowsOptionalFeature : Feature name Microsoft-Hyper-V-Tools-All is unknown.
At line:1 char:1

• Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V- ...

•   + CategoryInfo          : NotSpecified: (:) [Enable-WindowsOptionalFeature], COMException
    + FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand
  
  

Attach the log file

Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows PS C:\Windows\system32> $oldPath = [Environment]::GetEnvironmentVariable('Path', [EnvironmentVariableTarget]::Machine) PS C:\Windows\system32> if ($oldPath.Split(';') -inotcontains 'C:\minikube'){ >> [Environment]::SetEnvironmentVariable('Path', $('{0};C:\minikube' -f $oldPath), [EnvironmentVariableTarget]::Machine)

}
PS C:\Windows\system32> minikube start
W1130 15:30:33.353717 16184 main.go:291] Unable to resolve the current Docker CLI context "default": context "default": context not found: open C:\Users\satya.docker\contexts\meta\37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f\meta.json: The system cannot find the path specified.

• minikube v1.32.0 on Microsoft Windows 11 Home Single Language 10.0.22621.2715 Build 22621.2715
• Using the hyperv driver based on existing profile
• Starting control plane node minikube in cluster minikube
• Creating hyperv VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
  ! StartHost failed, but will try again: creating host: create: precreate: Hyper-V PowerShell Module is not available
• Creating hyperv VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
• Failed to start hyperv VM. Running "minikube delete" may fix it: creating host: create: precreate: Hyper-V PowerShell Module is not available

X Exiting due to PR_HYPERV_MODULE_NOT_INSTALLED: Failed to start host: creating host: create: precreate: Hyper-V PowerShell Module is not available

• Suggestion: Run: 'Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Tools-All -All'
• Documentation: https://www.altaro.com/hyper-v/install-hyper-v-powershell-module/
• Related issue: error provisioning host: Hyper-V PowerShell Module is not available #9040

PS C:\Windows\system32> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Tools-All -All
Enable-WindowsOptionalFeature : Feature name Microsoft-Hyper-V-Tools-All is unknown.
At line:1 char:1

• Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V- ...

•   + CategoryInfo          : NotSpecified: (:) [Enable-WindowsOptionalFeature], COMException
    + FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand
  

Operating System

Windows

Driver

Hyper-V

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.