How to Turn Off Virtualization Based Security

If your PC feels heavier than it used to (stutters, extra overhead, weird app behavior) and you suspect Virtualization-based Security (VBS) got turned on, the fastest way to shut it down is usually straightforward. Start with Core Isolation → Memory Integrity, then uncheck Virtual Machine Platform. If you can’t find those toggles (or they don’t seem to stick), move on to Group Policy (Device Guard), then a registry change, and finally the bcdedit method to disable the hypervisor.

Below is a decision-tree style path—pick the first option that matches what you see on your screen.

---

Turn off Core Isolation (Memory Integrity) to disable VBS

This is usually the first step. Memory Integrity is part of Core Isolation, and turning it off is one of the main ways to disable VBS.

Method 1 (Settings UI)

1. Open Settings.
2. Go to Privacy & security.
3. Open Windows Security.
4. Click Device security.
5. Find Core isolation and click Core isolation details.
6. Turn off Memory integrity.
7. Restart your PC when prompted.

What to look for

After the reboot, VBS-related protections should stop. If you want to be sure you didn’t miss a second switch, continue to the next method (Virtual Machine Platform).

---

Disable Virtual Machine Platform in Windows Features

Even if you shut off Memory Integrity, Windows can still keep parts of VBS behavior if Virtual Machine Platform is still enabled. This is also a very common fix.

Method 2 (Windows Features UI)

1. Open Control Panel.
2. Go to Programs → Turn Windows features on or off.
3. Find Virtual Machine Platform.
4. Uncheck it.
5. Click OK and let Windows apply the change.
6. Restart when prompted.

Decision point

• If Memory Integrity is off and Virtual Machine Platform is unchecked, you’ve usually done the key work.
• If you can’t find one of these settings, or it doesn’t change what you expect, skip ahead to Group Policy.

---

Use Group Policy (Device Guard) when you can’t find the setting

Some systems (especially work/school PCs) hide or lock down these UI toggles. In that case, Group Policy may be what you need.

Method 3 (Local Group Policy / Device Guard)

Use this path:

Local Computer Policy → Computer Configuration → Administrative Templates → System → Device Guard

Look for a setting named “Turn On …” (it’s under Device Guard and is related to turning on VBS).

What to do:

1. Open Local Group Policy Editor (search for it from the Start menu).
2. Navigate to the Device Guard location above.
3. Find the Turn On … setting.
4. Set it to Disabled (or make sure the “turn on” behavior isn’t enabled).
5. Apply changes, then reboot.

If you don’t see it

That usually means the policy isn’t available in your edition/config, or it’s being controlled elsewhere. The next best path is the registry method.

---

Disable VBS via Registry (EnableVirtualizationBasedSecurity = 0)

If you want a more direct switch (or the UI/policy options aren’t available), you can set the registry value that controls VBS.

Method 4 (Registry edit)

1. Press Win + R, type regedit, and press Enter.
2. Go to:

HKEY_LOCAL_MACHINE\SystemCurrentControlSetControlDeviceGuard

1. Find the DWORD value named EnableVirtualizationBasedSecurity.
2. Set it to 0.
3. Restart your PC.

Quick sanity check

If the change doesn’t “take,” common reasons are restarting too late, not using the right registry location, or another setting overriding it.

---

Disable the hypervisor with bcdedit (hypervisorlaunchtype off)

This method is more aggressive. It tells Windows not to launch the hypervisor, using this command:

bcdedit /set hypervisorlaunchtype off

Method 5 (Command Prompt as admin)

1. Open Command Prompt as an administrator.
2. Run:

bcdedit /set hypervisorlaunchtype off

1. Restart your PC.

When to use this

Use this when you want to stop the hypervisor itself, especially if:

• VBS still seems active after Memory Integrity + Virtual Machine Platform are changed, or
• policy/registry changes aren’t producing the behavior you expected.

---

How to handle Windows 11 24H2 specifically (what to check)

On newer Windows builds (including Windows 11 24H2), people often run into two issues:

1. They turn off one control and forget the other.
2. A setting may look off, but a different VBS-related component still loads.

For Windows 11 24H2, your checklist is simple:

Check these in order

1. Memory Integrity under Core isolation details is turned off.
2. Virtual Machine Platform is unchecked under Turn Windows features on or off.
3. If you can’t change either one, use Device Guard Group Policy instead.
4. If you want extra certainty, confirm the registry value:

EnableVirtualizationBasedSecurity = 0

1. If it still won’t budge, use:

bcdedit /set hypervisorlaunchtype off

If you only change one of the first two toggles, Windows can still leave enough behind that the device feels “on.”

---

If VBS is enabled but it isn’t running: likely causes to investigate

You’ll sometimes see this in troubleshooting posts: “VBS is enabled, but it isn’t running.” The important point is that “enabled” and “actually running” don’t always line up, especially after changes or after Windows settles.

Since the specific reason isn’t provided in your facts, treat this as a verification checklist, not a guaranteed cause list.

What to check after your changes

Use the methods above as your verification steps:

1. Memory Integrity

Confirm it’s off in Core isolation details, not just that you clicked it once.

1. Virtual Machine Platform

Confirm it’s really unchecked in Turn Windows features on or off.

1. Registry value (if used)

Make sure EnableVirtualizationBasedSecurity is set to 0 in:

HKEY_LOCAL_MACHINE\SystemCurrentControlSetControlDeviceGuard

1. bcdedit change (if used)

If you used bcdedit /set hypervisorlaunchtype off, confirm you restarted after applying it.

A practical note about timing

If you changed settings and checked status before the reboot fully finished, you may see confusing “enabled but not running” behavior. If that’s your situation, do one clean reboot and check again.

---

Is it okay to turn off virtualization-based security? (tradeoffs to consider)

Turning off virtualization-based security is a personal choice, and it’s not a “free performance win” with no tradeoffs.

Here’s the plain way to think about it:

• VBS off can reduce some overhead and may help with performance annoyances you’re seeing.
• VBS on adds security protections. If you’re working with sensitive accounts/files, or you’re not sure you want to change this, turning it off may not be the best choice.

So the decision comes down to:

• If you’re disabling VBS because you’ve got a real performance problem you can point to, try it.
• If device security matters more to you than extra smoothness, you might leave it on.

And if you’re doing this because an app is misbehaving, disable it, test, and if things get worse from a security standpoint (or expected protection disappears), turn it back on.

---

Is VBS necessary? When you might leave it on

You may want to leave VBS enabled if:

• Your PC is mainly for work/school tasks where security matters more than raw speed.
• You don’t have an active performance issue anymore.
• You don’t want to keep adjusting security settings and prefer a “set it and forget it” approach.

You’re more likely to turn it off when:

• You’re chasing overhead or instability after VBS/Hyper-V was enabled.
• The device feels slow, and you’ve narrowed it down to these protections being on.

---

After you change it: confirm it worked (and keep track of your method)

Once you disable VBS, don’t stop at “I clicked the toggle.” Re-check the controls you changed:

• Memory Integrity should be off
• Virtual Machine Platform should be unchecked
• If you used registry: EnableVirtualizationBasedSecurity should be 0
• If you used bcdedit: you restarted after bcdedit /set hypervisorlaunchtype off

Then you can say, with confidence: “Method X worked on my Windows version.”