Battlefield Ban Appeal: Error 117, Portal Flags, and What EA Actually Reads

Error 117 at login isn’t a connection issue. It means EA Anti-Cheat’s kernel driver blocked the game launch – usually the first visible sign that something was flagged. A lot of players spend time troubleshooting it as a technical problem before realizing the account is actually banned. That confusion matters because the window to gather relevant evidence is narrowest right after the flag fires.

Getting unbanned from Battlefield starts with reading the error correctly – and then building the ban appeal around what that error actually signals.

Error 117 and What It Tells You About the Appeal

Error 117 is specific to EA Anti-Cheat’s kernel-level driver. It appears when the driver itself blocks the game launch, which typically follows a cheat detection or a flagged third-party process. That distinction is useful because it narrows what the appeal needs to address.

EA Anti-Cheat checks process hooks, packet timing, and kernel drivers. Overlays that inject into DirectX, mouse driver macros, GPU monitoring tools, and certain performance software can all trigger the same signature as genuine cheat tools. NVIDIA Reflex and AMD Anti-Lag are whitelisted and won’t cause issues on their own – but third-party overlays that inject additional DLLs alongside them can.

If error 117 is what you’re seeing, the appeal needs to address the kernel-level flag specifically: what was running when you were banned from Battlefield, what injected into the game process, and why it wasn’t cheat software. A DxDiag generated after removing any overlays or macro tools, paired with a full process list from the flagged session, is the technical core of this case. An unedited gameplay clip or stream VOD for the flagged match supports it – if linking a stream, give the exact timecode rather than the full video so the reviewer can jump directly to the relevant moment.

Verified game files from the EA App or Steam client are worth including too. Corrupted game data can produce behavior that looks like memory edits from the anti-cheat side, and a clean verify result closes that question before the reviewer asks it.

The Portal Mode Trap – and Why It Needs Its Own Framing

Portal mode is specific to Battlefield and creates a ban scenario that doesn’t exist in any other game. It lets players access maps and settings from older Battlefield titles – but some community-run Portal servers are configured to bypass EA’s XP throttling rules. Playing on those servers, even without knowing they’re flagged, can trigger an automated exploitation ban.

EA’s automated checks work differently by mode and playlist. If the ban appeared after Portal sessions, the appeal needs to name the specific server or playlist, whether it was community-hosted or official, and what the session looked like from a progression standpoint. “I was playing Battlefield” gives the reviewer nothing to filter against. “Community Portal server, TDM playlist, flagged session on (map)” gives them a specific context to check.

The same logic applies to stat padding in co-op or custom modes. Playing with a friend in a way that inflates weapon mastery or unlock progress faster than normal can trigger a temporary stat wipe or a seven-day suspension – even without any intent. Match IDs and a clear explanation of the session context are what frames those cases correctly and separates an intentional exploit from something that just looked suspicious in the data.

What the Ban Appeal Needs Beyond the Error Code

Error 117 covers kernel-level and overlay-related flags. Other Battlefield ban types need different proof, but the same framing principle applies – address what EA actually logged, not just what you believe happened.

• For exploit or map glitch flags – a video showing the accidental trigger and a patch note link confirming the glitch existed at the time. An appeal that acknowledges the behavior happened but explains it was unintentional and contextualizes it against the patch state is consistently stronger than a flat denial.

• For boosting or RMT – match IDs, chat history showing the context of the sessions, and a direct explanation of any IP discrepancies. Unexplained location jumps in session data read as account sharing to the reviewer, and leaving them unaddressed creates a gap that’s harder to explain after the fact.

• For compromised accounts – password reset email, IP login data showing the location jump, and two-factor authentication now enabled. Get the account secured before submitting. An appeal describing a compromise while the account is still accessible raises an obvious follow-up question the reviewer will need answered before actioning anything.

• For toxicity – full chat log with surrounding context, not just the flagged lines. Prior account history without penalties adds weight. Reformation framing – specific steps taken, not a general apology – moves these cases faster than arguments about proportionality.

What Gets Left Out of Battlefield Ban Appeals – and Shouldn’t

A few things come up consistently in cases that stall:

• Not mentioning the game mode. EA’s review filters work by mode and playlist. Naming the specific mode, server type, and region gives reviewers a faster path to the right data. Omitting it means they have to find it themselves, which slows everything down.

• Not disclosing VPN use. If a VPN was active during the flagged match, list the exit IP that was active at the time. An unexplained IP jump alongside an anti-cheat flag creates a compounding suspicion that’s harder to address after submission than before it.

• Continuing to play Portal XP farm lobbies while the appeal is under review. EA’s Game Integrity Team can see account activity between submission and review. New stat anomalies during an active appeal can invalidate an otherwise solid case before anyone reads it.

• Sending multiple short follow-ups. EA’s review timeline runs around two business days for most Battlefield ban cases, up to a week for complex anti-cheat reviews. One complete appeal with everything attached moves faster than a chain of partial submissions – each follow-up before a reply adds time rather than urgency.

How to Get Unbanned from Battlefield

The only way of overturning a BF 6 ban is by submitting an EA ban appeal. Here’s how to do that:

Step 1: In order to start your Battlefield unban appeal, you’ll need to go on the official EA Help Center page.

Step 2: Click on “Help with a Game”, then select “Battlefield 6”.

Step 3: Scroll to the very bottom of this page, then click on “Contact us” next to “Looking for something else?”.

Source: help.ea.com

Step 4: Select the platform you’re playing Battlefield 6 on, which in our case would be “PC”.

Step 5: Select the topic as “Manage my account”, followed by the issue “Banned or suspended account”.

Source: help.ea.com

Step 6: Click on “Select contact option”.

Step 7: Log into your banned EA account, in case you aren’t already logged in.

Step 8: Choose the “Email” contact option, which will open the form for your Battlefield unban appeal.

Source: help.ea.com

Step 9: Now that we’re on the actual Battlefield unban appeal form, we’ll complete it as follows:

• enter your account’s “First and Last name”, as well as your account’s registered mail address;
• write a concise yet relevant subject, such as “Battlefield ban appeal”;
• under “Please describe your issue”, write your ban appeal – timing, reason, exonerating evidence or circumstances. Or, you can let us handle it – get a pro-crafted ban appeal now!
• attach any relevant files, if you have any (screenshots, documents and such).

Once all of that is done, simply press the “Email us” button underneath the Battlefield ban appeal, and your ticket will be sent to EA Support.

You’ll receive their answer via mail, the one you’ve put in the Battlefield 6 account unban form, so make sure to keep an eye on it, as well as on the Spam folder!