Fixing Docker Desktop Error: BIOS Virtualization and Data Execution Protection

Why Docker is hitting a wallYou’ve just finished installing Docker Desktop and are ready to start building containers. Instead of a running engine, you’re greeted by a popup claiming your BIOS settings are incorrect. This happens even if you’ve already turned on Windows features like Hyper-V.

Docker effectively hits a dead end because it cannot access the physical CPU features required to run a virtualized Linux kernel. To fix this, we need to verify three layers: the hardware firmware (BIOS), the Windows system components, and the boot configuration.

Step 1: Check the 'Virtualization' status in WindowsBefore you reboot your computer to mess with BIOS settings, let’s see what Windows actually detects. You can check this in seconds without any extra software.

• Press Ctrl + Shift + Esc to open Task Manager.- Switch to the Performance tab.- Select CPU from the left-hand sidebar.- Look at the stats below the graph. Find the Virtualization label.If it says Enabled, your BIOS is fine, and the problem lies in your Windows configuration. If it says Disabled, you must enter your BIOS to flip the switch.

Step 2: Enable Virtualization in the BIOS/UEFIThis is the most frequent culprit. Most consumer motherboards ship with virtualization turned off by default. While every menu looks different, the logic remains the same across brands.

• Restart your PC.- As the screen lights up, tap your BIOS key. This is usually F2 or Del for ASUS and MSI, F10 for HP, or F12 for Dell.- Head to the Advanced or CPU Configuration menu.- Find the virtualization setting:For Intel CPUs: Look for Intel Virtualization Technology, VT-x, or Vanderpool.- For AMD CPUs: Look for SVM Mode or Secure Virtual Machine.- Ensure Execute Disable Bit (Intel) or No-Execute Page Protection (AMD) is set to Enabled. This satisfies the "Data Execution Protection" part of the error.- Press F10 to save and exit.Pro tip: If you are using a corporate laptop, these settings are often locked by IT. You will need an administrator to unlock them for you.

Step 3: Repair the Windows Feature StateSometimes Windows thinks a feature is on when it’s actually stuck in a half-configured state. We can force these features to refresh using PowerShell. Open PowerShell as an Administrator and run:

dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

Restart your computer after these commands finish. This ensures that the Virtual Machine Platform—the engine behind WSL2—is properly registered with the OS.

Step 4: Fix the Hypervisor Boot TypeIn some cases, the Windows Boot Configuration Data (BCD) is set to ignore the hypervisor at startup. This is common if you’ve recently used other VM software like VirtualBox 5.x or older versions of VMware. To force the hypervisor to start, run this in an Administrative Command Prompt:

bcdedit /set hypervisorlaunchtype auto

Crucial: Perform a full Shut Down rather than a Restart. Windows "Fast Startup" often saves the current kernel state to the disk, which can prevent the hypervisor from re-initializing correctly. A cold boot forces everything to reload from scratch.

Step 5: Check for Antivirus InterferenceSecurity suites like Avast, Bitdefender, or Kaspersky often use "Hardware-assisted virtualization" to power their own sandbox features. Because only one application can control these CPU extensions at a time, they can lock Docker out.

• Open your Antivirus dashboard.- Navigate to Settings > Troubleshooting (or Core Shields).- Look for a checkbox labeled Enable hardware-assisted virtualization and uncheck it.- Reboot your machine.## Verification: Is it working?Once you’re back at your desktop, perform a quick three-point check:
• Check Task Manager again; Virtualization should now read Enabled.- Open a terminal and run wsl --list --verbose. You should see your Linux distros listed.- Launch Docker Desktop. The whale icon in your system tray should stay solid green without throwing errors.Finally, run docker run hello-world. If you see the "Hello from Docker!" message, you've successfully cleared the hardware hurdle.