How to Safely Disable Security Virtualization in Minutes

What security virtualization actually means

When Microsoft talks about security virtualization (often called Virtualization‑Based Security or VBS), it’s describing a set of hypervisor‑driven protections that isolate critical OS components. By running parts of the kernel inside a lightweight virtual machine, the system can enforce stricter integrity checks and protect against credential theft. The idea is sound, but the extra layer can cause compatibility hiccups with older drivers, certain gaming titles, or specialized enterprise software.

If you’ve hit a “cannot install” error, experience performance drops, or simply prefer a leaner setup, you might consider disabling security virtualization. The process is reversible, but it’s worth understanding the trade‑offs before you flip any switches.

Why you might want to disable it

Disabling security virtualization isn’t a decision to take lightly. The feature adds a hardening layer that stops many low‑level attacks, especially those targeting memory‑based exploits. However, real‑world scenarios where users choose to turn it off include:

• Legacy hardware or drivers that refuse to load under VBS.
• High‑performance gaming or VR applications that suffer from added latency.
• Corporate environments where a specific security suite already enforces isolation, making VBS redundant.
• Testing or development machines where frequent reboots and configuration changes are part of the workflow.

In each case, the benefit of a smoother experience must be weighed against the loss of an extra security barrier.

Preparation: What you need before you start

Before you attempt to disable security virtualization, gather the following:

• A local administrator account – the steps require elevated privileges.
• Backup of your system or at least a restore point; Windows can revert changes, but a snapshot adds peace of mind.
• Knowledge of your Windows edition – VBS is only available on Windows 10/11 Pro, Enterprise, and Education.
• Any documentation from your organization’s IT policy, in case the change conflicts with mandated standards.

With those items checked off, you’re ready to move on.

Step‑by‑step guide to turn off security virtualization

The most reliable method combines the Group Policy editor, Windows Features, and a quick PowerShell check. Follow the steps in order; skipping one can leave VBS partially enabled, which may still affect performance.

1. Disable the hypervisor launch

Open an elevated Command Prompt (right‑click Start → Windows Terminal (Admin)) and type:

bcdedit /set hypervisorlaunchtype off

Press Enter. This command tells the bootloader not to start the hypervisor that underpins VBS. You’ll need to restart for the change to take effect.

2. Turn off Core Isolation (Memory Integrity)

After the reboot, navigate to Settings → Privacy & Security → Windows Security → Device security. Under Core isolation, click Core isolation details and toggle Memory integrity to Off. Windows may prompt you to restart again.

3. Use Group Policy to disable VBS components

Press Win+R, type gpedit.msc, and press Enter. Follow this path:

• Computer Configuration → Administrative Templates → System → Device Guard
• Double‑click Turn on Virtualization Based Security.
• Select Disabled, click Apply, then OK.

This ensures that policies won’t automatically re‑enable VBS on the next policy refresh.

4. Uninstall the “Windows Hypervisor Platform” feature (optional)

If you want to be thorough, open Control Panel → Programs → Turn Windows features on or off. Scroll down, uncheck Windows Hypervisor Platform, and confirm. A restart will finalize the removal.

5. Verify the status with PowerShell

Open PowerShell as admin and run:

Get-CimInstance -ClassName Win32_DeviceGuard

If the SecurityServicesRunning array is empty, VBS is no longer active.

After you’ve disabled it: What to check next

Disabling security virtualization can surface a few side effects. Run these quick checks to confirm your system is stable:

• Open Event Viewer (search “eventvwr”) and look for any new error entries under System or Application that reference “hypervisor” or “VBS”.
• Launch the apps or games that previously complained. If they now start without error, you’ve solved the compatibility issue.
• Run sfc /scannow from an elevated Command Prompt to ensure no system files were corrupted during the process.
• Consider re‑enabling the feature later if you notice a rise in suspicious activity; the steps are reversible.

Common pitfalls and how to avoid them

Even with careful follow‑through, some users stumble into these traps:

• Forgot to reboot. The hypervisor launch flag only takes effect at boot time, so skipping the restart leaves VBS partially active.
• Group Policy overrides. In a domain‑joined environment, a central policy may re‑enable VBS on the next refresh. Ask your IT admin to adjust the setting or create an exclusion.
• Partial feature removal. Unchecking “Windows Hypervisor Platform” without also disabling the boot flag can cause Windows to fall back to a minimal hypervisor mode, which still consumes resources.

Double‑checking each step and documenting your changes will save you a lot of troubleshooting later.

Frequently asked questions

Is it safe to turn off security virtualization on a personal PC?

Generally, yes—especially if you’re the only user and you keep your system patched. You’ll lose the extra memory‑integrity shield, so staying vigilant with antivirus software and regular updates becomes more important.

Can I re‑enable VBS without reinstalling Windows?

Absolutely. Reverse the steps: set bcdedit /set hypervisorlaunchtype auto, turn Memory integrity back on, enable the Group Policy setting, and re‑check the Windows Hypervisor Platform feature. A couple of restarts will bring VBS back.

Will disabling security virtualization improve game performance?

Many gamers report a modest FPS bump—often 2–5%—once VBS is off, because the system no longer has to switch into the isolated VM for certain memory checks. The exact gain depends on your hardware and the game's engine.

Do enterprise security standards usually forbid disabling VBS?

In regulated industries (finance, healthcare, etc.) compliance frameworks often require the highest possible baseline protection, which includes VBS. Always check your organization’s policy before making changes on a work machine.