Introduction

This Minikube error means Minikube was told to use the Hyper-V driver, but Windows either does not have Hyper-V available or Minikube cannot access it correctly. The fix is to verify that Hyper-V is supported and enabled, then either configure it properly or switch to a different driver. In other words, the problem is usually driver selection, not Kubernetes itself.

Confirm Whether Hyper-V Is Actually Available

Hyper-V is not available on every Windows edition. It is typically supported on 64-bit Windows Pro, Enterprise, or Education systems with hardware virtualization enabled. If the machine does not satisfy that baseline, Minikube cannot start with the Hyper-V driver no matter how many times you retry.

A quick PowerShell check is useful.

systeminfo

Look at the Hyper-V requirements near the end of the output. You should also confirm that virtualization is enabled in firmware.

If the machine is on a Windows edition without Hyper-V support, the correct fix is not a Minikube flag. The correct fix is to use another driver such as Docker.

Enable Hyper-V If the System Supports It

If the machine supports Hyper-V but it is disabled, turn it on from an elevated PowerShell session.

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

Then reboot the machine. Without the reboot, Minikube may still fail because the virtualization components are not fully active yet.

Once Hyper-V is enabled, a basic startup looks like this.

minikube start --driver=hyperv

If Hyper-V is the driver you want permanently, you can store it in Minikube’s config.

minikube config set driver hyperv

Configure the Virtual Switch When Needed

On Hyper-V systems, Minikube may also need a usable virtual switch. If no appropriate switch is available, startup can fail even though Hyper-V itself exists.

A direct fix is to provide the switch name explicitly.

minikube start --driver=hyperv --hyperv-virtual-switch="Primary Switch"

The exact switch name depends on your machine. The important point is that Hyper-V availability and network-switch configuration are separate concerns.

Switching Drivers Is Often the Practical Fix

If Hyper-V is not supported, conflicts with your environment, or you simply do not want to manage it, choose another Minikube driver instead of forcing Hyper-V to work.

minikube start --driver=docker

That is often the easiest option on machines that already use Docker Desktop. The broader lesson is that Minikube needs a working virtualization backend, but it does not specifically require Hyper-V.

Permissions and Environment Still Matter

Even when Hyper-V is installed, Minikube can still fail if the shell lacks the required permissions or if the current configuration points to a stale driver setting. If you previously configured Hyper-V as the default and later removed or disabled it, Minikube may keep trying to use it.

In that case, inspect and update the active configuration rather than only rerunning start.

minikube config view
minikube config set driver docker

That kind of stale configuration is a common reason the error seems to persist after the machine environment changed.

Common Pitfalls

• Assuming every Windows edition includes Hyper-V support.
• Enabling Hyper-V but forgetting to reboot before retrying Minikube.
• Confusing missing Hyper-V with missing virtual-switch configuration.
• Persisting the Hyper-V driver in Minikube config and then forgetting it was set there.
• Forcing Hyper-V when Docker or another supported driver is the better fit for the machine.

Summary

• 'PROVIDER_HYPERV_NOT_FOUND means Minikube cannot use the Hyper-V driver on the current system.'
• First verify Windows support, hardware virtualization, and whether Hyper-V is enabled.
• If Hyper-V is valid, enable it, reboot, and configure a virtual switch if needed.
• If Hyper-V is not available or not desirable, switch Minikube to another driver such as Docker.
• Treat this as a virtualization-driver problem, not a Kubernetes problem.