Categories About Us Contact Us Become a Member

Virtualization-Based Security Not Running on Windows 11 and 10: How to Fix It

Virtualization-based security (VBS) shows as Not enabled in msinfo32 when Windows has no hypervisor to use. Read the status first. Then enable virtualization in your BIOS and Memory integrity in Windows Security. Games that list VBS as a requirement need the row to pass.

By Neeraj Singh ~6 min Updated Nov 2026 Checked against Microsoft Learn
Error message
Virtualization-based security: Not enabled (System Information, msinfo32)
Summary

Virtualization-based security sits at the bottom of System Summary in msinfo32. Riot Support lists three values, namely Running, Enabled but not running and Not enabled. Enable Memory integrity in Windows Security when the row reads Not enabled. Enable Intel VT-x or AMD SVM Mode in the BIOS when it reads Enabled but not running. VBS also needs Secure Boot and TPM 2.0. Restart and open msinfo32 again to check the new status.

What a Failed VBS Status Means

VBS uses the Windows hypervisor to guard a protected area of memory. VBS needs a 64-bit processor with Intel VT-x or AMD-V.

The msinfo32 row shows which stage failed. Not enabled means no VBS feature is on. The second status means a feature is on and Windows could not start it.

Memory integrity is one VBS feature. Microsoft also calls it HVCI.

PowerShell shows the same status as VirtualizationBasedSecurityStatus. A 0 means not enabled and a 1 means enabled but stopped. A 2 means VBS is on and active.

Common Causes of a Failed VBS Status

Memory integrity is off in Windows Security.
Intel VT-x or AMD SVM Mode is off in the BIOS. The hypervisor cannot start.
Secure Boot is off. VBS needs it on.
TPM 2.0 is off or missing.
Your processor or firmware misses the VBS hardware list.
You use a virtual machine without nested support or Guest VSM.

✓ How to fix it

Method 1

Read the VBS Status in msinfo32

1Right-click Start and open an admin PowerShell or Terminal window. Microsoft says to start msinfo32 there.
msinfo32
2Scroll to the bottom of System Summary and find Virtualization-based security.
3Read the value. Running needs no fix. Not enabled points to Method 2. Enabled but not running points to Methods 3, 4 and 5. Riot Support describes these three values on its Riot Support memory integrity page.
4Check the Services Running row too. Riot Support says it should list Hypervisor enforced Code Integrity.
5For a second check, enter this command. Microsoft says a VirtualizationBasedSecurityStatus of 2 means VBS is enabled and active.
Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard
6The Microsoft Learn memory integrity page explains the SecurityServicesRunning field. A 2 there means Memory integrity is active.
Method 2

Enable Memory Integrity in Windows Security

1Open Windows Security and select Device security.
2Select Core isolation details and switch Memory integrity on. The Microsoft Learn memory integrity page lists this path.
3Restart your PC.
4If Windows lists incompatible drivers, update or remove the driver and try again. Our Memory Integrity error guide covers that error step by step.
5Open msinfo32 again and read the Virtualization-based security row.
Method 3

Enable Virtualization in the BIOS

1Open Settings, then System and Recovery. Next to Advanced startup, select Restart now.
2In the recovery menu, open Troubleshoot, then Advanced options and UEFI Firmware Settings. The Microsoft Support virtualization page lists this route.
3Enable Intel Virtualization Technology (VT-x) on an Intel PC or SVM Mode on an AMD PC. Riot Support lists Advanced and CPU Configuration as the place to look. Menu names change by maker.
4Save and exit. Your PC restarts.
5Open Task Manager, then Performance and CPU. Look for Virtualization. Riot Support says it should read Enabled.
6Our BIOS virtualization guide shows the setting on common boards.
Method 4

Check Secure Boot and TPM 2.0

1VBS needs Secure Boot and TPM 2.0. The Microsoft Learn VBS page has the full list.
2Open msinfo32 and read the Secure Boot State row. If it says Off, follow our How to Enable Secure Boot guide.
3Check your chip with our TPM 2.0 check guide. Enable fTPM or PTT in the BIOS if it is off.
4Open Device security in Windows Security. The Microsoft Support Device security page says Standard hardware security not supported means a missed requirement.
Method 5

Check Windows Features

1Search for Windows features and select Turn Windows features on or off.
2Select Virtual Machine Platform, as the Microsoft Support virtualization page says. Riot Support also lists Hyper-V and Windows Hypervisor Platform for this step.
3Windows Home cannot install the Hyper-V role. See the Microsoft Learn Hyper-V page.
4Select OK and restart your PC.
5Open msinfo32 once more. The Virtualization-based security row should read Running.

VBS status shows in msinfo32. Not enabled points to Memory integrity. A failed start points to virtualization in the BIOS plus Secure Boot and TPM 2.0. Restart after every change and read the row again.

Frequently asked questions

What does Virtualization-based security Not enabled mean?
Not enabled means no VBS feature is on. Enable Memory integrity in Windows Security, then restart.
What does the failed start status mean?
A VBS feature is on and Windows could not start it. Riot Support points to virtualization in the BIOS. Also check Secure Boot, TPM 2.0 and your processor.
How do I check the VBS status?
Open msinfo32 and read the Virtualization-based security row at the bottom of System Summary. The PowerShell command in Method 1 gives the same answer as a number.
Does VBS need Secure Boot and TPM 2.0?
Yes. Microsoft says Secure Boot must be on for VBS and lists TPM 2.0 as required.
Is VBS the same as Memory integrity?
No. VBS is the base feature and Memory integrity is one service that uses it.
Do games ask for VBS?
Some do. EA lists HVCI and VBS capable hardware for Battlefield 6. FACEIT asks for Memory integrity. The links below show the game side.
Does VBS work in a virtual machine?
Yes, with nested support or Guest VSM. Guest VSM is on by default for Generation 2 Hyper-V machines.

Still not working?

If the row still fails, check Memory Integrity error guide and How to Enable Virtualization in BIOS. Playing Battlefield 6 or FACEIT? Read Battlefield 6 system requirements and the FACEIT Memory Integrity fix. Still stuck? Send us your msinfo32 row and the steps you tried and we add the missing fix.

Was this fix helpful? Thanks for your feedback!