Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Yes—turning off CPU virtualization in UEFI/BIOS is generally safe and reversible. It does not normally delete files or damage your processor. But it can stop virtual machines, WSL2, Windows Sandbox, some Android emulators, and security features such as Memory Integrity from working. If you are troubleshooting a specific app, first identify whether the issue is actually Hyper-V, a Windows security feature, or the app’s own settings; disabling the narrowest component is usually the better fix.
First, which “virtualization” do you mean?
Windows troubleshooting often uses “virtualization” to describe several different things. They are related, but not interchangeable. The firmware switch discussed here is usually called Intel Virtualization Technology, VT-x, or VMX on Intel systems, and SVM Mode or AMD-V on AMD systems. It gives hypervisors access to processor virtualization extensions; it is not virtual memory, CPU multithreading, Secure Boot, or TPM.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Microsoft Windows 11 (USB) | $128.28 | Buy on Amazon |
| 2 |
|
Virtualization Essentials | $30.46 | Buy on Amazon |
| 3 |
|
Hyper-V & Virtualization Mastery: Windows Server 2025 Guide (Windows Server 2025 Mastery Guide... | $5.99 | Buy on Amazon |
| 4 |
|
Virtualization Essentials, 2nd Edition | $15.00 | Buy on Amazon |
| 5 |
|
Hands-On Microsoft Windows Server 2019 (MindTap Course List) | $26.09 | Buy on Amazon |
| Layer | What it means | Typical consequence of disabling it |
|---|---|---|
| CPU virtualization in UEFI/BIOS | Processor support used by hypervisors and virtual machines. | Most hardware-accelerated VMs and other dependent features cannot use the CPU extensions. |
| Windows hypervisor and optional features | Hyper-V and components such as Virtual Machine Platform, Windows Hypervisor Platform, Sandbox, and WSL. | The specific Windows virtualization workflows relying on the disabled component may stop working. |
| Virtualization-based security (VBS) | Windows uses the hypervisor to isolate certain security functions, including Memory Integrity. | Turning off the relevant protection can reduce security hardening. |
| A VM’s nested-virtualization setting | Allows a guest virtual machine to run a hypervisor or virtualization-dependent workload of its own. | Nested workloads may fail, even though virtualization remains enabled on the physical PC. |
Microsoft’s virtualization guide explains how to reach firmware settings and notes that the exact menus vary by manufacturer.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What happens if you turn off CPU virtualization?
It does not normally harm the computer or erase data
Disabling the firmware option is a configuration change, not a permanent alteration to the processor. Re-enabling the same option restores the capability. It does not normally uninstall Windows or erase personal files. However, firmware interfaces differ, and changing the wrong setting can cause boot or access problems. Change only the option you intended to change. Take extra care on encrypted or company-managed devices.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
Some virtualization-dependent features may stop working
Depending on your Windows version, settings, and applications, disabling hardware virtualization may make these unavailable or cause errors:
- Hyper-V virtual machines, and many VMware Workstation or VirtualBox workloads.
- WSL2, which uses virtualization-related Windows components.
- Windows Sandbox and some Android emulators.
- Nested virtualization inside a VM.
- VBS-dependent protections such as Memory Integrity, and potentially Credential Guard on managed systems.
Some virtualization software can run with emulation or through a compatibility mode, but it may be limited or slower. Microsoft documents that third-party virtualization apps can fail or use slower emulation when Windows hypervisor components are involved. Its WSL FAQ also notes that newer VMware and VirtualBox versions have added Hyper-V compatibility; it is no longer accurate to say they can never coexist. Results still depend on software versions and workloads.
It does not guarantee faster Windows or better gaming
There is no general promise of higher FPS, longer battery life, lower temperatures, or faster everyday apps from switching off the firmware feature. If a particular VM is slowed or blocked because it is sharing the Windows hypervisor, changing the relevant Windows configuration may help that workload. That is different from a system-wide speed boost. Performance varies with the hardware, Windows and app versions, security configuration, and workload.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Rank #2
Does disabling virtualization improve security?
Not as a general rule. A narrow threat model might value disabling a hardware feature that is not used, but that is rarely the main security choice for a typical home PC. The more immediate concern is that turning off virtualization can prevent VBS-based protections from operating.
Microsoft describes VBS as an isolated environment for security solutions. Memory Integrity, also called Hypervisor-protected Code Integrity (HVCI), uses that environment to help protect kernel-mode code and limit certain memory-exploitation techniques. Disabling virtualization does not automatically make a PC insecure, but losing Memory Integrity or another managed protection can reduce hardening. Security also depends on updates, Secure Boot, TPM, account protection, antivirus, and other configuration choices. See Microsoft’s VBS and Memory Integrity overview.
If you use a work or school computer, do not turn off virtualization or a security feature without approval: Credential Guard and VBS may be required or policy-controlled. On a personal PC, a temporary change for diagnosis may be reasonable, but restore protections you rely on afterward.
Choose the least disruptive fix
| Your situation | Best first move |
|---|---|
| VMware or VirtualBox will not start | Check whether Hyper-V or VBS is active, update the VM software, and consult its current compatibility guidance before changing firmware virtualization. |
| You need WSL2 or Windows Sandbox | Keep hardware virtualization enabled and retain the Windows components those features require. |
| An Android emulator reports an acceleration or hypervisor error | Check the emulator’s supported hypervisor mode and update it. Do not assume the firmware switch is the cause. |
| A game or anti-cheat reports a virtualization conflict | Identify whether it objects to Hyper-V, VBS, or Memory Integrity. Disabling all virtualization may remove protections without addressing the specific conflict. |
| You are testing nested virtualization | Keep virtualization enabled on the physical host and configure nested virtualization for the VM, if the host hypervisor supports it. |
| You do not use VMs, WSL2, Sandbox, or emulators | There is usually no need to change the setting unless you have a specific troubleshooting reason. |
Check whether the Windows hypervisor is running
- Press the Windows key, search for
msinfo32.exe, and open System Information. - In the details pane, look for:
A hypervisor has been detected. Features required for Hyper-V will not be displayed.
That message means the Windows hypervisor is running; it does not mean that the firmware setting itself is disabled. Microsoft documents this check in its troubleshooting guidance for virtualization apps and Hyper-V.
Try a Windows-level change before changing UEFI
If a third-party VM is having trouble, disabling the Hyper-V hypervisor may be a narrower test than turning off CPU virtualization. Microsoft documents the following options. They require an administrator account and a restart may be needed:
Windows Features: Open Control Panel → Programs and Features → Turn Windows features on or off. Expand Hyper-V, then Hyper-V Platform, and clear Hyper-V Hypervisor if that option is present.
Rank #4
Administrative PowerShell:
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-HypervisorAdministrative Command Prompt:
DISM /Online /Disable-Feature /FeatureName:Microsoft-Hyper-V-HypervisorThese approaches target the Hyper-V hypervisor, not every Windows feature that may use virtualization. Turning it off may not resolve a conflict if VBS, Memory Integrity, Credential Guard, or another hypervisor component remains active. Conversely, disabling multiple Windows features can break WSL2, Sandbox, or other workflows. Change only what your specific test requires and note the original settings so you can restore them.
If a driver is flagged by Memory Integrity, first look for an updated compatible driver rather than disabling all virtualization-based security. When you genuinely need to test with Memory Integrity off, the usual path is Windows Security → Device security → Core isolation details → Memory integrity. Turn it off only if the control is available and you understand the security trade-off; restart as prompted. The control may be unavailable or managed by policy.
Free tools Windows power users keep installed
One-click scans. No signup required.
Turn off CPU virtualization in UEFI/BIOS
Use this only when a Windows-level or application-level change is not sufficient, or when a specific application or policy explicitly requires it. On Windows 10/11 systems that expose the UEFI option through Recovery:
Best Value
- Save your work and close applications.
- Open Settings → System → Recovery. Under Advanced startup, select Restart now.
- Choose Troubleshoot → Advanced options → UEFI Firmware Settings → Restart. If that choice is absent, use the computer or motherboard manufacturer’s instructions for entering firmware setup.
- In firmware, look in processor, CPU, security, or advanced settings for Intel Virtualization Technology, VT-x, or VMX on Intel systems, or SVM Mode/AMD-V on AMD systems. Set only that option to Disabled.
- Save changes and exit. The PC will restart.
Names and menu locations are not standardized, and the option can be hidden, locked by an administrator, unavailable on a particular processor, or reset by a firmware update. Check the official support information for your exact PC or motherboard model. Do not change Secure Boot, TPM, boot mode, or unrelated firmware options as a workaround.
Restore the setting and recover from problems
To re-enable CPU virtualization, return to the same UEFI/BIOS option, set it to Enabled, save, and restart. If you also changed Windows features, restore the ones your workflow needs—such as Hyper-V, Virtual Machine Platform, Windows Subsystem for Linux, Windows Sandbox, or Memory Integrity—and restart when prompted.
- A VM still fails: Note its exact error, check
msinfo32.exe, review Windows Features and Windows Security → Device security → Core isolation, restart fully, and update the VM software. A remaining policy or nested-virtualization requirement may be involved. - WSL2 stops working: Re-enable firmware virtualization and the Windows components WSL2 requires, including Virtual Machine Platform and the WSL feature. Check the current WSL documentation for your configuration.
- The firmware setting is missing: Confirm the exact computer or motherboard model and consult its manufacturer documentation. Do not use firmware updates except through the manufacturer’s official process.
- Windows will not boot after a firmware change: Return to firmware setup and restore only the virtualization option if you can. Do not reset all firmware settings casually; a broad reset can change unrelated boot or security settings. If BitLocker recovery appears, use your legitimate recovery key. Contact IT for a managed PC.
Changing CPU virtualization alone is not expected to delete files or normally prevent Windows from starting. Boot trouble is more likely if another firmware setting was changed at the same time.
Bottom line
Disabling virtualization is generally safe for the hardware and reversible, but it can remove functionality and security protections. Keep it enabled by default. If you have a VM conflict, first determine whether Hyper-V, VBS, Memory Integrity, or an application setting is the actual cause—and change the narrowest layer that solves it.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
