How to Enable AMD-V | BIOS Setting For Virtual Machines

Enabling hardware-assisted virtualization on an AMD system requires entering the BIOS or UEFI firmware and toggling the SVM Mode setting to Enabled.

If you are a developer running WSL 2, a gamer spinning up a local server, or an IT pro testing configurations in VMware Workstation, the difference between AMD-V being on versus off is night and day. Without it, your hypervisor has to handle memory mapping and instruction execution in software — a slow, inefficient process that leads to stuttering, long boot times, and error messages like “This host supports AMD-V, but AMD-V is disabled.” How to enable AMD-V is a straightforward process that takes about two minutes and requires flipping exactly one switch: SVM Mode. Most modern AMD motherboards leave this setting enabled, but if yours was configured for legacy OS compatibility or came with a specific firmware profile, it might be off. Here is exactly how to turn it on, verify it works, and get back to running your virtual machines at native speed.

Why Is AMD-V Disabled In The First Place?

AMD-V, also referred to as SVM (Secure Virtual Machine) mode in BIOS menus, is a hardware virtualization feature built into Ryzen, Athlon, and Opteron processors. It allows your CPU to handle virtual machines more efficiently by providing dedicated hardware resources for memory and process management. Manufacturers sometimes disable it by default to maintain compatibility with older operating systems or to meet specific enterprise security baselines. On ASUS and MSI motherboards, it is typically enabled out of the box, but it never hurts to confirm. If you are building a system for the first time, checking this box early saves a headache later.

Enabling AMD-V On Your AMD Processor: A Brand-By-Brand Guide

The universal first step is to restart your PC and press the BIOS key — usually Del, F2, F10, or F12 — during the initial boot screen. If the timing feels tricky, you can also enter the UEFI directly from Windows by navigating to Settings > System > Recovery > Advanced startup > Restart now, then clicking Troubleshoot > Advanced options > UEFI Firmware Settings > Restart. Once inside, the setting is almost always labeled SVM Mode.

The exact location varies slightly between manufacturers. The table below maps the path for the most common brands.

In the rare case the exact menu path does not match the table above (firmware versions differ between manufacturers), use your BIOS search function. On most modern systems, pressing Ctrl+F or F9 opens a search bar. Simply type “SVM” to jump directly to the correct setting. The official ASUS guide on enabling AMD-V covers their specific UEFI layout in detail, but the logic applies to almost every motherboard brand.

How To Check If AMD-V Is Working Correctly

After saving your BIOS changes with F10 and rebooting into Windows, you can confirm AMD-V is active in three seconds. Open Task Manager (Ctrl+Shift+Esc), click the Performance tab, and select CPU. At the bottom of the window, look for “Virtualization: Enabled.” If it says Enabled, you are good to go.

For a more definitive check, open Command Prompt and run:

systeminfo | find "Virtualization Enabled In Firmware: Yes"

If it returns the string, AMD-V is active. You can also use PowerShell:

Get-CimInstance Win_Processor | Select-Object Name, VirtualizationFirmwareEnabled

Troubleshooting: Common AMD-V Enablement Mistakes

If AMD-V still shows as disabled after following the steps above, the most common cause is a simple oversight in the BIOS or a conflict with Windows settings.

• Looking for “AMD-V”: The toggle is almost never called “AMD-V” in modern UEFI menus. It is labeled SVM Mode. Use your BIOS’s search function to find that exact string.
• Forgetting to Save: Enabling the setting does nothing if you exit without saving. Use the F10 hotkey to save and reboot, or select the “Save & Exit” option in your BIOS menu.
• Hyper-V Conflict: On Windows Pro and Enterprise, Hyper-V can take exclusive control of virtualization features. Disable it via Control Panel > Programs > Turn Windows features on or off, or run dism.exe /Online /Disable-Feature:Microsoft-Hyper-V-All in an administrator terminal.
• Secure Boot: Some systems require Secure Boot to be enabled for SVM to function. Check your BIOS Boot or Security tab if the regular path does not take effect.
• CPU Incompatibility: Very old AMD processors or specific enterprise models lack SVM support entirely. Check your CPU’s specifications on AMD’s official website to confirm AMD-V is listed.

Enabling AMD-V is one of those straightforward BIOS settings that delivers a major performance boost for zero cost. Once it is turned on, virtual machines run much closer to native hardware speed, and you can say goodbye to the cryptic errors that pop up when virtualization is left disabled.