How to Fix FACEIT "Virtualization-Based Security Required" – 2026

6 min to read

How to Fix FACEIT "Virtualization-Based Security Required" – 2026

"Virtualization-based security required" (or "Hypervisor launch type is off") means FACEIT needs VBS running and it is not. Turn on CPU virtualization in the BIOS if it is off, let the Windows hypervisor start with one bcdedit command, and turn on Memory integrity. After a restart, msinfo32 shows VBS Running and FACEIT lets you in.

FACEIT: Virtualization-Based Security Required

Virtualization-based security required
FACEIT Anti-Cheat: FACEIT: Virtualization-Based Security Required

What causes FACEIT: Virtualization-Based Security Required

VBS uses the CPU's virtualization to protect Windows. It does not run when:

  • SVM (AMD) or VT-x (Intel) is off in the BIOS,
  • the Windows hypervisor is blocked with hypervisorlaunchtype off, which many FPS tweak tools do,
  • neither Memory integrity nor VBS is turned on in Windows.

How to fix FACEIT: Virtualization-Based Security Required in Windows

1

Used RIP Tweaks before? Turn our Windows tweaks off first

If you turned on Disable Windows Hypervisor, Windows 10 Optimization or Windows 11 Optimization in RIP Tweaks, turn them off in the app and restart. They switch off the Windows hypervisor and Memory integrity, which this check needs. Turning them off puts back the settings your PC had.
2

Check that virtualization is on

Open Task Manager > Performance > CPU. Under the graph, Virtualization must say Enabled. If it says Disabled, turn it on in the BIOS (steps below).
3

Let the Windows hypervisor start

Memory integrity and VBS run on the Windows hypervisor. If a tweak tool switched it off, Memory integrity stays off even when the switch says on. In Terminal (Admin) run bcdedit /set hypervisorlaunchtype auto and restart.
4

Turn on Memory integrity

Open Windows Security > Device security > Core isolation details and switch Memory integrity on, then restart. If Windows refuses and shows Review incompatible drivers, click it: it lists the driver files in the way (often old RGB, fan, overclocking or anti-virus tools). Update or uninstall the app that installed each one, then try again. Never delete driver files by hand.
5

Check that VBS is running

Open msinfo32 again. Virtualization-based security should say Running. If it says Enabled but not running, virtualization is off in the BIOS (SVM on AMD, Intel Virtualization Technology on Intel) or the hypervisor is not allowed to start (step above). Turning on Memory integrity turns VBS on by itself.

How to fix it in the BIOS

This part happens in your PC's firmware setup (the BIOS), so open this page on your phone first. Menu names change a little between BIOS versions: if a path below does not match, look for the words in bold. Only if Task Manager shows Virtualization: Disabled.

1

Restart into the BIOS

Open Settings > System > Recovery, click Restart now next to Advanced startup, then Troubleshoot > Advanced options > UEFI Firmware Settings > Restart. Or run shutdown /r /fw /t 0 in Terminal (Admin). You can also press Del right after switching the PC on (desktops; F2 on many laptops and some ASRock and MSI boards).
2

Change these settings

  • Turn on CPU virtualization: SVM Mode on AMD, Intel Virtualization Technology (VT-x) on Intel.

Where to find them on your board:

ASUS

Press F7 for Advanced Mode.
CPU virtualization (SVM / VT-x): Advanced > CPU Configuration > SVM Mode (AMD) or Intel Virtualization Technology (Intel)

MSI

Press F7 for Advanced mode.
CPU virtualization (SVM / VT-x): OC > Advanced CPU Configuration > SVM Mode (AMD) or Intel Virtualization Tech (Intel)

Gigabyte (AORUS)

Press F2 to switch to Advanced Mode.
CPU virtualization (SVM / VT-x): Tweaker > Advanced CPU Settings > SVM Mode (AMD) or Intel Virtualization Technology (Intel)

ASRock

Press F6 to switch to Advanced Mode.
CPU virtualization (SVM / VT-x): Advanced > CPU Configuration > SVM Mode (AMD) or Intel Virtualization Technology (Intel)

Laptops and prebuilt PCs

Dell: F2, Boot Configuration > Secure Boot, Security > TPM 2.0 Security On, Virtualization Support > VT / VT-d.
HP: Esc then F10, Advanced > Secure Boot Configuration, Security > TPM Embedded Security, Advanced > System Options > Virtualization Technology.
Lenovo: F1 on ThinkPad, F2 or the Novo button on IdeaPad and Legion, Security > Secure Boot, Security > Security Chip, Security > Virtualization.
ASUS: F2, Security > Secure Boot Control, Advanced > Trusted Computing.
Acer: F2, set a Supervisor password first or Secure Boot stays greyed out, then Boot > Secure Boot and Security > TPM.
MSI: Del, Security > Secure Boot, Advanced > Trusted Computing.
Gigabyte / AORUS: F2, Security > Secure Boot, Advanced > Trusted Computing.
3

Save and restart

Press F10 and confirm with Yes. Windows starts normally.

Fix it in one click with RIP Tweaks (free)

RIP Tweaks 6.9.3 has a free anti-cheat error fixer. Open Fixes, then Anti-cheat errors, and paste FACEIT: Virtualization-Based Security Required or pick your game. The app first checks what your PC has right now (for example Secure Boot: Off, TPM: On) and shows only the steps still missing.

The anti-cheat error fixer in RIP Tweaks

It fixes the Windows side itself

Memory integrity, the Windows hypervisor, test signing, Control Flow Guard, the vulnerable driver blocklist and services that an optimizer switched off: the app changes them for you, saves what it changed first, and can put every change back.

It takes you into the BIOS with the right card

What only the BIOS can change (TPM, Secure Boot, CSM, virtualization, IOMMU), the app shows for your exact board maker, suspends BitLocker for you and restarts straight into the BIOS. A QR code opens this page on your phone.

It checks again after the restart

Back in Windows, the fixer checks again and shows green, or exactly what is still missing.

The fixer is free in every plan, also without an account. Download RIP Tweaks (free)

Check that it worked

msinfo32: Virtualization-based security says Running. Restart the FACEIT anti-cheat.

Frequently asked questions

What does "Hypervisor launch type is off" mean?

Windows was told not to start its hypervisor (hypervisorlaunchtype off), usually by a tweak tool. Run bcdedit /set hypervisorlaunchtype auto in Terminal (Admin) and restart.

Who needs VBS on FACEIT?

FACEIT asks for it on higher-ELO accounts and rolls it out in waves. If you see this message, it applies to your account now.

Does Memory integrity lower FPS?

It can cost a little performance in some games, and Microsoft says so itself. On recent CPUs the difference is usually small. When an anti-cheat requires it, there is no way around it: it has to be on to play.

Memory integrity will not turn on. Why?

Almost always a driver Windows does not allow under Memory integrity. Click Review incompatible drivers in Core isolation, update or remove the app behind each driver, and restart. If the switch turns itself off again, the Windows hypervisor is blocked (run bcdedit /set hypervisorlaunchtype auto) or virtualization is off in the BIOS.

Can changing these settings get me banned?

No. These are the anti-cheat's own requirements, and the publisher asks you to change them. Bans come from cheats and tools that tamper with the game, never from turning on Windows security features.

Sources

All anti-cheat errors: Anti-Cheat Error Fixes. Related: How to Fix FACEIT "Please Enable Memory Integrity to Continue" – 2026 and How to Fix FACEIT "Please Enable IOMMU" – 2026.