Minikube突然改用VirtualBox驱动而非Hyper-V的原因咨询

我的Windows机器已启用Hyper-V且安装了VirtualBox，此前可正常执行命令：

minikube start --cpus 6 --memory 20g --disk-size=50g

该命令默认使用Hyper-V驱动，运行无报错。但现在执行相同命令时，出现如下错误：

minikube start --cpus 6 --memory 20g --disk-size=50g
- minikube v1.30.1 on Microsoft Windows 11 Enterprise 10.0.22621.1848 Build 22621.1848
- Using the virtualbox driver based on existing profile ! You cannot change the CPUs for an existing minikube cluster. Please first delete the cluster.
- Starting control plane node minikube in cluster minikube
- Creating virtualbox VM (CPUs=3, Memory=20480MB, Disk=51200MB) ... ! StartHost failed, but will try again: creating host: create: precreate: This computer is running Hyper-V. VirtualBox won't boot a 64bits VM when Hyper-V is activated. Either use Hyper-V as a driver, or disable the Hyper-V hypervisor. (To skip this check, use --virtualbox-no-vtx-check)
- Creating virtualbox VM (CPUs=3, Memory=20480MB, Disk=51200MB) ...
- Failed to start virtualbox VM. Running "minikube delete" may fix it: creating host: create: precreate: This computer is running Hyper-V. VirtualBox won't boot a 64bits VM when Hyper-V is activated. Either use Hyper-V as a driver, or disable the Hyper-V hypervisor. (To skip this check, use --virtualbox-no-vtx-check)
X Exiting due to PR_VBOX_HYPERV_64_BOOT: Failed to start host: creating host: create: precreate: This computer is running Hyper-V. VirtualBox won't boot a 64bits VM when Hyper-V is activated. Either use Hyper-V as a driver, or disable the Hyper-V hypervisor. (To skip this check, use --virtualbox-no-vtx-check)
- Suggestion: VirtualBox and Hyper-V are having a conflict. Use '--driver=hyperv' or disable Hyper-V using: 'bcdedit /set hypervisorlaunchtype off'

未对系统做任何修改，请问导致Minikube突然从Hyper-V切换为VirtualBox驱动的原因是什么？

• 本地配置文件被修改：Minikube会将集群的驱动信息存储在本地配置文件（路径通常为~/.minikube/profiles/minikube/config.json）中，即使你没有手动修改，误操作、后台脚本、或者其他工具的冲突都可能导致文件里的Driver字段被改为virtualbox，启动时Minikube会优先读取已有配置而非默认驱动。
• Hyper-V驱动检测临时异常：Minikube选择驱动时会按优先级检测，若Hyper-V服务出现短暂故障、权限变更，或者系统重启后Hyper-V未完全初始化，Minikube可能会 fallback 到已安装的VirtualBox驱动，导致驱动切换。
• 残留旧集群配置：如果之前曾用VirtualBox创建过Minikube集群，旧的配置文件未彻底清除。当你再次执行启动命令时，Minikube会读取到旧的VirtualBox驱动配置，而非使用默认的Hyper-V。
• Minikube版本更新后的逻辑变化：错误信息显示当前使用Minikube v1.30.1，若该版本是自动更新而来，新版本的驱动检测逻辑可能与旧版本不同，导致原本默认选择Hyper-V的行为发生改变，优先选用了VirtualBox。

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