Windows10下Minikube启动报错config.json未找到，求K8S技术帮助

Hey there, let's sort out this issue without jumping straight to reinstalling Minikube—you don't need that yet! Here's what's going on and how to fix it:

Why This Happens #

When you manually deleted the Hyper-V VM without running minikube stop first, Minikube's local configuration (stored in C:\Users\<YourUsername>\.minikube on Windows) didn't get updated. Minikube still expects the old VM's files and config to exist, so when you try to start a new instance, it can't locate the missing config.json tied to the deleted VM.

Step-by-Step Fix #

• First, clean up Minikube's stale state: Run this command in your terminal (as admin if needed):

  minikube delete
  

  This command will wipe out all residual Minikube configurations, leftover VM files, and state data—even though you already deleted the Hyper-V VM manually, this ensures Minikube's local records are fully reset.

• Restart Minikube with your original command:

  minikube start --vm-driver hyperv --hyperv-virtual-switch "Primary Virtual Switch"
  

  Now Minikube will create a fresh VM and generate all the necessary config files from scratch.

• Double-check your Hyper-V switch (if issues persist): Make sure your "Primary Virtual Switch" is set up as an External switch, bound to a working network adapter, and isn't disabled in Hyper-V Manager. A misconfigured switch can cause unexpected startup errors too.

No need to reinstall Minikube—this state cleanup is almost always enough to resolve this kind of config mismatch.

内容的提问来源于stack exchange，提问作者Sri