How to Disable Virtualization Based Security

If Windows feels a bit heavier than it should, or you’re troubleshooting a weird compatibility issue, turning off Virtualization-Based Security (VBS) can help. The two knobs that most people need are in Windows Security/Core Isolation and in a Hyper-V-related Windows feature. Work them in order: Memory Integrity first, then Virtual Machine Platform.

---

Turn off Memory Integrity (Core Isolation) to disable VBS

This is the most common switch people use to reduce VBS.

1. Open Settings.
2. Go to Privacy & security.
3. Click Windows Security.
4. Choose Device security.
5. Find Core isolation.
6. Select Core isolation details.
7. Turn Memory integrity Off.

Once you flip it off, Windows may ask you to restart. If it does, do it. If it doesn’t, you should still restart after you finish the rest of the steps, so everything re-loads cleanly.

---

Disable Virtual Machine Platform (Hyper-V component) to reduce VBS

Next, you’ll remove/uncheck a Windows feature tied to virtualization. This is one of the other main steps people use to stop VBS from being active.

1. Press Win + R.
2. Type: `optionalfeatures`
3. Press Enter.
4. In the list, look for Virtual Machine Platform.
5. Uncheck it.
6. Click OK.
7. Restart Windows when prompted.

If you don’t want to use the optional features window, you can also find the same setting through Windows features search, but the `optionalfeatures` method is the most direct.

Order matters. Do Memory Integrity first, then disable Virtual Machine Platform. If you do both, restart once at the end (or after each prompt if Windows insists).

---

Windows 11 vs Windows 10: where the settings live

The steps above are the “exact paths” people usually follow, but Windows 10 and 11 can label things a little differently.

Where to look in Windows 11

• Settings → Privacy & security → Windows Security → Device security → Core isolation
• Then open Core isolation details and switch Memory integrity off.

Where to look in Windows 10

• Settings → Update & Security → Windows Security
• Then go to Device security and Core isolation to get to Core isolation details.

The feature toggle is the same for both

• `optionalfeatures` → Virtual Machine Platform → uncheck → OK → restart

If you’ve ever searched for “VBS” directly and got nothing useful, that’s normal. Windows often hides the control behind Memory integrity and Virtual Machine Platform instead.

---

Windows 11 24H2: what to check if VBS won’t fully turn off

On newer builds, you might do the steps and still see something that looks like VBS didn’t fully stop. The research that’s circulating around this topic suggests extra friction on builds like Windows 11 24H2—people report registry or security-core setting changes when the normal UI path doesn’t seem to fully stick.

Before you go down that rabbit hole, check the basics carefully:

Re-check both toggles (don’t trust just one)

After rebooting, confirm:

• Memory integrity is still Off under Core isolation details
• Virtual Machine Platform is still unchecked under Windows optional features

It’s easy for one setting to change and the other to look “unchanged” after updates or pending restarts.

Make sure you reboot after everything

A common reason people think VBS is still on is that Windows hasn’t fully restarted into the new configuration yet. If you only half-done it (turned one toggle off but didn’t reboot), the system can still behave like VBS is active.

If it still looks on after both toggles

If you’ve confirmed both settings are off and you’ve restarted, then you’re in the “VBS won’t fully turn off” zone. At that point, what you’ll usually see from community troubleshooting is that people add build-specific changes (like registry/security core adjustments) because Windows behavior can differ by release.

This guide focuses on the two main, settings-based steps plus a policy fallback below (in case the normal option isn’t visible). But if your 24H2 system simply keeps reporting VBS as enabled, you’ll likely need those extra, build-specific tweaks after you’ve proven Memory Integrity + Virtual Machine Platform are actually off.

---

If you can’t find the VBS option: use Local Computer Policy (Administrative Templates)

Sometimes Windows just won’t show you what you expect in the UI. When that happens, the fallback path is Local Computer Policy through Administrative Templates.

Here’s the route people use:

1. Press Win + R
2. Type: `gpedit.msc`
3. Press Enter
4. Go to: Computer Configuration → Administrative Templates
5. Look for the policy setting related to Virtualization-based security / VBS there
6. Apply the policy to turn it off
7. Restart the PC

A couple of notes:

• This method is specifically called out in troubleshooting threads for cases where the normal “Core isolation / VBS” options are missing or confusing.
• If you don’t have gpedit.msc (some Windows editions don’t include it), you may need an edition-specific workaround—but the first step is still to try the Settings/Core isolation + Virtual Machine Platform toggles above.

---

Virtualization-based security disabled but still running: what to verify after changes

This is the confusing one, and it shows up a lot in search. You turn the toggles off, but a check somewhere still says VBS is “running” (or “enabled”).

Here’s a simple verification checklist that lines up with the two switches you changed.

1) Confirm Memory Integrity is actually off

Go back to:

• Settings → Windows Security → Device security → Core isolation details
• Make sure Memory integrity is Off

If it flips back on after a reboot, you haven’t fully disabled it yet.

2) Confirm Virtual Machine Platform is actually unchecked

Re-open:

• `optionalfeatures`
• Verify Virtual Machine Platform is not checked

If Windows re-checks it, your system may be reapplying a feature state after an update or a restart you didn’t complete fully. (Usually this comes down to either missing a restart or an update reconfiguring the system.)

3) Reboot after the final change

Do not stop after you change one toggle. Make sure you reboot after both changes are done. If you only rebooted mid-way, finish everything and reboot again.

4) Re-check after any Windows updates

Updates can change security features. If you changed VBS right before an update (or right after), re-verify both toggles once the update finishes.

That’s the key idea: if you see “still running,” treat it like a sign to re-verify what Windows currently has active. In most cases, the fix is still the same two toggles plus a clean restart cycle.

---

Is it a good idea to disable VBS in Windows 11? (tradeoffs to consider)

Disabling VBS can make sense when you’re chasing performance or troubleshooting a driver/app issue. That said, VBS is part of Windows’ security setup, and turning it off can change how your system protects certain things.

So before you commit, think about why you’re turning it off:

• If your goal is performance: you’re trading some security features for a leaner setup.
• If your goal is troubleshooting: disabling VBS can help you figure out whether VBS-related behavior is the cause of an app or compatibility problem.
• If your goal is “because I don’t use it”: you still might not want to remove it unless you have a reason. Security features aren’t usually “free,” but they’re there for a reason.

If you’re doing this for stability or compatibility testing, consider re-enabling it later once you’ve confirmed the issue is gone.

---

Should I enable virtualization-based security? (when to leave it on)

If you don’t have a specific performance issue or compatibility problem, leaving VBS on is often the safer choice. It’s one of those settings you typically turn off only when you have a clear reason.

You should strongly consider keeping it enabled if:

• You’re not sure what change caused your issue
• You want the extra security hardening Windows provides by default
• You’re not actively troubleshooting a specific app/game/driver

And if you did turn it off to test something, it’s reasonable to turn it back on after the problem is solved—especially on machines that handle work, logins, or sensitive files.

---

After you follow the steps (Memory Integrity off, then Virtual Machine Platform unchecked), verify the result and bookmark this guide so you can come back the next time a Windows update changes how things behave.