How To Turn Off Vbs In Windows: Step-by-step Guide

Virtualization-based security (VBS) creates an isolated, secure region of memory in Windows to protect critical system components from malware. While Microsoft enables this feature by default on modern hardware to boost system defense, it can introduce performance overhead—particularly in PC gaming and resource-intensive applications. If you need to disable VBS to reclaim system performance or troubleshoot virtualization conflicts, you can do so through Windows Security, the Registry Editor, or Group Policy.

Disabling VBS removes the hypervisor-enforced layer protecting core operating system processes. Before making changes, you should weigh the security trade-offs against the performance gains, especially on corporate devices or shared computers where enhanced protection matters.

What is Virtualization-Based Security?

VBS uses hardware virtualization and the Windows Hypervisor to create an isolated virtual environment. Inside this secure container runs Device Guard, Credential Guard, and the Hypervisor-Protected Code Integrity (HVCI) service. HVCI ensures that kernel-mode drivers and system binaries are properly signed and trustworthy before they load.

When VBS runs, it prevents unauthorized software from injecting code into the Windows kernel. However, running an active hypervisor layer continuously consumes CPU cycles and memory. Gamers and content creators often notice frame rate drops, input latency, or stuttering when VBS and memory integrity are active. Turning it off drops this virtualization tax, though it leaves your system relying purely on traditional Windows Defender protections.

Checking Your Current VBS Status

Before making any modifications, confirm whether VBS is currently running on your system. Windows provides a built-in tool specifically designed to inspect system security configurations.

1. Press the Windows Key, type System Information, and press Enter.
2. Look at the right-hand pane and scroll down near the bottom to find Virtualization-based security.
3. Check its status value. If it says Running, VBS is active. If it says Not enabled, no further action is required.

You can also check via PowerShell for a more direct readout. Open PowerShell as an administrator and run the command Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard. Review the output fields to see if virtualization security services are running.

Method 1: Disabling VBS via Windows Security

The most user-friendly approach involves turning off memory integrity directly within the Windows Security application. This is often enough to disable the core performance-impacting components of VBS without touching deep system registries.

1. Open the Start menu, type Windows Security, and open the app.
2. Click on Device security in the left sidebar.
3. Under the Core isolation section, click the Core isolation details link.
4. Locate the toggle switch for Memory integrity (also known as hypervisor-protected code integrity).
5. Switch the toggle to Off.
6. Restart your computer when prompted to apply the changes.

If the memory integrity toggle is greyed out or controlled by your organization, you may be bound by group policies, or your processor might lack hardware virtualization support in the BIOS/UEFI.

Method 2: Disabling VBS via Registry Editor

If the graphical interface fails to disable VBS completely, or if core virtualization security services remain active, you can modify the Windows Registry.

1. Press the Windows Key + R, type regedit, and press Enter to open the Registry Editor.
2. Navigate to the following path in the left address bar: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard
3. Look for a DWORD value named EnableVirtualizationBasedSecurity on the right side.
4. Double-click the value and change its data from 1 to 0.
5. Next, navigate to the related folder path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
6. Locate the DWORD value named RunAsPPL. If it exists, double-click it and set its value to 0. If you want to configure core isolation settings explicitly, check for LsaCfgFlags and set that to 0 as well.
7. Close the Registry Editor and restart your computer.

Modifying the registry incorrectly can cause system instability. Always ensure you follow the exact path and only change the specified values. You can learn more about managing system configurations safely through official documentation on the Microsoft Learn platform.

Method 3: Disabling VBS via Group Policy

For users running Windows Pro, Enterprise, or Education editions, the Local Group Policy Editor provides a centralized switch to turn off VBS. Home edition users will need to rely on the Registry method instead.

1. Press the Windows Key + R, type gpedit.msc, and press Enter.
2. In the left window pane, expand Computer Configuration, then Administrative Templates, then System, and finally click on Device Guard.
3. In the right pane, double-click the policy named Turn On Virtualization Based Security.
4. Select the Disabled radio button in the upper left corner of the configuration window.
5. Click Apply and then OK.
6. Reboot your machine to finalize the configuration change.

Disabling Hypervisor-Level Features in BIOS/UEFI

Sometimes VBS remains tied to hardware-level virtualization extensions managed by your motherboard's firmware. If Windows settings and registry tweaks do not fully deactivate the feature, you may need to adjust your BIOS settings.

1. Restart your PC and repeatedly press your manufacturer's designated BIOS key (commonly F2, F12, Del, or Esc) during boot.
2. Locate the CPU or Advanced settings tab.
3. Look for settings related to Intel Virtualization Technology (VT-x), AMD-V, or SVM Mode.
4. While disabling these entirely will stop VBS, note that it will also disable Docker, Windows Subsystem for Linux (WSL), and virtual machines. If you only want to stop VBS without losing virtual machine support, leave CPU virtualization enabled and rely on the Windows-level registry or security toggles instead.
5. Save changes and exit the BIOS.

For detailed hardware specifications and processor virtualization support guidelines, consult the official Intel ARK database or the AMD processors guide.

Common Mistakes When Disabling VBS

Many users attempt to turn off VBS and run into roadblocks because they miss crucial operational details. Avoid these frequent pitfalls:

• Forgetting to reboot: VBS runs at the kernel level and requires a complete system restart to release hypervisor locks. A simple sign-out or sleep cycle will not work.
• Overlooking dependent services: Disabling memory integrity often requires turning off related isolation features first. If a policy is locked by an enterprise profile, local tweaks will automatically revert upon reboot.
• Confusing virtualization with VBS: Disabling SVM or VT-x in the BIOS stops all virtual machines from running. If you only want to stop VBS for gaming frames, keep hardware virtualization enabled and disable memory integrity inside Windows instead.

Frequently Asked Questions

Will turning off VBS damage my computer?

No, disabling VBS will not harm your hardware or operating system files. It simply removes an extra software security layer that isolates core processes from potential malware attacks.

Why is my memory integrity toggle greyed out?

A greyed-out toggle usually means a Group Policy is enforcing the setting, your CPU lacks necessary hardware features, or third-party virtualization software like a hypervisor is currently active on the machine.

Does turning off VBS improve gaming performance?

Yes, on systems with mid-range or high-end graphics cards, disabling VBS and memory integrity can reduce CPU overhead, eliminate micro-stutters, and increase average frame rates in demanding video games.

Can I re-enable VBS later if I change my mind?

Absolutely. You can reverse any of these steps by turning memory integrity back on in Windows Security or changing your registry values back to their default states and rebooting.