Skip to content
Pinter Computing

Knowledge Base for IT Professionals, Teachers, and Astronauts

Pinter Computing

Knowledge Base for IT Professionals, Teachers, and Astronauts

  • Home
  • Programming
  • DevOps
  • Project Management
  • Software and Hardware
  • Miscellaneous
  • Egyebek
  • About
  • Experience
  • Education
  • Contact
  • Home
  • Programming
  • DevOps
  • Project Management
  • Software and Hardware
  • Miscellaneous
  • Egyebek
  • About
  • Experience
  • Education
  • Contact
Close

Search

Home/Knowledge Base/Docker for Windows cannot start: “Hardware assisted virtualization and data execution protection must be enabled in the BIOS”
Knowledge Base

Docker for Windows cannot start: “Hardware assisted virtualization and data execution protection must be enabled in the BIOS”

By Laszlo Pinter
January 28, 2019 1 Min Read
4

To start Docker on Windows, Hyper-V and the Hypervisor has to be enabled on Windows.

  1. Start a PowerShell window as administrator
  2. Enable Hyper-V
    dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All
  3. Enable the Hypervisor
    bcdedit /set hypervisorlaunchtype auto
  4. Restart the computer

Tags:

Docker
Author

Laszlo Pinter

Follow Me
Other Articles
Previous

List the Active Directory groups the user is a member of

Next

x509: certificate signed by unknown authority

4 Comments
  1. REZURAsantoso says:
    March 27, 2020 at 9:28 am

    Docker for Windows cannot start: “Hardware assisted virtualization and data execution protection must be enabled in the BIOS”

    Reply
  2. Mohammad Wasim Khan says:
    August 20, 2020 at 3:41 am

    PS C:\WINDOWS\system32> dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All

    Deployment Image Servicing and Management tool
    Version: 10.0.19041.329

    Image Version: 10.0.19041.450

    Error: 0x800f080c

    Feature name Microsoft-Hyper-V is unknown.
    A Windows feature name was not recognized.
    Use the /Get-Features option to find the name of the feature in the image and try the command again.

    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

    Reply
    1. Ashley says:
      October 1, 2020 at 10:57 am

      Hyper V feature isn’t in Windows Home but in Windows Pro version, so if you have Home installed HyperV will not be recognized as a feature.

      Reply
  3. Sam says:
    October 7, 2020 at 9:03 am

    Is anyone can help me about this issue. I try about this about 2 months now is working

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Search

Last Changes

  • DevOps Engineering part 1. (Mac) - Make your Macintosh easier to use June 25, 2026
  • Japan travel tips June 22, 2026
  • How to stop the rain and snow in Cities: Skylines II June 20, 2026
  • Cities: Skylines II Developer Mode June 20, 2026
  • 'CSII_MANAGEDPATH' has incorrect path(s) when building Cities: Skylines II mod June 20, 2026

Tags

.NET .NETcore 3Dprinting ASP.NET Core AutodeskInventor AWS C# Chef cloud DevOps Docker EntityFramework Games Git Go iOS iPad iPhone iPod Java Kubernetes Linux MacOSX MSSQL MVC Node.js Packer PowerShell Python RDS RightScale Ruby security Splunk TeamCity Terraform TestKitchen Tomcat Ubuntu Vagrant VirtualBox VisualStudio Windows WordPress Xcode

Recent Comments

  • Zengei László on MyHeritage családfa exportálása és küldése emailben
  • Raúl Castillo on DynDns update error
  • MICHAEL on Windows Media Player 12 cannot find the album information
  • Nargis on Configure Epson ET-3850 scanning on Windows 11
  • Venczelné Zemen Erika on Delta S2302 termosztát programozása

–

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org
Copyright 2026 — Pinter Computing. All rights reserved.