The Cheating Fix Nobody Wants to Actually Implement
Cheating in online games isn't a detection problem, it's an identity problem. Anti-cheat vendors keep playing whack-a-mole with kernel drivers and behavior heuristics because they're trying to solve "is this specific process cheating" instead of "is this a real, accountable human." Flip the problem and it gets a lot smaller. The system: Verified accounts only. To play ranked/competitive servers, you need an account tied to a mobile number and a real email provider — no Gmail, no Hotmail/Outlook, no throwaway domains. Use a provider that requires ID-backed signup or a paid domain, so burner accounts cost real money and real effort to make. Device-bound certificate. Once verified, the game client issues a digital certificate tied to that install — hardware ID plus account. This certificate is what the server checks, not just a login token. Server-side auth gate. Game servers reject any connection that doesn't present a valid, verified certificate. No cert, no join. This happens at the network/auth layer, before matchmaking, before the anti-cheat kernel driver even has to do anything. Ban = actually banned. Because the account is tied to a phone number and a real identity trail, a ban follows the person, not just the hardware ID. Rebuying the game or reinstalling Windows doesn't get you back in — you need a new verified phone number and a new legitimate email, which raises the cost of re-offending dramatically. Why it works faster than software-based anti-cheat: current anti-cheat is reactive — it detects a cheat, cheat devs patch around it, repeat forever. This is preventative — it doesn't care what software you're running, it cares whether you're a verified, accountable person. A cheater who gets banned can't just spin up a new Gmail and be back in five minutes. A few honest caveats worth flagging, since "fixed in a month" is the part that won't survive contact with reality: Phone verification has a black market already — SMS-verification bypass services exist for pennies per number, and cheaters/gold-farmers already use them at scale for other platforms. It raises the cost, it doesn't kill the supply. Privacy and regulatory pushback — tying gameplay to a real phone number is a significant data-collection ask, and in places like the EU it runs into GDPR questions about necessity and proportionality. Legit players get burned — people who share a household, use work-issued email domains, live somewhere with unreliable mobile carriers, or just don't want their gamertag linkable to their real number will have real friction. It doesn't stop the actual cheat vector — device-bound certs authenticate the account, not the client integrity. A verified, real-identity player can still run an aimbot; you've made cheaters more identifiable and bannable, not literally undetected. The one gaming platform who has the balls to do this will show cheating will be wiped out in 3 months maybe less .
"Kicked for Inactivity"
PC, I can't even get into a match. Game acts like it's searching for a match, and the search progress bar gets a bout a quarter of the way out and then the entire application freezes. Less than a minute later I'm hit with "You were kicked for inactivity." This has been multiple days and multiple attemps at getting into a match a day. I've deactivated FRS in graphics and still can't get into a match. I've restarted my router, I've restarted my PC, I've cleared my cache, I've verified game files, I still can't get into a match. I can't get a hold of ANYONE at EA. This has only happened after they started requiring SecureBoot to play any of their content. Spent $60 on a game and I can't even play it.
Crash at start menu
I was playing without issues until yesterday afternoon. Today, however, the game crashes just a few seconds after loading the start menu screen. I’ve already tried the usual fixes: repairing/reinstalling EA Javelin Anticheat, verifying game files, disabling overlays, running as administrator, closing potentially conflicting programs, adjusting exploit protection settings, and so on. Unfortunately, it still crashes. Yesterday, I updated my Nvidia drivers and installed the Windows update that was released just yesterday. Could that be the problem? I tried reverting to the old Nvidia drivers, but with no success. I'll also try a system repair. Other users on Reddit have also reported the same problem, and I tried their suggested solutions without any success.
Battlepass not progressing
Completed multiple game and in the game completed weekly challenges, earned tokens would appear at the end of game screen however battlepass would not progress and would state "no progress earned". restarted game multiple times and nothing worked and am now missing ~20 tokens from progress.
Game Crashes Mid Match
I can not finish a match in the game about 10 or so minutes in the game just auto closes without warning. I have tried the following options. My PC specs are below as well. I am unable to upload the crashdump file. Repair EA Anti-Cheat & Run as Admin: Go to your EA Anti-Cheat folder (C:\Program Files\EA\AC), right-click EAAntiCheat.Installer.exe, and choose Run as Administrator. Select Battlefield 6 and click Repair. Set Steam, the EA App, and bf6.exe to Run as Administrator via their executable compatibility settings. Disable Overlays & Conflicting Software: Turn OFF the Steam Overlay (Steam > Right-click BF6 > Properties > General). Close Razer Haptic/Chroma apps, FPSRunner, and hardware monitoring overlays (MSI Afterburner/GeForce Experience). Clear Shader & Profile Cache: Delete the folder at C:\Program Files (x86)\Steam\steamapps\shadercache\2807960. Go to Documents\Battlefield 6\settings and rename PROFSAVE_profile to PROFSAVE_profile_old. Clean Driver Install & In-Game Settings: Perform a clean installation of your graphics driver (using NVIDIA's setup or DDU). PC Specs: Processor: AMD Ryzen 7 3700X 8-Core Processor (3.60 GHz) Installed RAM: 32.0 GB Graphics card: NVIDIA GeForce RTX 2080 SUPER (8 GB) Edition Windows 11 Home Version 25H2 OS build 26200.9445
