To enable virtualization in Windows 11, go to Settings > System > Recovery, select Restart now next to Advanced startup, then choose Troubleshoot > Advanced options > UEFI Firmware Settings > Restart, and set the processor’s virtualization item (Intel VT-x, AMD-V or SVM Mode) to Enabled before you save and exit. If your app also needs a Windows component, turn on Virtual Machine Platform or Hyper-V in Turn Windows features on or off afterward.
This applies to Windows 11 Home, Pro and Enterprise on Intel and AMD PCs. The firmware setting works in every edition; only Hyper-V is limited to Pro and Enterprise.
Check First, Because It Is Often Already On
Microsoft points out that many Windows devices already have virtualization enabled, and that it is always on for Surface devices. A 30-second check can save you a trip into the firmware.
- Press Ctrl + Shift + Esc to open Task Manager.
- Select Performance in the left column (the icon that looks like a small graph).
- Select CPU. The processor graph opens.
- Read the Virtualization line in the details under the graph. It says Enabled or Disabled.

If it says Enabled, skip to the section on Windows features. If it says Disabled, the firmware setting is off and the next two sections are for you.
For a more detailed answer, open Terminal or Command Prompt, type systeminfo and press Enter. At the bottom of the output, the Hyper-V Requirements section lists items such as virtualization enabled in firmware and Second Level Address Translation, each marked Yes or No. If you instead see “A hypervisor has been detected. Features required for Hyper-V will not be displayed,” Windows is already running a hypervisor, which means virtualization is on and in use.
What Actually Needs Virtualization on Windows 11
Two different switches are involved, and mixing them up is the most common reason the task feels unfinished. The firmware switch makes the processor’s virtualization features available. A Windows feature then decides which part of Windows uses them. The table shows what common tools ask for.
| You want to use | Firmware virtualization | Windows feature to turn on |
|---|---|---|
| WSL 2 (Linux on Windows) | Required | Virtual Machine Platform (wsl --install turns it on for you) |
| Hyper-V Manager virtual machines | Required | Hyper-V (Pro and Enterprise only) |
| Windows Sandbox | Required | Windows Sandbox |
| Google Play Games on PC | Required | Windows Hypervisor Platform, if the installer asks |
| Memory integrity (Windows Security) | Required | None; it is a Windows Security setting |
| Android emulators and other virtual machine apps | Usually required | Whatever the app’s own requirements list |
Google lists “Hardware virtualization must be turned on” among the PC requirements for Google Play Games, and the article on getting Google Play apps and games on Windows 11 explains what that app can and cannot do now that the Windows Subsystem for Android is gone. Microsoft’s Core isolation page also notes that memory integrity needs virtualization turned on in UEFI or BIOS.
Open UEFI Firmware Settings From Windows 11
The setting is not in Windows, so the PC has to restart into its firmware (the setup program many makers still call BIOS). Starting the trip from Windows avoids racing a startup key. Save open work first, because the restart happens as soon as you confirm it.
- Press Windows + I to open Settings.
- Select System, then select Recovery on the right.
- Next to Advanced startup, select Restart now, then confirm with Restart now in the message that appears. The PC restarts to a blue Choose an option screen.
- Select Troubleshoot, then Advanced options.
- Select UEFI Firmware Settings, then Restart. The PC restarts again and opens the firmware setup screen.

Two other routes reach the same blue screen. Microsoft’s Windows Recovery Environment documentation describes holding Shift while you select Restart from the power menu on the sign-in screen. You can also press the maker’s setup key right after power on; Dell, for example, documents F2 at the Dell logo. If UEFI Firmware Settings is missing from Advanced options, or the key goes by too fast, the walkthrough on opening BIOS or UEFI in Windows 11 lists the startup keys by brand and the usual reasons the option does not appear.
Turn On the Processor Virtualization Setting
Firmware screens differ by maker, and many respond only to the keyboard. Arrow keys move, Enter opens an item, and the save and exit keys are usually listed along the bottom or side of the screen.
- Open the tab where processor options live. Common names are Advanced, Configuration, CPU Configuration, Security or Virtualization Support.
- Find the virtualization item. Intel PCs usually call it Intel Virtualization Technology, Intel VT-x or VMX. AMD PCs usually call it SVM Mode or AMD-V. On Dell PCs it is Virtualization, under Advanced or Virtualization Support.
- Change it to Enabled.
- Choose Save and Exit (often the F10 key) and confirm. The PC restarts into Windows.
- Open Task Manager, go to Performance > CPU, and confirm that Virtualization now reads Enabled.


Change nothing else on these screens. Microsoft warns that adjusting other firmware settings might keep you from getting into Windows, so leave Secure Boot, boot order and storage options where they are, even when they sit next to the virtualization item.
You may see a second, related item called VT-d, Virtualization for Direct-IO or, on AMD boards, IOMMU. It lets a virtual machine use a physical device directly. Dell’s instructions turn it on together with the main setting, and leaving it on is harmless, but WSL 2, Windows Sandbox and ordinary virtual machines only need the main CPU item.
For model-specific screens, Microsoft’s Enable virtualization on Windows page links each major maker’s instructions (Acer, ASUS, Dell, HP and Lenovo). Dell’s hardware virtualization article adds that on Dell computers released in 2025 or later, some hidden settings such as VT-x appear only after you press Ctrl + Alt + S in the BIOS.
Turn On the Windows Feature Your App Needs
Once the firmware switch is on, some tools work right away. Others need one of these components, which you turn on from the classic Windows Features window.
- Select Start, type Windows features, and open Turn Windows features on or off.
- Check the box for the component your app asks for: Virtual Machine Platform for WSL 2, Hyper-V for Hyper-V Manager, Windows Sandbox for Sandbox, or Windows Hypervisor Platform for apps such as Google Play Games that request it.
- Select OK. Windows installs the files and shows a progress window.
- Select Restart now when asked. The feature is active after the restart.

The same features can be turned on from an administrator PowerShell window (right-click Start, choose Terminal (Admin), and approve the prompt). Microsoft documents these commands:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
Enable-WindowsOptionalFeature -FeatureName "Containers-DisposableClientVM" -All -Online
The first turns on Hyper-V and asks you to type Y to restart. The second turns on Virtual Machine Platform and leaves the restart to you. The third turns on Windows Sandbox. For Linux, wsl --install turns on what WSL needs and installs Ubuntu in one step, and the guide to setting up WSL 2 on Windows 11 covers the WSL commands after that.
Turn on only what you need. Microsoft notes that VMware Workstation and VirtualBox can run into trouble when the Hyper-V hypervisor is running unless you use versions that support Hyper-V, so a PC that runs those apps should not get Hyper-V and Windows Hypervisor Platform switched on without a reason. Android emulators have their own rules here; the article on installing BlueStacks on Windows 11 explains which BlueStacks builds work alongside Hyper-V.
Windows 11 Home and Hyper-V
Microsoft’s Hyper-V installation page states that the Hyper-V role cannot be installed on Windows 11 Home. Home users still get the firmware setting, Virtual Machine Platform and WSL 2, and can run third-party virtual machine apps. Hyper-V itself needs a 64-bit processor with Second Level Address Translation (SLAT), VM Monitor Mode extensions and at least 4 GB of memory.
When Virtualization Still Shows Disabled
Work down this list. Each item matches a cause that Microsoft or a PC maker documents.
- The change was not saved. Go back into firmware, confirm the item reads Enabled, and leave with the save option, not exit without saving.
- There is no virtualization item at all. Dell states that a Dell PC whose BIOS has no virtualization option does not support it. On other brands, check the model’s support page and install any firmware update the maker offers, then look again.
- The processor is too old. Microsoft’s WSL troubleshooting page says WSL 2 needs SLAT, which arrived with first generation Intel Core processors, and that chips such as the Intel Core 2 Duo cannot run it. To find your processor’s exact model, use the steps for checking PC specs in Windows 11.
- systeminfo shows a Hyper-V requirement as No. Besides virtualization, Hyper-V needs Data Execution Prevention, which Intel firmware calls the XD (execute disable) bit and AMD calls the NX (no execute) bit. Make sure that item is enabled too, as Microsoft’s Hyper-V requirements page lists.
- Windows Hypervisor Platform appears but Hyper-V does not. Microsoft says this means the PC might not be compatible with Hyper-V.
- WSL shows error 0x80370102. Turn on Virtual Machine Platform and the firmware setting, restart, then check the hypervisor launch setting in an administrator window with
bcdedit /enum | findstr -i hypervisorlaunchtype. If it shows Off, runbcdedit /set hypervisorlaunchtype Autoand restart, as Microsoft’s WSL troubleshooting page describes. - Windows 11 is itself running in a virtual machine. The firmware setting does not exist there. The host has to expose virtualization to the guest (nested virtualization); on a Hyper-V host, Microsoft’s command is
Set-VMProcessor -VMName "VM name" -ExposeVirtualizationExtensions $true(with the virtual machine’s name from Hyper-V Manager).
How to Turn It Off Again
Reverse only the part you changed. To remove a Windows component, open Turn Windows features on or off, clear its box, select OK and restart. To turn off the firmware setting, restart into UEFI Firmware Settings the same way, set the item to Disabled, and save and exit.
Think twice before the second one. WSL 2, Hyper-V machines, Windows Sandbox and emulators stop working, and memory integrity in Windows Security depends on the same hardware feature. Microsoft recommends keeping memory integrity on, so on most PCs the firmware setting should stay enabled even if you remove the apps that needed it.
Questions About Virtualization in Windows 11
Does Windows 11 need virtualization turned on to work?
No. Windows 11 runs with the setting off. Features built on it, such as WSL 2, Windows Sandbox, Hyper-V and memory integrity, are what stop working. Microsoft lists memory integrity as on by default in Windows 11, so a PC with virtualization off is also missing that protection.
Is the Windows 11 process different from Windows 10?
The firmware part is the same. The difference is the starting point: Windows 10 keeps Recovery under Update & Security, while Windows 11 puts it under System. The separate guide to enabling virtualization in Windows 10 follows that path, and also notes that Windows 10 support ended on October 14, 2025.
Do I need Hyper-V turned on to use VirtualBox or VMware?
No. Those apps need the firmware setting, not Hyper-V. Microsoft advises running versions of VMware and VirtualBox that support Hyper-V if both are installed, or turning the Hyper-V features off when they conflict.
Will turning on virtualization in firmware change anything I can see?
Not by itself. The setting makes a processor feature available; nothing new appears in Windows until an app or Windows feature uses it. The visible proof is the Virtualization: Enabled line in Task Manager.
Is it safe to leave virtualization enabled?
Yes for typical home use, and Windows relies on it for memory integrity. As with any firmware visit, the risk comes from changing other settings by accident, which is why the steps above change only the one item.