Docker ошибка hyper v

I’ve been encountering this issue, and as far as I can tell, it has something to do with how Windows starts (or doesn’t start) either the Hyper-V service, its hypervisor, or the Windows Hypervisor Platform. I can’t precisely say when this has started happening, but my best guess is 2 to 3 weeks ago, while I was still using Docker 3.6. I use Docker, VMWare, and WSL. The behavior of the virtualization services is erratic, to say the least, and not necessarily Docker’s fault, but I’m writing this to try and help investigating.

I’ve witnessed the following scenarios, all starting with all applications off.

1. Docker says it can’t enable the Hyper-V service. I start a WSL window, then VMWare, successfuly. Then I try starting Docker, now it works (simultaneously with WSL+VMWare).
2. Docker starts fine out of the blue. VMWare suddenly doesn’t start virtual machines. WSL works.
3. Today, VMWare started fine. Docker didn’t start the first time with the usual error message. After a few minutes, I tried again, and it worked.

My best guess is that a Windows update changed something about how one of the necessary virtualization services actually fires up (or doesn’t), and it’s borking Docker and VMWare.

Настольное приложение Docker довольно популярно среди разработчиков, разрабатывающих новое программное обеспечение для различных систем Windows. Приложение позволяет использовать несколько виртуальных систем для тестирования новых сборок, исправлений только из системы разработчика. Но что, если Docker неожиданно выдает сообщение об ошибке «Docker не может включить Hyper-V»? Не волнуйся. Просто следуйте этим простым исправлениям, чтобы решить проблему очень быстро.

Обходные пути –

а. Запустить снова ваш компьютер и снова попробуйте получить доступ к виртуальным системам в вашей системе.

б. Отключите любую запущенную антивирусную программу и проверьте еще раз.

Исправление 1. Включите Hyper-V в вашей системе.

Hyper-V — это дополнительная функция, которую необходимо включить вручную для работы с ней.

1. Сначала щелкните правой кнопкой мыши Клавиша Windows и после этого нажмите «Запустить“.

2. Затем введите эту команду и нажмите Входить.

дополнительные возможности

3. Как только появится компонент Windows, проверять «Hyper-V»Из списка дополнительных функций.

4. Как только вы это сделаете, нажмите «ОК“.

Теперь Windows включит HyperVisor на вашем компьютере.

5. Затем нажмите «Перезагрузить сейчас“.

После перезагрузки компьютера Hyper-V будет включен. Это займет некоторое время. После перезагрузки компьютера откройте Docker и попробуйте запустить виртуальную машину.

Альтернативный метод —

Если предыдущий метод не работает, попробуйте этот.

1. Сначала щелкните правой кнопкой мыши значок Windows и выберите «Windows PowerShell (администратор)“.

2. Как только появится терминал, введите или вставьте этот код отсюда и нажмите Входить.

DISM / Онлайн /Включить-функцию / Все / FeatureName:Microsoft-Hyper-V

Windows включит эту функцию.

Закройте окно PowerShell и перезагрузите компьютер один раз.

Исправление 2 — Включить виртуализацию в BIOS

Одним из ключевых требований Hyper-V является активация виртуализации в BIOS.

1. Сначала выключите компьютер.

2. Запустите машину.

3. Когда система загружается, вам нужно нажать кнопку «Удалить“* клавишу на клавиатуре, чтобы открыть программу настройки BIOS на вашем компьютере.

* ПРИМЕЧАНИЕ— Конкретный ключ может отличаться от производителя к производителю. Это различные ключи-

Esc, F1, F2, F10, F11, F12 или Удалить

Нажатие выделенной клавиши через некоторое время вызовет экран BIOS.

3. Однажды BIOS откроется настройка, перейдите к «Передовой”Таб.

4. Затем выберите «Виртуализация»Из списка и убедитесь, что это«Включено“.

(На некоторых компьютерах вы можете заметить «Режим SVM» вместо настроек «Виртуализация». Включите его, чтобы получить тот же эффект)

5. Снова нажмите связанную с ним клавишу, чтобы сохранить настройки.

[Это «F10Клавиша для этого компьютера.]

6. После этого выберите «да», Чтобы наконец сохранить и выйти из настроек BIOS на вашем компьютере.

После того, как вы сохранили настройки, ваш компьютер сделает это автоматически. Теперь откройте приложение Docker на своем компьютере и попробуйте открыть новую виртуальную машину.

Исправление 3 — Удалите и переустановите Hyper-V.

Если сами файлы Hyper-V случайно повреждены, Docker не откроется.

1. нажмите Клавиша Windows + X ключи вместе.

2. Затем нажмите «Windows PowerShell (администратор) », Чтобы получить к нему доступ.

3. Копировать вставить эти коды один за другим и нажмите Входить после этого выполнять эти коды последовательно.

Отключить-WindowsOptionalFeature -FeatureName microsoft-hyper-v -online restart-computer. Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All restart-computer. Enable-WindowsOptionalFeature -Online -FeatureName Контейнеры -Все

После выполнения кодов откройте Docker еще раз и проверьте, решает ли это проблему.

ПРИМЕЧАНИЕ–

Если проблема все еще существует, попробуйте следующие шаги —

а. Откройте терминал PowerShell с правами администратора.

2. После этого выполните этот код и проверьте, помогает ли это.

MOFCOMP% SYSTEMROOT%  System32  WindowsVirtualization. V2.mof

Проверьте, решает ли это проблему.

Ваша проблема должна быть решена.

15th March 2023

4 min read

sudo systemctl status docker

sudo systemctl start docker

sudo journalctl -u docker.service

by Tashreef Shareef

Tashreef Shareef is a software developer turned tech writer. He discovered his interest in technology after reading a tech magazine accidentally. Now he writes about everything tech from… read more

Updated on August 26, 2020

Docker Desktop is a software application for Windows machines that allows the developers to build production-ready container applications easily. However, some users have reported Hyper-V and container features are not enabled error while installing Docker Desktop in the computer. You can find similar issues in the Reddit community as well.

Does anyone have any ideas how to enable Hyper-v and containers on Windows 10 Pro 64bit with compatible hardware (according to msinfo32) and all requirements met ie BIOS virtualisation enabled, >4GB RAM and so on. Despite all this none of the commands in powershell or cmd succeed.They complain that one or more parent features must be enabled. There is no error when enabling via Windows features but after the restart Hyper-v regresses to disabled. 

If you are troubled by this error, here are a couple of troubleshooting tips to help you fix Hyper-v and containers features are not enabled error in Windows computer.

How to fix Hyper-v and containers features are not enabled

1. Enable Virtualization in BIOS for Hyper-V

1. If you haven’t already, you need to enable Hyper-V in BIOS before Docker can install and enable containers features.
2. Shutdown your computer if it is on.
3. Restart the computer and press F2 to open the BIOS setup. The function key can be different depending on the motherboard maker.
4. Use the right-arrow key to navigate to the Advanced tab.
5. Choose the Virtualization Technology and hit enter.
6. Select Enable and hit Enter again.
7. Save the changes (F10) and exit.
8. Try to run Docker and check if the Hyper-v and containers features are not enabled error is resolved.

---

How to use Windows Sandbox and VirtualBox VMs simultaneously

---

2. Enable Hyper-V in Windows 10

1. If the issue persists, you may have to manually enable Hyper-V virtualization feature in Windows 10.
2. Press Windows Key + R to open Run.
3. Type control and click OK.
4. In the Control Panel, go to Programs > Programs and Features.
5. From the left pane, click on Turn Windows Features on or off.
   
   
6. Select Hyper-V in the Windows Features window.
7. Click OK to apply the changes.
8. Once the installation is completed, you are prompted to restart the computer.

Enable Hyper-V with CMD and DISM

1. Alternatively, you can also use DISM and PowerShell command to enable Hyper-V.
2. Right-click on Start and select PowerShell (admin).
3. In the PowerShell window, type the following command and hit enter.
   DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V
4. Close the PowerShell window and launch Docker. Check for any improvements.

---

3. Try to Remove and Reinstall Hyper-V

1. If you have already installed Hyper-V, it is possible that the installation may be corrupt resulting in Hyper-v and containers features are not enabled error. Try to remove and install Hyper-V manually to see if that helps.
2. Right-click on Start and select Windows PowerShell (Admin).
   
   
3. In the PowerShell window type the following command and hit enter one by one.
   Disable-WindowsOptionalFeature -FeatureName microsoft-hyper-v -online restart-computer
   Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All restart-computer
   Enable-WindowsOptionalFeature -Online -FeatureName Containers -All
4. Check for any improvements.
5. If the issue persists, try to run the following command in the PowerShell and check if it helps.
   MOFCOMP %SYSTEMROOT%System32WindowsVirtualization.V2.mof

RELATED STORIES YOU MAY LIKE:

• The best virtual machines for Windows 10 to use today
• How to run 16-bit apps in Windows 10 64-bit [STEP-BY-STEP GUIDE]
• Windows Virtual Desktop might arrive by the end of the year

Let us take a closer look at the error docker error hardware assisted virtualization and the effective troubleshooting steps to deal with the error. With the support of our Docker hosting support services at Bobcares, we can give you a detailed note on the error with Troubleshooting tips.

Enable Hardware Assisted Virtualization

Error: Docker says: There was an Error: The BIOS must have data execution protection and hardware aided virtualization enabled.


Intel and AMD have enhanced their CPU lineups with virtualization enhancements. The virtualization features will label themselves differently depending on the CPU: Intel refers to it as VT-x (Virtualization Technology), while AMD refers to it as SVM (Secure Virtual Machine).

To use the CPU’s virtualization extensions, we must enable them in the BIOS or UEFI of the motherboard, as well as in the operating system settings.

Enable AMD Secure Virtual Machine (SVM)

When we have an AMD CPU with Zen 2 architecture (for example, AMD Ryzen 7 3700X), we can enable SVM on an AMD X570 chipset motherboard (for example, MSI MEG X570 Unify) by doing the following:

1. Switch off the computer.
2. When the startup screen shows, turn on the computer and click the “Del” (Delete) key.
3. We can use the “F7” key for accessing the “Advanced Mode” in “MSI Click Bios 5”.
4. Choose the “OC” (Overclocking) options.
5. Choose “CPU Features”
6. Change “SVM Mode” to “Enabled.”
7. Exit the BIOS and save the configuration.

Enable Microsoft Hyper-V

When using Microsoft Windows, we must enable Hyper-V after enabling hardware-assisted virtualization (i.e. Microsoft Windows 10 Professional).

The Microsoft Hyper-V feature can be enabled in the “Control Panel” by going to the “Turn Windows features on or off” section and selecting “Turn Windows features on or off”.

Let us take a closer look at the error docker error hardware-assisted virtualization and the effective troubleshooting steps to del with the error.

Docker says: An error occurred: Hardware assisted virtualization and data execution protection must be enabled in the BIOS.

Enable Hardware Assisted Virtualization

Intel and AMD have enhanced their CPU lineups with virtualization enhancements. The virtualization features are labeled differently depending on the CPU used: Intel refers to it as VT-x (Virtualization Technology), while AMD refers to it as SVM (Secure Virtual Machine).

To use the CPU’s virtualization extensions, we must enable them in the BIOS or UEFI of the motherboard, as well as in the operating system settings.

Enable AMD Secure Virtual Machine (SVM)

When we have an AMD CPU with Zen 2 architecture (for example, AMD Ryzen 7 3700X), we can enable SVM on an AMD X570 chipset motherboard (for example, MSI MEG X570 Unify) by doing the following:

1. Switch off the computer.
2. When the startup screen shows, turn on the computer and click the “Del” (Delete) key.
3. Press “F7” to access “Advanced Mode” in “MSI Click Bios 5”.
4. Choose the “OC” (Overclocking) options.
5. Choose “CPU Features”
6. Change “SVM Mode” to “Enabled.”
7. Exit the BIOS and save the configuration.

Alternative Solutions for Docker Error Hardware Assisted Virtualization

A SOLUTION (If Hyper-V is totally disabled or not installed)

• Start PowerShell as an administrator.
• Dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All will enable Hyper-V.

SOLUTION B (If Hyper-V is already activated but not working)

Enable Hypervisor by entering the following code:

bcdedit /set hypervisorlaunchtype auto

Reboot the system and try again.

SOLUTION C for docker error hardware assisted virtualization

If the situation persists, the Hyper-V on the machine is most likely corrupt, therefore follow the steps given below:

1. Uncheck all Hyper-V-related components in Control Panel -> [Programs] -> [Windows Features]. Reboot the system.
2. Re-enable Hyper-V. Restart.

NOTE 1:

Hardware virtualization is necessary as a precondition for Hyper-V. Check if the PC supports it; if it does and it still does not work, the BIOS may be incorrectly configured and this feature is disabled.

We can check, activate it, and try again in this situation. The virtualization features can report under different labels depending on the platform utilized (for example, if we don’t find any choice that directly utilizes the virtualization label, on AMD we must check the SVM feature status, on Intel the VT-x feature state).

NOTE 2:

We can only install certain versions of Hyper-V, for example, Windows 10 Enterprise; Windows 10 Professional; Windows 10 Education.

Hyper-V cannot deploy itself on less expensive or mobile Windows editions, such as Windows 10 Home; Windows 10 Mobile; or Windows 10 Mobile Enterprise.

Solution D

Please follow the procedures given below:

1. Start PowerShell as administrator or CMD as administrator.
2. In PowerShell, type bcdedit /set hypervisorlaunchtype auto.
3. Finally, reboot the system and try again.

Solution E

In this scenario of docker error hardware assisted virtualization, we needed to enable virtualization in the BIOS. So in this case we have to Firstly, Restart the PC. After that, While on the restart page, press any of the following keys to access the bios settings in Windows: ESC, f1, f2, f3, f4, f8, or delete.

Follow the procedures below for Intel-based systems:

• press f7 (advanced mode)
• go to advanced
• CPA configuration
• enable virtualization

And it will work after all of the previous configuration processes.

Solution F:

We can also attempt the following steps for the docker error hardware assisted virtualization:

1. Firstly, In PowerShell, type bcdedit /set hypervisorlaunchtype auto.
2. After that, restart the computer.
3. Try the docker —version in the command line now.

Or In PowerShell (admin enabled), try this:

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

This will install HyperVisor without any management tools, after which we may run Docker.

[Need assistance with similar queries? We are here to help]

Conclusion

To conclude we have learned all of the possible and effective solutions to deal with the error, docker error hardware assisted virtualization. With the assistance of Docker hosting Support Services, we have gone through all of the possible solutions and steps to deal with the error.