Add bcdedit trick for hypervisor troubleshooting

Signed-off-by: Simon Ferquel <simon.ferquel@docker.com>
This commit is contained in:
Simon Ferquel 2020-10-06 11:45:05 +02:00
parent 99788a00ab
commit ca2777ee78
1 changed files with 10 additions and 0 deletions

View File

@ -166,6 +166,8 @@ script](https://github.com/moby/moby/issues/24388).
2. Virtualization enabled in the BIOS
3. Hypervisor enabled at Windows startup
#### Hyper-V
Docker Desktop requires Hyper-V as well as the Hyper-V Module for Windows
@ -202,6 +204,14 @@ If you manually uninstall Hyper-V, WSL 2 or disable virtualization,
Docker Desktop cannot start. See [Unable to run Docker for Windows on
Windows 10 Enterprise](https://github.com/docker/for-win/issues/74).
#### Hypervisor enabled at Windows startup
If you have completed everything described above, and still have Docker Desktop faiing to start because of Hypervisor issues, this might be because the Hypervisor is installed but not launched at Windows Startup. Some tools (such as older versions of Virtual Box) and video game installers are known to do that.
To make the Windows Hypervisor run at launch:
- Open an administrative console prompt
- Run `bcdedit /set hypervisorlaunchtype auto`
- Restart Windows
### Networking and WiFi problems upon Docker Desktop for Windows install
Some users may experience networking issues during install and startup of