Virtualization is one BIOS switch standing between you and WSL2, Hyper-V, Windows Sandbox, VirtualBox, Docker Desktop and nearly every Android emulator worth installing. To enable virtualization in BIOS, you restart into the UEFI firmware, turn on Intel Virtualization Technology (VT-x) or AMD SVM Mode, save, and then confirm the result inside Windows 11. The hard part is the menu itself, because a Microsoft Q&A answer puts it plainly: “The location of the virtualization setting depends on the PC manufacturer.”

This tutorial runs through 13 steps in about 30 minutes. You check the current state, enter the firmware, flip the right settings on ASUS, MSI, Gigabyte and ASRock boards, save safely, and prove the result with Task Manager, PowerShell and a real WSL2 install. If your goal is Android gaming, the same switch matters for setting up LDPlayer 9 on a gaming PC, because missing hardware virtualization is a classic cause of slow or refused emulator launches.

The advice reflects the hardware market on November 06, 2026. AMD’s product page lists the Ryzen 9 9950X3D as its newest Ryzen 9 X3D desktop chip, and Intel’s documentation now covers its Core Processor Series 3. Every one of those chips still uses the same two names: VT-x on Intel and SVM on AMD. No official source we checked says either name was renamed, retired or replaced.

·

Google · Preferred Sources

Don't miss new tech stories on Google

Add Tech Insider once in the Google app and our stories appear in your news suggestions.

Add Now

What BIOS Virtualization Does and Who Needs It

Hardware-assisted virtualization is a set of instructions built into the CPU. It lets a hypervisor run a guest operating system directly on the processor instead of translating every instruction in software. Without it, a virtual machine either refuses to start or crawls. With it, a Linux guest boots in seconds and an Android emulator reaches playable frame rates.

Two vendor names cover the whole story. Intel calls the feature Intel Virtualization Technology, shortened to VT-x, and some boards label it VMX. AMD calls it SVM, short for Secure Virtual Machine, and also uses the older marketing name AMD-V. Both live in the motherboard firmware, not in Windows. That means no Windows setting, registry tweak or driver update can turn the feature on if the BIOS keeps it off.

The stakes are practical. A PC with the flag off cannot run a modern developer toolchain, a Linux subsystem or a serious emulator, even if the processor is brand new and expensive. Owners of a current chip such as the Ryzen 9 9950X3D hit this wall just as often as owners of five-year-old laptops, because the factory firmware profile, not the CPU, decides the default. Plenty of software depends on that one switch:

WSL2. The second generation of Windows Subsystem for Linux runs a real Linux kernel inside a lightweight virtual machine, so it needs virtualization in firmware plus the Virtual Machine Platform feature in Windows.

Hyper-V. Microsoft’s own hypervisor needs the firmware flag and a Windows edition that includes it, which means Pro, Enterprise or Education.

Windows Sandbox and Docker Desktop. Both lean on the same Windows virtualization features.

VirtualBox and VMware Workstation. Third-party hypervisors check the same CPU flags and refuse to start 64-bit guests when they are off.

Android emulators. BlueStacks, LDPlayer, MuMu and similar apps use hardware virtualization for speed. Our explainer on what affects Android emulator performance on Windows 11 covers CPU, RAM, GPU and virtualization together, and our look at Hyper-V compatibility for Windows 10 Android emulators shows how the hypervisor question changes by Windows version.

Many boards ship with the feature already enabled, and MSI says in its support material that its supported Intel notebooks generally have VT-x and VT-d switched on by default. Desktop boards vary more. A BIOS reset, a firmware update that loads defaults, or a board sold with conservative factory settings can all leave it off. So the first job is always to check before you change anything.

Prerequisites and Versions

You need less than most guides suggest. The list below covers the hardware, software and habits that keep this job short and safe.

CPU: any modern Intel Core or AMD Ryzen processor. Current examples include AMD’s Ryzen 9 9950X3D and Intel’s Core Ultra X9 388H, whose Intel product page reportedly lists VT-x as supported. Very old low-end chips may lack the feature, so check your exact model on the maker’s spec page.

Motherboard or laptop: ASUS, MSI, Gigabyte or ASRock boards are covered here. Laptops from other brands use the same two settings under different menu names.

Windows 11: any supported release. Home edition handles WSL2 and the Virtual Machine Platform. Hyper-V itself needs Pro, Enterprise or Education.

PowerShell: version 5.1 (built into Windows 11) or PowerShell 7.x. Open it as Administrator for the Windows feature steps.

Ubuntu 24.04 LTS: the Linux distribution used for the WSL2 test in Step 12.

Optional tools: Sysinternals Coreinfo for a deep CPU feature dump, and VirtualBox 7.x if you want a second hypervisor check.

A wired keyboard: some boards ignore Bluetooth keyboards until Windows loads.

Your BitLocker recovery key: firmware changes rarely trigger a recovery prompt, but a saved key turns a scary screen into a two-minute detour.

Time and power: about 30 minutes. Plug a laptop into mains power first.

If your PC is an Arm-based Windows laptop, stop here. Arm machines do not expose an x86 VT-x or SVM switch, and the steps below do not apply. Our comparison of BlueStacks and WSABuilds on Arm laptops explains how Android emulation works on that hardware instead.

The Settings You Will See: VT-x, SVM, VT-d and IOMMU

Firmware menus use a handful of names for the same ideas. The table below maps the labels to what they do, so a strange menu entry does not send you down the wrong path.

The first row is the one almost everyone needs. The second row only matters if you hand a physical device, usually a graphics card, to a virtual machine. AMD’s technical article on building a private cloud with Ryzen AI Max, published in October 2026, tells readers to enable SVM and, where device or GPU passthrough is required, IOMMU. It adds that the BIOS location varies by motherboard vendor and typically sits under AMD CBS or the Advanced CPU and PCI menus.

Microsoft’s own support page, “Enable Virtualization on Windows,” follows the same split. It sends Intel owners to a VMX guide and AMD owners to an AMD-V guide, which tells you the vendor-specific menus are the real obstacle. Once the firmware flag is on, Windows needs its own features switched on as well, and Steps 10 to 12 cover that part.

Reading the labels takes a little care. The Intel entry sometimes carries a prefix such as Intel (VMX) in front of Virtualization Technology, and the AMD entry sometimes appears as plain SVM with no word Mode after it. Treat all of these as the same control. If you see a separate entry called Virtualization Technology Redirect Protection or something similar, ignore it for this job, because it is a different Intel capability and not the master switch.

One more distinction saves confusion. VT-x and SVM are CPU features. VT-d and IOMMU belong to the chipset and memory controller. Enabling the second pair does nothing for WSL2 if the first pair is still off, and the reverse is also true for passthrough projects.

Step 1 to 4: Check the Current State Before You Reboot

Do the reading first. A two-minute check often shows the feature is already on, and the real problem sits in Windows.

Step 1: Check Task Manager

Press Ctrl+Shift+Esc, open the Performance tab, and click CPU. The lower right shows a line labeled Virtualization. It reads Enabled or Disabled. If a hypervisor is already running, for example because Hyper-V or Memory Integrity is active, Windows may show extra text about a hypervisor, and the line still reads Enabled.

Step 2: Run the command-line check

Open PowerShell and run the two commands below. The first prints the Hyper-V requirement block from systeminfo, and the second reads the CPU flag directly.

systeminfo | Select-String -Pattern "Hyper-V Requirements" -Context 0,4 (Get-CimInstance -ClassName Win32_Processor).VirtualizationFirmwareEnabled

A healthy result on a machine where no hypervisor is running looks like this:

> Hyper-V Requirements: VM Monitor Mode Extensions: Yes Virtualization Enabled In Firmware: Yes Second Level Address Translation: Yes Data Execution Prevention Available: Yes True

If a hypervisor is already active, systeminfo prints a different message instead, one that says a hypervisor has been detected and that the Hyper-V feature list is hidden. That message is good news. A hypervisor cannot run unless virtualization is on, so you can skip ahead to Step 10.

Step 3: Identify your CPU and motherboard

Next, find out exactly what you have. The menu names depend on the board and the BIOS version, so write both down.

Get-CimInstance Win32_Processor | Select-Object Name Get-CimInstance Win32_BaseBoard | Select-Object Manufacturer, Product, Version

Typical output names an Intel or AMD CPU and a board such as a Z-series, B-series or X-series model from ASUS, MSI, Gigabyte or ASRock. Keep that product string handy. You will paste it into the maker’s support page if the setting turns out to be missing.

Step 4: Save your BitLocker key and note your BIOS settings

Check whether drive encryption is active and copy the recovery key somewhere off the PC. Run this in an elevated PowerShell window.

manage-bde -status C: manage-bde -protectors -get C:

If protection shows as On, store the numerical password in your Microsoft account, a USB stick or a password manager. Then take a phone photo of any BIOS settings you have customized, such as fan curves or memory profiles. Firmware changes seldom disturb them, but a photo costs five seconds. Finally, plug a laptop into power and close everything you have open.

Step 5 and 6: Enter the BIOS and Reach Advanced Mode

Now the firmware. You have two reliable routes into it, and the Windows route works even on boards with fast boot that skip the “press Delete” prompt.

Step 5: Boot into UEFI from Windows 11

Open Settings, go to System, then Recovery, and click Restart now next to Advanced startup. After the restart, Windows shows a blue menu. Microsoft’s guide says to choose “Select Troubleshoot > Advanced options > UEFI Settings > Restart.” On some builds the entry reads UEFI Firmware Settings, but the path is the same.

Prefer the keyboard? One command restarts straight into the firmware:

shutdown /r /fw /t 0

If that command reports that the firmware does not support the request, fall back to the classic method. Power the PC on and tap the BIOS key repeatedly. Delete works on most desktop boards from ASUS, MSI, Gigabyte and ASRock, and F2 works on many too.

Step 6: Switch from the simple screen to Advanced mode

Modern boards open on a friendly dashboard with temperatures, fan speeds and a boot-order strip. The virtualization setting almost never lives there. On many recent boards, a function key flips the view to a full menu tree. ASUS and MSI boards typically use F7 for that toggle. Gigabyte boards typically use F2 to move between simple and classic views, and ASRock boards typically use F6 for Advanced mode. Your screen usually prints the exact key along the bottom or top edge, so trust the screen over this list.

Once you reach the classic view, look for a tab or section named Advanced, Settings, Tweaker, OC or CPU Configuration. Do not change anything yet. Just locate the CPU submenu, because Step 7 starts there.

Step 7 to 9: Enable Virtualization in BIOS and Save

This is the shortest part of the job. Three actions: turn on the CPU flag, decide on I/O virtualization, and save the change correctly.

Step 7: Turn on VT-x or SVM Mode

On an Intel board, find Intel Virtualization Technology, which some firmware abbreviates to VT-x or VMX, and set it to Enabled. On an AMD board, find SVM Mode or Secure Virtual Machine and set it to Enabled. When you enable virtualization in BIOS on an AMD board, the entry often hides below an AMD CBS or CPU Features branch, so follow AMD’s tip about the Advanced CPU and PCI menus if the first pass finds nothing.

Menu paths drift between board generations and BIOS versions, so treat the following as starting points rather than promises:

ASRock’s support FAQ points Intel users to BIOS, Advanced, CPU Configuration, Intel Virtualization Technology, Enabled.

MSI’s notebook guidance uses Advanced, then Intel Virtualization Technology and VT-d on Intel, or Advanced, then SVM and IOMMU on AMD.

ASUS documentation refers to the control as VT or SVM, depending on the CPU brand.

Gigabyte describes the Intel option as Intel Virtualization Technology and the AMD option as SVM Mode.

Step 8: Decide on VT-d or IOMMU

Skip this step if you only want WSL2, Hyper-V, Sandbox or an Android emulator. Enable VT-d on Intel or IOMMU on AMD only if you plan device passthrough, such as giving a GPU to a Proxmox or KVM guest. AMD’s October 2026 guidance lists IOMMU as a requirement for that scenario, and Gigabyte’s support history for the B760 DS3H DDR4 board says a September 2025 BIOS already turned VT-d and IOMMU on before boot by default, alongside Pre-boot DMA Protection. If your board shows those options already enabled, leave them alone.

Step 9: Save, exit and watch the first boot

Press F10, or use the Save and Exit tab, and confirm the prompt. The PC restarts. Let it boot all the way to the Windows sign-in screen without touching anything. If you see a BitLocker recovery screen, enter the key you saved in Step 4. If the screen stays black for more than a minute, power off, wait ten seconds, and boot again. A second restart is normal after a firmware change because the board retrains memory.

One warning belongs here. Never flip five other options while you are in the menu. If something breaks, you will not know which change caused it. Change the virtualization entry, save, and leave the rest of the firmware alone.

Vendor Notes for ASUS, MSI, Gigabyte and ASRock

The four big board makers all document the same two controls, but their wording and layouts differ. These notes come from each maker’s support material as of this month, and they are hedged because your BIOS version decides the final menu text.

ASUS

ASUS support pages describe the control as VT or SVM and link to instructions for enabling virtualization and installing a virtual machine in Windows. On an Intel board, look for Intel Virtualization Technology. On an AMD board, look for SVM Mode. According to the ASUS support material, which was updated in October 2026, the same page group is where you find the current BIOS download for your exact model. That matters if the option is missing and a newer BIOS is the fix.

MSI

MSI’s official notebook guidance says Intel systems use Advanced, then Intel Virtualization Technology and VT-d, while AMD systems use Advanced, then SVM and IOMMU. The guide says to save with F10 and reboot. MSI also says its supported Intel notebooks generally ship with VT-x and VT-d enabled, which explains why laptop owners often only need Windows features. Desktop owners should expect the entry under a CPU features or advanced CPU branch.

Gigabyte

For Gigabyte Intel boards, the setting is generally described as Intel Virtualization Technology, and on AMD boards as SVM Mode. The company publishes a changelog on each board’s support page, and the B760 DS3H DDR4 support page is a good example of what to read. According to that page, BIOS F17 appeared on September 29, 2026 and prepared the board for upcoming processor support. Reading the changelog tells you whether a newer BIOS touched virtualization defaults.

ASRock

ASRock’s FAQ names the Intel path in full: BIOS, Advanced, CPU Configuration, Intel Virtualization Technology, Enabled. For AMD, it names the entry Secure Virtual Machine and says the CPU must support AMD-V. ASRock updated its virtualization FAQs in October 2026, according to the company’s support pages. If you keep an EXPO memory profile on an ASRock or any other board, remember that loading default settings can reset it, and our guide to AMD EXPO ULL RAM setup shows how to restore it.

Step 10 to 13: Verify It in Windows 11 and Put It to Work

The firmware flag is only half the job. These four steps prove the change stuck and switch on the Windows features that use it.

Step 10: Confirm the flag in Windows

Repeat the checks from Steps 1 and 2. Task Manager should now read Virtualization: Enabled, and the PowerShell query should print True. Compare your results with this table.

If any row shows a problem, jump to the troubleshooting section before continuing.

Step 11: Enable the Windows virtualization features

Microsoft’s walkthrough tells you to open Windows Features and says, “In the Windows Features window that just opened, find Virtual Machine Platform and select it.” You can skip the dialog and do the same job in an elevated PowerShell window. The first command enables the Virtual Machine Platform. The second enables Hyper-V on Pro, Enterprise or Education editions. The third adds the Windows Hypervisor Platform, which some third-party emulators and VMs use.

dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All -All -NoRestart Enable-WindowsOptionalFeature -Online -FeatureName HypervisorPlatform -All -NoRestart Restart-Computer

Home edition users will see an error on the second command because Hyper-V is not part of Home. That is expected, and WSL2 still works through the Virtual Machine Platform. Not every workload needs every feature, so the table below shows what to switch on for each job and avoids piling hypervisor layers onto a PC that does not need them.

The pattern is simple. Every row needs the firmware flag, and only a few need a Windows feature on top. Turn on the minimum set for your goal. Extra layers do not make anything faster, and they raise the odds that two hypervisors fight over the same CPU resources. Readers who remember Android apps on Windows can also see our walkthrough of the Windows Subsystem for Android alternatives, which explains what to run now that the old subsystem is gone.

After the reboot, confirm the hypervisor launches at boot. This command should print hypervisorlaunchtype Auto.

bcdedit /enum | Select-String hypervisorlaunchtype

Step 12: Install WSL2 and boot Ubuntu 24.04

This is the real-world test. A WSL2 distribution only starts when virtualization works end to end.

wsl --update wsl --install -d Ubuntu-24.04 wsl -l -v

Windows downloads the distribution and asks you to create a Linux username and password. The last command prints a table. A working install looks like this:

NAME STATE VERSION * Ubuntu-24.04 Running 2

A VERSION value of 2 confirms that the distribution runs inside a virtual machine, which proves hardware virtualization is on. If you see error code 0x80370102, jump to the troubleshooting section, because that code points straight at the BIOS switch.

Two more commands are worth knowing before you move on. The first prints the WSL version details and the default distribution. The second shuts the whole WSL virtual machine down, which is the quickest way to apply a configuration change or recover from a stuck session.

wsl --status wsl --shutdown

Next, open the Ubuntu shell and run uname -r. The command prints the Linux kernel version that Microsoft ships for WSL2. Seeing a real Linux kernel string, rather than an error, is the practical proof that the hypervisor, the Virtual Machine Platform and your BIOS setting all work together. Docker Desktop users get a free bonus here. When you pick the WSL2 backend in Docker’s settings, the app reuses this same virtualization stack and needs nothing extra from the firmware.

Step 13: Run the readiness script and keep a record

Finally, run the one-file readiness check from the next section. It collects the CPU flag, hypervisor state and Windows feature status into a short report you can save, share with support or run again after a BIOS update. That makes it the closing proof for the 13 steps.

If you installed Hyper-V and want one more test, create a throwaway virtual machine from PowerShell. The example below builds an empty Generation 2 VM with 2 GB of startup memory and 20 GB of dynamic disk. It only proves that Hyper-V can create and start a guest, so you can delete it afterward.

New-VM -Name "VirtTest" -Generation 2 -MemoryStartupBytes 2GB -NewVHDPath "$env:USERPROFILE\VirtTest.vhdx" -NewVHDSizeBytes 20GB Start-VM -Name "VirtTest" Get-VM -Name "VirtTest" | Select-Object Name, State Stop-VM -Name "VirtTest" -TurnOff Remove-VM -Name "VirtTest" -Force

The Get-VM line should print the state Running. If Start-VM fails with a message about virtualization or a hypervisor that is not running, go back to the bcdedit check in Step 11 and confirm the hypervisor launch type is Auto. The empty VM has no operating system, so it simply sits at a firmware screen, and that is a normal result for this test.

Complete Working Project: A Virtualization Readiness Check

Copy this script into a file named Check-Virtualization.ps1 and run it in an elevated PowerShell window. It reports the firmware flag, whether a hypervisor is running, and the state of the four Windows features that matter. It then prints a plain verdict. The script also copes with the one trap that confuses people: when a hypervisor runs, some systems report the firmware flag as False even though virtualization works.

param( [switch]$AsJson ) $ErrorActionPreference = 'Stop' function Get-FeatureState { param([string]$Name) try { (Get-WindowsOptionalFeature -Online -FeatureName $Name).State.ToString() } catch { 'Unknown (run as Administrator)' } } $cpu = Get-CimInstance -ClassName Win32_Processor | Select-Object -First 1 $sys = Get-CimInstance -ClassName Win32_ComputerSystem $os = Get-CimInstance -ClassName Win32_OperatingSystem $firmwareOn = [bool]$cpu.VirtualizationFirmwareEnabled $hypervisor = [bool]$sys.HypervisorPresent if ($hypervisor) { $verdict = 'OK: a hypervisor is running, so virtualization is on.' } elseif ($firmwareOn) { $verdict = 'OK: virtualization is enabled in firmware.' } else { $verdict = 'OFF: enable Intel VT-x or AMD SVM Mode in the BIOS.' } $report = [ordered]@{ Computer = $env:COMPUTERNAME Windows = "$($os.Caption) build $($os.BuildNumber)" Cpu = $cpu.Name.Trim() FirmwareVirtualization = $firmwareOn HypervisorPresent = $hypervisor HyperV = Get-FeatureState 'Microsoft-Hyper-V-All' VirtualMachinePlatform = Get-FeatureState 'VirtualMachinePlatform' HypervisorPlatform = Get-FeatureState 'HypervisorPlatform' WslFeature = Get-FeatureState 'Microsoft-Windows-Subsystem-Linux' Verdict = $verdict } if ($AsJson) { $report | ConvertTo-Json } else { $report.GetEnumerator() | ForEach-Object { '{0,-24} {1}' -f $_.Key, $_.Value } }

Run it from the folder where you saved it. If PowerShell blocks the script, allow it for the current window only, which leaves your system policy untouched.

Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass .\Check-Virtualization.ps1 .\Check-Virtualization.ps1 -AsJson | Out-File "$env:USERPROFILE\virtualization-report.json"

A healthy report on a Pro edition machine with WSL2 installed looks like this. Your CPU and build number will differ.

Computer DESKTOP-EXAMPLE Windows Microsoft Windows 11 Pro build ##### Cpu AMD Ryzen 9 9950X3D 16-Core Processor FirmwareVirtualization True HypervisorPresent True HyperV Enabled VirtualMachinePlatform Enabled HypervisorPlatform Enabled WslFeature Enabled Verdict OK: a hypervisor is running, so virtualization is on.

If you also use Linux or run commands inside WSL, this short Bash companion checks the CPU flags and the KVM device. It reads /proc/cpuinfo for the vmx flag (Intel) or svm flag (AMD).

#!/usr/bin/env bash if grep -qE '(vmx|svm)' /proc/cpuinfo; then echo "CPU flag: virtualization visible ($(grep -oE -m1 '(vmx|svm)' /proc/cpuinfo))" else echo "CPU flag: no vmx or svm found" fi if [ -e /dev/kvm ]; then echo "KVM device: present" else echo "KVM device: missing (load kvm_intel or kvm_amd, or enable the BIOS switch)" fi

Common Pitfalls When You Enable Virtualization in BIOS

Most failed attempts trace back to the same seven mistakes. Knowing them in advance saves a second reboot.

Staying on the simple dashboard. The virtualization entry rarely appears in the easy view. Press the key that opens the advanced menu tree before you decide the option does not exist.

Enabling VT-d or IOMMU and stopping there. Those settings handle device remapping. They do not replace Intel Virtualization Technology or SVM Mode, and WSL2 still fails without the CPU flag.

Forgetting to save. Exiting with Esc or choosing Discard Changes throws the edit away. Use F10 and confirm the prompt.

Loading defaults by accident. A menu entry named Load Optimized Defaults or Restore Defaults resets virtualization, memory profiles and fan curves on some boards. Avoid it unless you intend a full reset.

Mixing hypervisors. When Hyper-V and the Windows Hypervisor Platform are active, VirtualBox and VMware fall back to Microsoft’s layer, and speed drops. Pick one main hypervisor per workflow, or accept the slower path.

Ignoring Windows features. A correct BIOS setting does not start WSL2 on its own. Steps 11 and 12 matter just as much as Step 7.

Changing other security settings while you are there. Turning off Secure Boot or the TPM to chase a different problem can block Windows 11 updates and some games. If you need those toggles, follow our guides to enabling TPM 2.0 in BIOS and enabling Secure Boot on Windows 11 rather than guessing.

There is also a quieter trap. Microsoft’s Q&A guidance, already quoted above, says the location depends on the PC manufacturer, and the same is true of the setting’s name. A hidden entry called Intel (VMX) Virtualization Technology is the same switch as VT-x. Typing the word virtualization into the firmware search box, where one exists, helps on newer boards.

Troubleshooting: 10 Fixes for Virtualization Problems

Work down this list in order. Each item names the symptom, the likely cause and the fix.

The option is missing from the BIOS. First switch to Advanced mode, then look under CPU Configuration, CPU Features, Tweaker or OC. If it is still absent, check your CPU’s spec page, because a few older or low-end models lack the feature. On a laptop, the maker may hide it, and a BIOS update from the support page sometimes restores the entry.

Task Manager still says Disabled after you enabled it. The change probably did not save. Re-enter the BIOS, confirm the entry reads Enabled, then exit with F10. Also check that you edited the right entry, because VT-d and IOMMU do not count.

systeminfo reports Virtualization Enabled In Firmware as No. The CPU flag is off. Return to Step 7. If you run an AMD system, confirm you set SVM Mode and not an unrelated AMD CBS entry.

WSL fails with error 0x80370102. Windows is telling you virtualization is off in the BIOS or the Virtual Machine Platform feature is missing. Check Task Manager, run the Step 11 commands, and reboot.

VirtualBox reports VERR_VMX_NO_VMX or VERR_VMX_MSR_ALL_VMX_DISABLED. Both messages point at VT-x being unavailable. Enable it in the BIOS. If it is already on, another hypervisor may hold the hardware, so see the next item.

An Android emulator or VM says virtualization is disabled when it is enabled. Windows features such as Hyper-V, Virtual Machine Platform and Memory Integrity put a hypervisor under Windows. Some emulators handle that cleanly and others do not. Update the emulator, turn on the Windows Hypervisor Platform, or switch the emulator to a compatible mode in its settings.

Hyper-V is missing from Windows Features. You are on Home edition. Use WSL2 and the Virtual Machine Platform instead, or upgrade to Pro.

The PC does not boot after the change. Power off, wait ten seconds, and try again, because memory retraining can take a second pass. If it still fails, clear the CMOS using the jumper, button or battery method in your board manual, then repeat the change on its own.

The setting resets itself. A BIOS update, a CMOS reset or a dying CMOS battery can load defaults. Re-enable the switch and rerun the Step 13 script after every firmware change. If it resets on every cold boot, replace the CMOS battery.

A managed work laptop blocks the change. Corporate firmware often uses a BIOS password or management policy. Ask your IT team, because bypassing it can break your device policy.

Advanced Tips for Power Users

Once the basics work, these options squeeze more out of the same switch. They suit developers, home-lab builders and anyone who runs more than one hypervisor.

Nested virtualization. If you run a hypervisor inside a Hyper-V VM, expose the CPU extensions to the guest. Shut the guest down first, then run this on the host.

Set-VMProcessor -VMName "LabVM" -ExposeVirtualizationExtensions $true

Check deeper CPU features. Sysinternals Coreinfo prints a feature matrix. The command coreinfo -v shows whether VMX (Intel) or SVM (AMD) is present, plus second-level address translation support, so you can tell a missing feature from a disabled one.

Trade security for compatibility, carefully. Windows security features like Memory Integrity use the hypervisor. MSI’s support material mentions that VBS, Memory Integrity and Hyper-V can affect third-party virtualization software. If an older emulator misbehaves, update it before you disable a protection. Turning Memory Integrity off weakens defenses, so treat it as a last resort and turn it back on afterward.

Linux and KVM. On a dual-boot or dedicated Linux box, lscpu | grep -i virtualization shows VT-x or AMD-V, and the kvm-ok tool from the cpu-checker package reports whether /dev/kvm is usable. Add your account to the kvm group so QEMU can open the device without root.

Device passthrough. For a GPU passthrough project, enable IOMMU in the BIOS, then confirm the kernel sees it. AMD’s Proxmox article walks through a full passthrough build and is worth reading end to end before you start.

Confidential computing. Server-grade hardware layers memory encryption on top of virtualization. If that interests you, our comparison of Intel TDX, AMD SEV-SNP and AWS Nitro shows how the three approaches differ, and none of them replaces the basic VT-x or SVM switch.

Automate the check. If you manage several PCs, or you simply want a log after every sign-in, register the readiness script as a scheduled task. It writes the latest JSON report to a folder you choose, and a diff between two reports shows exactly when a setting changed.

$action = New-ScheduledTaskAction -Execute 'powershell.exe' -Argument '-NoProfile -ExecutionPolicy Bypass -Command "& C:\Tools\Check-Virtualization.ps1 -AsJson | Out-File C:\Tools\last-report.json"' $trigger = New-ScheduledTaskTrigger -AtLogOn Register-ScheduledTask -TaskName 'VirtualizationCheck' -Action $action -Trigger $trigger -RunLevel Highest

Know the Fast Startup effect. Windows Fast Startup saves part of the system state on shutdown, and a shutdown followed by a power-on does not always reload every firmware setting the way a restart does. If a BIOS change seems not to apply, use Restart rather than Shut down for your first boot, or hold Shift while choosing Shut down to force a full power cycle.

Mind the performance trade-offs. Running WSL2 or a Hyper-V guest alongside a game is fine on a modern desktop, but the hypervisor does add a thin layer under Windows. Competitive gamers sometimes see small differences in latency-sensitive titles after enabling Hyper-V features, though results vary by game and by hardware. If that worries you, test with your own title and the Windows Hypervisor Platform switched off, then compare. Measure first and decide second.

Keep a record. Save the JSON report from the readiness script after each BIOS update. If a later update flips the setting, you will notice at once. For wider hardware tuning, browse the Hardware category for related walkthroughs.

Frequently Asked Questions

Is it safe to enable virtualization in BIOS?

Yes. The switch is a standard CPU feature, and every mainstream PC maker documents it. Enabling it does not void a warranty or damage hardware. The only practical effect is that software can now use the processor’s virtualization instructions, so a malicious program with the right privileges could in theory do the same as a legitimate hypervisor. Keep Windows updated, and the risk stays small.

Does enabling VT-x or SVM slow my PC down?

Not in normal use. The feature sits idle until a hypervisor or emulator asks for it. Running a virtual machine uses CPU and memory, of course, but that cost comes from the VM and not from the BIOS flag.

What is the difference between VT-x and VT-d?

VT-x virtualizes the processor so guests can run natively. VT-d virtualizes input and output, which lets the chipset assign a physical device to a guest. AMD’s names are SVM and IOMMU. Most people only need VT-x or SVM.

Why can’t I find virtualization in my BIOS?

The usual reasons are the simple view hiding the menu, a different label such as VMX or Secure Virtual Machine, or a laptop whose maker hides the entry. Open Advanced mode, search for the words virtualization, VMX and SVM, and check the CPU Configuration branch. If nothing appears, look up your CPU on the maker’s spec page.

Do I need virtualization enabled for Android emulators?

Most of them run far better with it, and several refuse to launch without it. After you enable it, check that the emulator’s own settings use the right graphics and engine mode.

How do I enable virtualization in BIOS on Windows 11 without pressing keys at boot?

Use Settings, System, Recovery, Advanced startup, then Restart now, and choose Troubleshoot, Advanced options, UEFI Firmware Settings. Or run shutdown /r /fw /t 0 from an elevated prompt. Both methods land you in the firmware without racing the boot screen.

Will a BIOS update turn virtualization off?

Sometimes. Updates can load default settings, and defaults vary by board. After every BIOS update, rerun the readiness script and re-enable the switch if the verdict reads OFF.

Do Arm-based Windows laptops have this setting?

No. Arm processors use their own virtualization design, and the x86 flags VT-x and SVM do not apply. The steps in this guide are for Intel and AMD PCs.