Hardware virtualization cannot normally be enabled with a Windows Command Prompt command. Intel VT-x, AMD-V/SVM, and similar CPU virtualization features are controlled by the computer’s UEFI/BIOS firmware. CMD or PowerShell can help inspect Windows configuration, but if Task Manager reports virtualization as disabled, you generally need to restart into firmware settings.
Check virtualization before changing anything
- Press Ctrl+Shift+Esc to open Task Manager.
- Select Performance and then CPU.
- Look for the Virtualization status.
- If it says Enabled, the processor feature is already active; troubleshoot the virtualization application instead.
- If it says Disabled, identify the PC or motherboard model and consult its firmware instructions.
- Restart into UEFI/BIOS, enable Intel Virtualization Technology, AMD SVM, or the equivalent setting, save, and restart.
- Return to Task Manager and verify that Windows now reports virtualization as enabled.
CMD cannot replace the firmware setting
Commands such as systeminfo can report virtualization-related information, and Windows commands can enable operating-system features such as Hyper-V. Those actions are different from switching on the CPU virtualization capability in firmware.
Hyper-V is a separate Windows feature
After hardware virtualization is enabled, a supported Windows edition can enable Hyper-V through Windows Features, DISM, or PowerShell. Other software such as WSL 2 or third-party VM applications has its own requirements. Do not enable every virtualization component simply because one application needs CPU virtualization.
Change only the necessary firmware option
Do not disable Secure Boot or TPM, or change storage-controller settings, just to enable virtualization. Windows 10 is past standard support, so a virtualization workstation that qualifies should also be evaluated for Windows 11.
If the firmware option is missing, identify the exact processor and motherboard. Very old CPUs may lack the feature, while some managed or OEM systems hide or lock firmware settings.
On a work-managed computer, firmware settings may be protected by an administrator password or policy. Contact IT instead of attempting to bypass those controls.
Kermit Matthews is a freelance writer based in Philadelphia, Pennsylvania with more than a decade of experience writing technology guides. He has a Bachelor’s and Master’s degree in Computer Science and has spent much of his professional career in IT management.
He specializes in writing content about iPhones, Android devices, Microsoft Office, and many other popular applications and devices.