FACEIT AC "The service cannot be started" Fix

The message The service cannot be started is the most harmless of the FACEIT Anti-Cheat errors. It has nothing to do with UEFI, hardware, or Windows security: the FACEITService that the anti-cheat runs through is simply disabled. One window, one minute.

AK-47 | RedlineAWP | AsiimovM4A4 | AsiimovUSP-S | Kill ConfirmedAK-47 | Slate

The quick fix

1. Press Win + R, type services.msc, press Enter.
2. Find FACEITService in the list (it is sorted alphabetically).
3. Double-click it.
4. Set Startup type to Manual.
5. Click Apply, then the Start button.
6. Close the window and launch FACEIT AC again.

Manual, not Automatic, is deliberate: the anti-cheat starts the service itself when it launches, so automatic startup is unnecessary — the service would just sit in memory doing nothing.

Why the service disables itself

Three usual suspects, by frequency:

• "Optimizers" and tweakers. Utilities that disable "unnecessary" services, along with every kind of game booster, set unfamiliar services to Disabled wholesale. FACEITService gets caught in that sweep constantly.
• Antivirus software. Third-party antivirus sometimes blocks a kernel-level driver — which is exactly how any serious anti-cheat works. Add the FACEIT folder to exclusions.
• An interrupted update. If the client updated while the machine was shutting down or the connection dropped, the service can be left in an intermediate state.

The startup type is grayed out

That means you lack administrator rights, or the service is locked by policy.

Option one — the command line. Click Start, type cmd, right-click "Command Prompt" → "Run as administrator". Run two commands:

sc config FACEITService start= demand
sc start FACEITService

The space after start= is required — that is sc syntax, and without it the command returns an error.

Option two. Sign in to Windows under an account with administrator rights: services cannot be edited from a standard user account.

FACEITService is not in the list at all

Then the anti-cheat is only partially installed. Reinstall it:

1. Settings → Apps → Installed apps.
2. Uninstall FACEIT Anti-Cheat (you do not need to remove the FACEIT client itself).
3. Reboot — this is the step people skip most often, and without it driver leftovers interfere with the new install.
4. Download the anti-cheat again from the FACEIT site and install it by right-clicking the file → "Run as administrator".

The service starts and immediately stops

That is a different symptom. It usually means a conflict with another kernel-level anti-cheat — Vanguard from Valorant, ESEA, occasionally protection from other platforms. Two such drivers coexist poorly.

Check Installed apps and make sure only one is present. Vanguard in particular starts with Windows and keeps running even when Valorant is closed: it has to be uninstalled, not just exited.

If the problem survives all of that, it is no longer about the service. See the general breakdown of FACEIT AC errors — most likely you are hitting the Windows security requirements.

Why this error keeps coming back

"The service cannot be started" is not one failure but a shared message for a whole class of situations: the anti-cheat could not bring its service up. The reason is that FACEITService lives by Windows rules, and three different forces keep touching it.

Optimizers and tweakers. Programs promising to speed up your system disable services in bulk from lists found online. FACEITService lands on those lists regularly, because it is not signed by Microsoft and runs constantly. After every optimizer pass the error returns, looking like an anti-cheat fault when the cause is other software.

Third-party antivirus. An anti-cheat by nature does what malware does: loads a driver, reads other processes memory, watches running programs. Some antivirus products block this silently, with no notification, and the service simply never starts.

Windows updates. Feature updates sometimes reset service configuration and folder permissions. The error shows up right after a reboot, even though everything worked yesterday.

The practical conclusion: if the error returned a few days after you fixed it, look not at the anti-cheat but at whatever on your machine keeps switching it off.

What not to do

• Reinstall Windows. The problem is almost never the whole system; a reinstall costs hours and changes nothing half the time, because the same software goes back on afterwards.
• Disable your antivirus permanently. Adding the anti-cheat folder to exclusions is enough. Permanently disabled protection is a disproportionate price.
• Download a fix from a third-party site. The only correct source of the anti-cheat is FACEIT itself. Files named "faceit fix" in search results are a classic lure, and an account with skins interests an attacker more than your match does.
• Set the service to Automatic and walk away. The anti-cheat manages its own service: it is meant to start with the client, not to sit running permanently.

How to confirm the fix actually worked

No error when launching the client is not proof by itself: the service could have come up and died a minute later. Verify by fact rather than by feeling.

Open Services and find FACEITService. A healthy state looks like this: the service is running, the startup type is not grayed out, and the Windows event log has no fresh records of it terminating unexpectedly. If the state changes on its own within a few minutes, something is killing it, and the place to look is your antivirus and startup list rather than the anti-cheat itself.

The second method is more reliable: launch the FACEIT client and leave it for ten minutes without joining a match. If no error appears in that time and the service stays running, the fix is real. Testing inside a live match is a bad idea: a crash mid-game counts as abandoning, with all the rating consequences that follow.

Should I uninstall and reinstall the anti-cheat? Only if the earlier steps did not help. A reinstall repairs damaged files but does not remove the cause: if an antivirus or optimizer is killing the service, the error returns after the first reboot.

Why do I get this error when a friend on the same build does not? Because the cause is usually not Windows but the set of installed programs. The anti-cheat conflicts with specific software: security suites, tweakers, RGB drivers. An identical OS version guarantees nothing.

Can the anti-cheat harm my computer? It runs with driver privileges, like any kernel-level anti-cheat, and that is a deliberate trade-off: without such access there is no way to catch cheats hiding below Windows. Install it only from the official FACEIT site.