The command sets the current hypervisor launch type to automatic.
The command sets the current hypervisor launch type to automatic.
Hello, I encountered problems starting Docker on Windows due to Hyper-V not being enabled. Initially, I tried running bcdedit /set {current} hypervisorlaunchtype auto, but Docker still didn’t function. Later, I discovered Hyper-V wasn’t activated, so I executed Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper -V -All, which resolved the issue. Regarding your question, bcdedit /set {current} hypervisorlaunchtype auto likely configured Hyper-V to launch as a service for the current user at boot.
It hasn't done anything because that's the standard setting. With hyper-v active, it runs automatically at startup unless turned off via bcdedit, which lets you disable it without removing it completely.