GRIND
FACEIT troubleshooting

Fix every FACEIT Anti-Cheat error.

Secure Boot, TPM 2.0, IOMMU, virtualization, Memory Integrity and the fatal error codes — each with the exact steps. Got your PC running? Tune it with the CS2 Optimizer.

FACEIT security requirements — the timeline

  1. Apr 2025 IOMMU + VBS rollout begins (limited) — gradually required for ~60% of players.
  2. Aug 2025 IOMMU / Memory Integrity becomes mandatory for everyone above 3000 ELO.
  3. 25 Nov 2025 TPM 2.0 becomes mandatory for all players.
  4. 14 Oct 2026 Windows 10 is no longer allowed — Windows 11 (23H2+) becomes the only supported OS.

Dates announced by FACEIT (Windows Security Requirements FAQ); the rollout schedule can shift.

Step 0 · Check the foundation The foundation: UEFI + GPT

Almost every FACEIT AC error traces back to two things: your BIOS must run in UEFI mode (not Legacy/CSM) and your system disk must be GPT (not MBR). Check this before touching anything else.

Check Win+R → msinfo32. Look at two fields: “BIOS Mode” and “Secure Boot State”.

✓ BIOS Mode = UEFI

Good — almost everything is fixable right in BIOS/Windows. If “Secure Boot State” is Off, go to the Secure Boot card below. If it’s On but FACEIT still complains, re-check drivers and reinstall the AC client.

✕ BIOS Mode = Legacy (CSM)

STOP. Do NOT enable Secure Boot — on Legacy/MBR the PC will fail to boot. Check the disk partition style (Win+R → diskmgmt.msc → disk Properties → Volumes → “Partition style”). If GPT — disable CSM in BIOS (Boot → CSM/Legacy Support → Disabled / “UEFI only”), then enable Secure Boot. If MBR — convert with mbr2gpt, or clean-install Windows from USB (Rufus: scheme GPT, target UEFI; or Ventoy) with CSM disabled.

Trust factor: why you’re asked for more than your friend

FACEIT AC is not only a cheat detector — it also acts as face control. The exact set of features it forces you to enable depends on how much it trusts your account: reports, playing in a stack with cheaters/boosters/smurfs, playing from a PC café on another IP, or several accounts from one PC all raise the bar. One player can play without core isolation or virtualization; another must enable every Windows and motherboard security mechanism. So treat the list below as a menu — switch on whatever your client actually asks for.

First: a clean, official Windows

Pirated and “debloated” Windows builds with stripped updates, Defender and security components are the #1 reason errors won’t fix. On such a system TPM, Secure Boot, Memory Integrity and Windows Update often simply don’t work — and you can’t even tell what was removed. Install an official Windows 11 image (23H2+) and tune it by hand, not with a gutted build.

Please enable Secure Boot

Enable Secure Boot

BIOS / UEFI
Symptom

FACEIT AC shows “Please enable Secure Boot” — often after a Windows reinstall, hardware swap or BIOS reset.

Why it happens

“Secure Boot: Enabled” in BIOS is not the same as it being active. It only truly works in UEFI mode with GPT disks, and often needs its keys re-written.

Steps
  1. Win+R → msinfo32. Confirm BIOS Mode = UEFI (if Legacy — see “The foundation” and stop here).
  2. Reboot → Del/F2 → Security tab (or Boot).
  3. New BIOS (2022+): Secure Boot = Enabled, Secure Boot Mode = Standard. Often enough.
  4. Still asking at “Enabled”: set Secure Boot → Disabled, then Secure Boot Mode → Custom (lets you re-write keys).
  5. Key Management → “Restore Factory Keys” / “Install default keys” (if active) → confirm.
  6. Set Secure Boot back to Enabled (Standard). Save (F10) & exit.
  7. Reboot → msinfo32 again: Secure Boot State should now read On.
BIOS paths
  • MSI Settings → Advanced → Windows OS Configuration → Secure Boot. Доп. параметр Secure Boot Preset / hardware OS → Maximum Security.
  • ASUS Boot → Secure Boot → OS Type → «Windows UEFI Mode» (+ Key Management → Clear/Restore Keys).
  • Gigabyte BIOS → Secure Boot → Secure Boot Enable + Secure Boot Mode → Standard/Custom.
  • ASRock Security → Secure Boot → Enabled + Active Secure Boot; Install Default Secure Boot Keys.
↻ If it didn’t help
  • Update your BIOS and Windows — on beta BIOS versions Secure Boot can be flaky.
  • PC hangs or won’t boot after enabling → disk is MBR/Legacy: go back to “The foundation”.
  • On an MBR disk, convert first: admin cmd `mbr2gpt /validate /allowFullOS` then `mbr2gpt /convert /allowFullOS` — only then disable CSM and enable Secure Boot.
  • No Secure Boot option at all → CSM (Legacy) is on. Switch to UEFI first.
  • Gigabyte board with a 2022-era BIOS: Secure Boot shows Enabled but the AC sees it as invalid (expired Microsoft KEK cert) → Key Management → Restore Factory Keys + update BIOS.
  • Very rarely the BIOS module is damaged (board defect): only a board swap helps.

↳ Still asking after this? Update your BIOS and Windows. If the PC hangs on boot, your disk is likely MBR/Legacy — see “The foundation” above.

Full Secure Boot fix guide →
Please enable TPM 2.0 / TPM attestation failed

Enable TPM 2.0

BIOS / UEFI
Symptom

“Please enable TPM 2.0” or “TPM attestation failed”. The AC won’t start without TPM 2.0.

Why it happens

TPM 2.0 is a security module on most modern boards. FACEIT AC will not start without it. Intel exposes it as PTT; AMD as fTPM.

Steps
  1. Win+R → tpm.msc (maximize the window). “The TPM is ready for use” + version 2.0 → already on.
  2. “Compatible TPM cannot be found” → it’s off in BIOS. Reboot → Del/F2 → Advanced or Security.
  3. Intel: enable “Intel Platform Trust Technology (PTT)”.
  4. AMD: enable “AMD fTPM” / “Security Device Support” → AMD CPU fTPM.
  5. AMD reset cycle (fixes ~80%): set fTPM = Disabled → save → boot to Windows → reboot → fTPM = Enabled → save → boot → open tpm.msc → “Clear TPM”.
  6. Got a discrete dTPM module on a header? Disable it in BIOS and switch to firmware TPM (fTPM/PTT) instead.
  7. Save, reboot, re-check tpm.msc.
BIOS paths
  • Intel Advanced / Security → Intel Platform Trust Technology (PTT) → Enabled.
  • AMD Advanced / Security → AMD fTPM switch → AMD CPU fTPM (или Security Device Support → Enabled).
↻ If it didn’t help
  • Enabled but still erroring → update your BIOS: TPM attestation bugs are a BIOS fix.
  • AMD “attestation failed” + Security processor Manufacturer Version starting 3.x (e.g. 3.92.0.5, in Windows Security → Device security) → known fTPM bug; only a BIOS update fixes it (look for a beta BIOS with the fix).
  • Board support: Intel since 6th gen (2015), AMD since X370/B350 (2016–17). X99/X79/LGA 1150/1155/2011 usually have no module — you need an add-on TPM or a new board.
  • TPM on but the chip is “dead” even after a BIOS update → hardware failure, take it to service.
  • The old advice “disable virtualization and core isolation for TPM” no longer works — TPM must be ON.

↳ ⚠ Using BitLocker? Suspend it before clearing the TPM (manage-bde -protectors -disable C:), or Windows will ask for your recovery key on boot. No TPM at all on your board? You need a board/CPU that supports it or an add-on TPM module. Pirated/debloated Windows often breaks TPM — use an official Windows image.

Full TPM 2.0 fix guide →
System is missing important Windows security updates

Missing Windows security updates

Windows
Symptom

“System is missing important Windows security updates”. Needs Windows 11 23H2+.

Why it happens

FACEIT AC requires up-to-date Windows security protocols. It needs Windows 11 23H2 or newer — Windows 10 support has ended.

Steps
  1. Open Windows Update and install every available security update.
  2. On Windows 10: upgrade to 11, or clean-install 11 from USB.
  3. On Windows 11 with no updates showing: run PC Health Check, then Windows 11 Installation Assistant → Start.
  4. If updates keep failing or you re-installed several times this year, check you are not stripping Windows Defender during “optimization”.
  5. Last resort: clean install of an official Windows image, then update via Windows Update.
↻ If it didn’t help
  • Even on the latest build it still asks → a clean install of an official Windows image almost always fixes it.
Full step-by-step guide for this error →
Please enable Memory Integrity / Core Isolation

Enable Memory Integrity

Windows
Symptom

“Please enable Memory Integrity / Core Isolation”.

Why it happens

A Core Isolation feature FACEIT may require at higher trust. It depends on Secure Boot and virtualization being on too.

Steps
  1. Search “Core isolation” → Windows Security → turn on Memory Integrity → reboot.
  2. Toggle greyed out or won’t turn on? Click “Review incompatible drivers” in Windows Security — it names the exact .sys blocking HVCI. Remove each owner (its uninstaller or `pnputil /delete-driver oemNN.inf /uninstall /force`).
  3. If it errors despite being on, enable SVM/VT-x and Secure Boot in BIOS — they are linked.
  4. If Windows Security is broken/won’t open (debloated Windows), reinstall an official Windows image.
↻ If it didn’t help
  • All on but the error stays → re-check that SVM/VT-x and Secure Boot are really active (not just “Enabled”).
  • Windows 10 is no longer supported — make sure the OS itself isn’t the problem.
  • Heads-up: Memory Integrity ON breaks PUBG (Steam), Lineage 2 private servers, GameLoop and The Finals — a known toggle conflict. If you play those too, you’ll have to flip it per game.
  • On AMD, SVM + Memory Integrity can give your Nvidia GPU Code 52 in Device Manager → fix by reinstalling the Nvidia driver with DDU, or turning Memory Integrity back off.

↳ Old FACEIT guides told you to DISABLE core isolation for TPM — that no longer applies. TPM must be ON now.

Full TPM 2.0 & Memory Integrity guide →
Please enable virtualization (Intel VT-x / AMD SVM)

Enable virtualization

BIOS / UEFI
Symptom

“Please enable virtualization” (Intel VT-x / AMD SVM).

Why it happens

CPU virtualization must be on in BIOS, and sometimes in Windows too.

Steps
  1. BIOS → Advanced → CPU Configuration.
  2. AMD: enable “SVM Mode” / “SVM” / “AMD-V”.
  3. Intel: enable “Intel Virtualization Technology” / “VT-x”.
  4. Save & reboot.
  5. If Windows still reports it off, enable virtualization in Windows features too.
BIOS paths
  • MSI OS Settings → CPU Features (или просто Advanced).
  • Gigabyte Tweaker → Advanced CPU Settings → SVM Mode / VT-x.
  • ASUS / Intel Advanced → CPU Configuration → Intel Virtualization Technology.
↻ If it didn’t help
  • Error “Hypervisor launch type is off” → admin Command Prompt: bcdedit /set hypervisorlaunchtype auto, then reboot.
Please enable IOMMU (VT-d)

Enable IOMMU / VT-d

BIOS / UEFI
Symptom

“Please enable IOMMU”. Usually for players at ~2000 ELO+.

Why it happens

Usually required for players at ~2000 ELO+. AMD calls it IOMMU; Intel calls it VT-d.

Steps
  1. Update your BIOS first.
  2. AMD: Advanced → AMD CBS → NBIO Common Options → enable IOMMU.
  3. Intel: enable “VT-d” (Advanced → System Agent / PCI subsystem / CPU config).
  4. Some boards also need “Kernel DMA Protection” enabled. Save & reboot.
BIOS paths
  • AMD (MSI) Advanced → AMD CBS → NBIO Common Options → IOMMU (или OC → CPU Common Options).
  • AMD (ASUS/Gigabyte) AMD CBS → NBIO, либо System Agent (SA) Configuration.
  • Intel Advanced → System Agent (SA) Configuration / PCI Subsystem / CPU Config → VT-d → Enabled.
↻ If it didn’t help
  • No IOMMU/VT-d option even after a BIOS update → some old/budget boards simply don’t have it.
Enable NX / Execute Disable Bit / DEP

Enable NX bit & DEP

BIOS / UEFI
Symptom

“Enable NX / Execute Disable Bit / DEP”.

Why it happens

Data Execution Prevention must be active at CPU and Windows level.

Steps
  1. BIOS → Advanced → CPU Configuration → set “NX Mode” / “Execute Disable Bit” / “XD Bit” to Enabled.
  2. Windows: System → Advanced system settings → Performance → Data Execution Prevention → turn on DEP for all programs and services.
  3. Reboot and re-check.
You need to disable test signing

Disable driver test signing

Windows
Symptom

“You need to disable test signing to launch FACEIT AC”.

Why it happens

Windows is in test-signing mode, usually after safe-mode boots or third-party “optimizer” driver testing.

Steps
  1. Open an elevated Command Prompt (Run as administrator) — not from a PowerShell wrapper.
  2. Check the flags: bcdedit /enum {current} — look at testsigning, nointegritychecks, debug.
  3. Run the full batch: bcdedit /set testsigning off · bcdedit /set nointegritychecks off · bcdedit /debug off
  4. Reboot.
↻ If it didn’t help
  • Command won’t apply (Secure Boot on) → that’s fine: with Secure Boot, test signing is already off — look elsewhere.
  • On a cracked/activator Windows, testsigning turns itself back on after every reboot — the only real fix is a clean licensed Windows.
The service cannot be started

AC service cannot start

Windows
Symptom

“The service cannot be started”.

Why it happens

The FACEIT AC service was disabled — often by an “optimizer” that touched services or the registry.

Steps
  1. Win+R → services.msc.
  2. Find every FACEIT service (FACEITService / FACEITAC) → Startup type = Manual (or Automatic) → Start.
  3. Error 1053/1067 or it won’t start → your antivirus is blocking it: whitelist C:\Program Files\FACEIT AC\ in Kaspersky/Dr.Web/ESET and turn off self-defense for the restart.
  4. Service missing entirely (a tweaker deleted it) → recreate it: sc create FACEITService binPath= "C:\Program Files\FACEIT AC\faceitservice.exe" start= demand — or just reinstall the AC.
  5. Still failing → reinstall the FACEIT AC client from faceit.com.
↻ If it didn’t help
  • Tuned your system with tweaks → reset Windows security services to default, then retry.
Error verifying digital signature

Error verifying digital signature

Windows
Symptom

“Error verifying digital signature” when the AC starts.

Why it happens

The Windows root certificate store is broken or the system clock is wrong, so the AC can’t validate signatures.

Steps
  1. Fix the clock: Settings → Time & language → set time & time zone automatically; or admin cmd `w32tm /resync /force`.
  2. Update root certificates: run Windows Update and install everything (root certs ship through it).
  3. Repair system files: admin cmd `sfc /scannow`, then `DISM /Online /Cleanup-Image /RestoreHealth`.
  4. Reboot and relaunch the AC.
Your Windows kernel has been modified

Windows kernel has been modified

Windows
Symptom

“Error: your Windows kernel has been modified” — PatchGuard tampering detected.

Why it happens

Something patched the kernel at runtime — usually leftovers of cheats, an old PatchGuard bypass, or a “debloat”/tweak tool.

Steps
  1. Repair the system: admin cmd `sfc /scannow`, then `DISM /Online /Cleanup-Image /RestoreHealth`.
  2. Scan for a rootkit: Malwarebytes Anti-Rootkit (or another anti-rootkit tool).
  3. Remove any kernel-driver loaders / tweak tools and reboot.
  4. If it persists, the only reliable fix is a clean install of an official Windows image.

↳ If you ran cheats on this account before, traces in the kernel can also mean a FACEIT ban — not just an error.

Full clean reinstall of FACEIT AC

Clean reinstall of FACEIT AC

Windows
Symptom

A normal uninstall/reinstall doesn’t help and the generic “reinstall the client” advice keeps failing.

Why it happens

Leftover files, registry keys and a stuck driver/service survive a normal uninstall — they must be wiped by hand.

Steps
  1. Quit FACEIT AC from the tray (right-click → Quit).
  2. services.msc → FACEITService → Stop → Startup type = Disabled.
  3. Uninstall via C:\Program Files\FACEIT AC\unins000.exe (as admin), or Settings → Apps. Reboot.
  4. Delete leftovers: C:\Program Files\FACEIT AC\, C:\ProgramData\FACEIT\, %LocalAppData%\FACEIT\, C:\Windows\System32\drivers\FACEIT*.sys (use Safe Mode if a .sys won’t delete).
  5. In regedit remove: HKLM\SYSTEM\CurrentControlSet\Services\FACEITService, HKCU\Software\FACEIT, HKLM\SOFTWARE\FACEIT.
  6. Reboot → install a fresh AC from faceit.com → run as administrator → Log in with Steam.
Incompatible driver detected (nvme, mtkwlex …)

Incompatible driver detected

Drivers
Symptom

“Incompatible driver detected” naming a driver like nvme (Samsung / Solidigm / Micron / Phison SSD) or mtkwlex (MediaTek RZ616 Wi-Fi 6E). The AC won’t start.

Why it happens

A proprietary storage or Wi-Fi driver is incompatible with the DMA protection / IOMMU that FACEIT now enforces. Swapping it for the standard Microsoft driver (or a fresh one) fixes it. Unlike “Forbidden driver”, the driver isn’t banned — it’s just an old/incompatible version.

Steps
  1. SSD / NVMe (Samsung / Solidigm / Micron / Phison): Device Manager → Storage controllers → right-click the proprietary NVMe controller → Update driver → Browse my computer → Let me pick → “Standard NVM Express Controller” → reboot.
  2. For a SATA drive pick “Standard SATA AHCI Controller” the same way. (Samsung Magician / vendor toolboxes stop working after this, but the AC starts.)
  3. Wi-Fi MediaTek RZ616 (mtkwlex): Settings → Windows Update → Advanced options → Optional updates → tick the MediaTek driver → install → reboot.
  4. If the MediaTek update isn’t listed: Device Manager → Network adapters → MediaTek → Properties → Details → Hardware Ids → copy the top value → download that driver from the Microsoft Update Catalog → install the .inf.
↻ If it didn’t help
  • The driver keeps coming back after a reboot → an app reinstalls it (Samsung Magician, a vendor toolbox). Uninstall that app first, then swap to the standard driver again.
  • No “Optional updates” section → download the driver by Hardware ID straight from catalog.update.microsoft.com.

↳ Different from “Forbidden driver”: there the driver is banned outright; here it just needs updating or swapping to the Microsoft standard driver.

Forbidden driver (RTCore64, WinRing0x64, edevmon / ESET, Interception …)

Forbidden / blocked driver

Drivers
Symptom

A specific .sys driver name is named as forbidden/blocked (HWiNFO, storage or sound drivers).

Why it happens

A driver with an outdated/vulnerable signature is loaded — common with monitoring tools (HWiNFO) and storage/sound drivers.

Steps
  1. First just reboot — that alone unblocks the AC after the first launch in many cases.
  2. If the window shows a .sys path, find its owner: admin PowerShell `Get-WmiObject Win32_SystemDriver | ? PathName -like "*name*"`, or simply Google the .sys name.
  3. RTCore64.sys → MSI Afterburner / RivaTuner (RTSS): update to the latest version.
  4. WinRing0x64.sys → OpenRGB, HWiNFO, EVGA Precision: close the app, then in admin cmd `sc stop WinRing0_1_2_0 && sc delete WinRing0_1_2_0` and delete the file from C:\Windows\System32\drivers.
  5. edevmon.sys / EpfwLWF.sys → ESET: a normal uninstall leaves an NDIS filter behind — run ESETUninstaller.exe in Safe Mode.
  6. keyboard.sys / mouse.sys → Interception driver: run install-interception.exe /uninstall from its folder, then reboot.
  7. inpoutx64.sys / HwRwDrv.sys → old overclock tools / AOMEI Backupper: update or uninstall the parent app.
  8. A nameless driver whose name changes on every reboot → Lenovo PC Manager (CN version) or a rootkit: remove Lenovo PC Manager; if there is none, scan with Malwarebytes Anti-Rootkit.
↻ If it didn’t help
  • Yellow “!” in Device Manager → update or re-plug the device; sometimes it’s easier to uninstall the driver and let Windows install its own.

↳ FACEIT updates its blocked-driver list without notice, so the exact names change over time. The current list lives in the FACEIT support KB.

Fatal errors (23, 78/79, 95, 99, 100, 115, 122, 126) & memory corruption

FACEIT fatal error codes

Fatal codes
Symptom

A “Fatal error” with a numeric code, or “Memory corruption detected”.

Why it happens

These are mostly hardware/driver/Windows-integrity issues. The fix depends on the code.

Error codes
  1. Error 23 — update your BIOS.
  2. Errors 78/79 — test hardware: RAM with MemTest, CPU with Prime95. Often too-tight RAM timings or unstable OC.
  3. Error 95 — remove the “secret” folder if present; update ASUS Armoury Crate.
  4. Error 99 — bad sectors / pagefile issue — check your SSD/HDD.
  5. Error 100 — an overlay/recording app is hooking the game — close capture/analytics overlays.
  6. Error 115 — possible rootkit — scan with an anti-rootkit tool (e.g. Malwarebytes Anti-Rootkit).
  7. Error 122 — file/disk corruption or driver conflict — see “Forbidden driver” above.
  8. Error 126 — a critical Windows component is missing/corrupt — repair, then reinstall Windows if needed.
  9. Memory corruption detected — reset any RAM overclock to default; test RAM (TestMem5 / Karhu).
↻ If it didn’t help
  • Critical Error appeared after tweaks → first reset Windows security services to default, then act by code.
  • Hardware-testing window before the AC starts: either run the 10–15 min stress test or remove your overclock — FACEIT didn’t like your hardware’s behavior.
Anti-cheat restarts in a loop

AC restart loop

Network
Symptom

FACEIT AC restarts over and over and never finishes loading.

Why it happens

FACEIT AC cannot verify your hardware config or fetch its files — usually network/VPN/ISP related.

Steps
  1. Keep clicking Restart until it loads.
  2. Disable any VPN, reboot your router, and try again.
  3. If you are in a region with FACEIT connectivity issues, a stable connection / region change often fixes it.
You need the anti-cheat client running to connect

AC client must be running

Network
Symptom

“You need the anti-cheat client running to connect”, even though it is running.

Why it happens

Usually a mismatch between the Steam account in CS2 and the one linked to your FACEIT profile.

Steps
  1. Make sure the Steam account in CS2 is the one linked to your FACEIT.
  2. Restart Steam, the FACEIT AC client and the game.
  3. If the accounts differ — log into the right Steam or re-link FACEIT.
CIS-specific causes (pirated Windows, ESET / Kaspersky, Lenovo CN, internet cafés)

CIS-specific causes

Windows
Symptom

Common region-specific reasons FACEIT AC won’t start on PCs in CIS countries.

Why it happens

In CIS, the usual culprits are non-official Windows builds, locally popular antivirus software and laptops/cafés with extra kernel software.

Steps
  1. Pirated / “debloated” Windows (Ghost Spectre, AtlasOS, Tiny11, custom LTSC): Defender, attestation and updates are stripped — only a clean official Windows fixes it.
  2. ESET NOD32: a normal uninstall leaves edevmon.sys / EpfwLWF.sys — run ESETUninstaller.exe in Safe Mode.
  3. Kaspersky / Dr.Web: whitelist the FACEIT AC folder and turn off self-defense while the AC starts.
  4. Lenovo PC Manager (CN version, laptops from AliExpress): uninstall it — it loads a kernel driver the AC blocks.
  5. Internet cafés (CCBoot / CCU Cloud Update): they break TPM attestation — ask the café admin or use FACEIT saving-mode.
Still stuck? Work the checklist top-down

From safe to radical — don’t touch BIOS until Step 5, and don’t reinstall Windows until Step 6.

  1. Step 0 · Diagnose (5 min)
    • winver → Win 11 build ≥ 22621 (22H2), or Win 10 ≥ 19045 (22H2).
    • msinfo32 → BIOS Mode = UEFI, Secure Boot State = On.
    • tpm.msc → Specification 2.0, Status = Ready. Then launch the AC as administrator.
  2. Step 1 · Software (15 min)
    • Fully update Windows (Windows Update + Optional updates).
    • Reinstall the GPU driver with DDU + a fresh one from nvidia.com / amd.com.
    • Disable VPN, Hyper-V/VMware; close OpenRGB/MSI Center/AIDA64; remove old MSI Afterburner, Lenovo PC Manager, ESET (via ESETUninstaller).
  3. Step 2 · Antivirus (5 min)
    • Whitelist C:\Program Files\FACEIT AC\ in Kaspersky / Dr.Web / ESET / Defender.
    • Temporarily disable self-defense and confirm the AC starts.
  4. Step 3 · BCD / registry (10 min)
    • Admin cmd: bcdedit /set testsigning off · /set nointegritychecks off · /debug off · /set nx OptIn · /set hypervisorlaunchtype auto — then reboot.
  5. Step 4 · Service & reinstall (15 min)
    • services.msc → FACEITService → Manual + Start.
    • No luck → full clean reinstall of the AC (see the card above).
  6. Step 5 · BIOS (30+ min, careful)
    • Enable TPM 2.0 (fTPM/PTT), virtualization (VT-x/SVM), IOMMU/VT-d, Secure Boot (UEFI + GPT).
    • Update BIOS to the latest (mandatory for the AMD TPM 3.x bug); run the TPM reset cycle.
  7. Step 6 · Reinstall Windows (last resort)
    • Rufus → official Windows 11 23H2/24H2 ISO → GPT/UEFI, CSM off → clean install.
    • Install only vendor drivers (no DriverPack); put the FACEIT AC on first.
Conflicting software — what to remove or update

FACEIT AC is a kernel-level anti-cheat, so it clashes with other kernel software. Find your program and act.

  • Old anti-cheats nProtect GameGuard, Xigncode3, BattlEye/EAC runtime, leftover Riot Vanguard (vgk.sys) → uninstall the game / Vanguard, verify sc query vgk says it’s gone.
  • RGB / peripherals OpenRGB (WinRing0x64.sys), SignalRGB, old MSI Center, iCUE, Razer Synapse 2.x, old Logitech G HUB → update to latest; for OpenRGB delete the WinRing0 service.
  • Overclock / monitoring MSI Afterburner < 4.6.5, old RTSS, old HWiNFO64, Throttlestop, ASUS GPU Tweak → update or close before launching.
  • Antivirus ESET (edevmon.sys/EpfwLWF.sys — use ESETUninstaller), Kaspersky, Dr.Web, Avast → whitelist the AC folder or remove.
  • VPN / proxy NordVPN, ExpressVPN, WireGuard, Cloudflare WARP, Hola → disable the service and the TAP/virtual adapter while the AC starts.
  • Virtualization VMware, VirtualBox, Sandboxie kernel drivers conflict → remove; Hyper-V/WSL2 are needed for Memory Integrity but can be toggled off for a test.
  • Cheat traces Cheat Engine, x64dbg, Process Hacker (KProcessHacker.sys), kernel-driver loaders → remove; scan with Anti-Rootkit. ⚠ Old cheat traces can also mean a ban.
  • Disk / backup tools AOMEI Backupper, EaseUS Todo/Partition Master, old Acronis True Image → update to latest or uninstall.
  • System “optimizers” O&O ShutUp10, WPD, Privatezilla, Win10Tweaker → if the AC broke right after “optimizing”, revert to defaults and reinstall the AC.