How to enable virtualization in BIOS, on one PC or a whole fleet
How to enable virtualization in BIOS: what VT-x, AMD-V and VT-d do, how to check they are on, where Dell, HP, Lenovo, ASUS, MSI and Gigabyte hide the setting, how VBS builds on it, the WSL, Docker and Hyper-V errors that point back to it, and how to switch it on across a fleet.
Updated: November 2026
Hyper-V won't install, WSL2 throws an error, or Docker Desktop refuses to start, and the fix is one switch buried three menus deep in the firmware. Every vendor names that switch differently and hides it somewhere new. Here's how to check whether it's already on, where Dell, HP, Lenovo, ASUS, MSI and Gigabyte keep it, and how to flip it on a hundred machines without visiting any of them.
What you're switching on
Modern Intel and AMD processors can run virtual machines at close to full speed, but only if the firmware lets them. That permission is one setting, and Intel and AMD call it different things. On Intel it's VT-x, which firmware menus label "Intel Virtualization Technology" or "Intel (VMX) Virtualization Technology". On AMD it's AMD-V, which ASUS, MSI and Gigabyte boards list as "SVM Mode".
On Dell, HP, Lenovo and MSI machines, a second setting sits in the same menu. Intel VT-d and AMD's IOMMU (also called "AMD-Vi") let the hypervisor control which memory each device can reach. You need it for passing a GPU or NVMe drive straight to a VM, and Windows security features use it to block DMA attacks. If you're in the menu anyway, turn both on.
The third piece, second-level address translation (SLAT), is built into every recent CPU and has no switch. Hyper-V requires it, per Microsoft's Hyper-V system requirements, so on very old hardware the answer can be "this machine can't do it" rather than "the setting is off". What those VMs are for is a separate question, covered at the end.
Check whether it's already on
It may already be on, so check before you reboot anything. Open Task Manager, go to Performance, click CPU, and look for "Virtualization: Enabled" under the graph.
From a command prompt, systeminfo gives a fuller answer. Scroll to "Hyper-V Requirements". If every line says Yes, the firmware side is done.
There's one trap. If the line reads "A hypervisor has been detected. Features required for Hyper-V will not be displayed", virtualization is already on and in use. Hyper-V, WSL2 or memory integrity is running, and Windows hides the detail because the hypervisor has claimed the CPU extensions. That's a pass, not a failure.
Where each vendor hides it
Getting into the firmware is the same everywhere: Settings > System > Recovery > Advanced startup > Restart now, then Troubleshoot > Advanced options > UEFI Firmware Settings. That route works when the boot key is too fast to catch. After that, the menus split by vendor. Names and paths vary by model and BIOS version, so treat these as the first places to look, not guarantees.
| Vendor | Boot key | Where to look | What it's called |
|---|---|---|---|
| Dell | F2 (on 2025 and later models, Ctrl + Alt + S shows hidden settings) | Virtualization Support | Enable Intel Virtualization Technology, VT for Direct I/O |
| HP | Esc, then F10 | Business models: Advanced > System Options. Consumer models: Configuration. Older models: Security | Virtualization Technology (VTx), Virtualization Technology for Directed I/O (VTd) |
| Lenovo ThinkPad | F1 | Security > Virtualization | Intel Virtualization Technology, Intel VT-d Feature, or AMD-V equivalents |
| ASUS | F2 or Del, then F7 for Advanced Mode on desktop boards | Advanced > CPU Configuration | Intel (VMX) Virtualization Technology, or SVM Mode on AMD |
| MSI | Del | Intel: OC > CPU Features. AMD (AM5): OC > Advanced CPU Configuration | Intel Virtualization Tech and Intel VT-D Tech, or SVM Mode on AMD |
| Gigabyte | Del, then F2 to switch from Easy Mode to Advanced Mode | Tweaker > Advanced CPU Settings | Intel (VMX) Virtualization Technology, or SVM Mode on AMD |
| Microsoft Surface | - | - | Ships enabled |
Save, exit, and check Task Manager again once Windows is back. If the option is greyed out, look for a BIOS supervisor password you haven't entered, or a BIOS so old it predates the setting. Our guide to BIOS updates covers the second case.
What needs it
Four things on a modern Windows machine depend on this switch. Hyper-V needs it to run any VM. WSL2 needs it too, together with the Virtual Machine Platform Windows feature, which Microsoft's manual install steps enable with dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart. Docker Desktop on Windows runs on WSL2 or Hyper-V, so it inherits both requirements.
The fourth is the one that matters most for a company fleet. Virtualization-based security (VBS) uses the Windows hypervisor to wall off parts of the OS, and features like memory integrity and Credential Guard run inside that wall. Microsoft's VBS hardware requirements list the CPU virtualization extensions and SLAT as required, and an IOMMU for protection against DMA attacks.
That answers the question in this r/sysadmin thread, which asks whether to leave virtualization off when users don't run VMs. Leaving it off also switches off the security features that run on the hypervisor. On a business laptop, that trade costs more than it saves.
How to enable VBS in BIOS
There is no VBS switch in the firmware. The BIOS provides what VBS stands on, and Windows turns VBS on. In the firmware that means virtualization (VT-x or SVM Mode) on, VT-d or the IOMMU on, and Secure Boot on, which Microsoft lists as required for VBS. Our guide to checking Secure Boot covers that last switch.
Then turn it on from Windows. On one PC, memory integrity sits under Windows Security > Device security > Core isolation details. On a fleet, Microsoft's memory integrity guide gives the Intune settings catalog entry (Virtualization Based Technology > Hypervisor Enforced Code Integrity) and the Group Policy route, where "Enabled without UEFI lock" keeps the setting removable by policy later.
To confirm, run msinfo32 from an elevated prompt and read the VBS lines at the bottom of System Summary. Virtualization-based security set to Running means the firmware side and the Windows side are both in place.
Errors that point back to the BIOS
Each tool reports a missing switch in its own words. These are the messages that point straight at the firmware setting.
- WSL2: "Error: 0x80370102 The virtual machine could not be started because a required feature is not installed." Microsoft's WSL troubleshooting page says to turn on the Virtual Machine Platform feature and make sure virtualization is enabled in the BIOS.
- Docker Desktop: an "Unexpected WSL error" ending in HCS_E_HYPERV_NOT_INSTALLED. Docker's troubleshooting guide lists virtualization disabled in the BIOS as the first cause.
- Hyper-V: event 41 from Hyper-V-Hypervisor in the System log, "Hyper-V launch failed; Either VMX not present or not enabled in BIOS."
If the firmware setting is on and the error stays, check two things. First, power the machine off completely: Microsoft's guidance for event 41 says a restart is not sufficient after the BIOS change. Second, check that Windows still launches the hypervisor at boot, because Docker's guide names older VirtualBox versions and video game installers among the tools that switch it off. bcdedit /enum | findstr -i hypervisorlaunchtype shows the value, and bcdedit /set hypervisorlaunchtype auto from an admin prompt, followed by a restart, turns it back on.
Docker Desktop has also improved its own messages. Version 4.94, from October 2026, says at startup when virtualization is disabled in firmware, and version 4.93 fixed a false "Virtualization support not detected" error on machines with Virtual Machine Platform turned on, per Docker's release notes. If Task Manager shows virtualization as enabled and Docker disagrees, update Docker Desktop first.
Switch it on across a fleet
Walking to each desk and pressing F2 doesn't scale past a handful of machines. Dell, HP and Lenovo each ship a tool that changes firmware settings from inside Windows, so an RMM or Intune can push the change and the setting takes effect at the next reboot.
On Dell, Dell Command | Configure sets it from the command line with cctk --Virtualization=Enabled --VtForDirectIo=Enabled. On HP, the Client Management Script Library does it in PowerShell with Set-HPBIOSSettingValue -Name "Virtualization Technology (VTx)" -Value "Enable", and the older BIOS Configuration Utility takes a config file instead. On Lenovo, it's WMI: call SetBiosSetting("VirtualizationTechnology,Enable") on the Lenovo_SetBiosSetting class, then save once with Lenovo_SaveBiosSettings. Lenovo's guide warns to save once at the end, not after every setting.
Setting names differ between models, even within one vendor. Read the current value first, on a pilot machine of each model, before you push anything. The same habit applies to every firmware change, as our PowerShell commands guide puts it: get before you set.
If you'd rather see the single-PC version first, this short walkthrough goes through the menus and the Task Manager check.
OpenFrame can run the vendor script as a bulk operation across the machines that need it, with an approval gate before anything touches the firmware.
BIOS passwords and change control
If the fleet has a BIOS supervisor password, and managed business machines should, every vendor tool needs it to change a setting. That turns a one-line change into a secrets problem: the script has to carry the password without leaving it in plain text in a log or a deployment package.
Setting that password in the first place can be harder than using it. In this May 2026 thread, a tech with a Lenovo fleet already in the field quotes Lenovo's own WMI guide: WMI can't set an initial password from blank, only change or clear an existing one.
Treat a firmware change like any other change. Inventory which models you have, set or confirm the BIOS password, run the vendor tool on a pilot group, reboot, and verify with systeminfo before you widen the rollout. A firmware setting that half the fleet ignored because of a model mismatch is worse than one you never pushed, because the report says it's done. If the same models also need TPM switched on for BitLocker, bundle both into one change window. Our TPM guide covers that side.
One switch, four features
Virtualization in BIOS is a single setting that four Windows features lean on: Hyper-V, WSL2, Docker Desktop and VBS. Check it before you reboot, turn on VT-d or IOMMU while you're there, and on a fleet, push it with the vendor's own tool behind a BIOS password you control.
For the part that comes after the switch, read our guide to what virtualization is and how to pick a hypervisor.

Aliaska Varieva
VP of Engineering
Hi! I’m Aliaska, and I’ve been working as a software engineer (mostly Java + a bit Kotlin) for over 8 years now. I mostly spend my time building backend services, integrating systems, fixing bugs (the fun part 🙃), and making sure things don’t fall apart behind the scenes.
Related Content
Frequently Asked Questions
/blog/how-to-enable-virtualization-in-bios
Still deciding?
Ask Mingo answers from our docs and customer stories.