Persistent Launch Context Issue with EA App + AntiCheat (FC26)

I’d like to share a technical issue that appears to stem from how launch context and anti-cheat state are handled across Steam and the EA App.

After using a mod manager briefly (which altered the game’s launch path), the game now consistently triggers a “Launch with custom arguments” prompt. From that point on, the game no longer launches, even after:

• Fully uninstalling and reinstalling the EA App
• Clearing all EA-related caches (ProgramData, AppData)
• Reinstalling the game via Steam
• Resetting Steam configuration and local userdata
• Testing on a fresh Windows user profile

Despite all of this, the system continues to behave as if a custom launch context is still active.

What this suggests

It appears that some form of launch state or anti-cheat flag is being persisted beyond the local installation — possibly at the integration layer between Steam, EA App, and the AntiCheat service.

More importantly, there is no visible way for users to reset or clear this state.

Why this is a problem

From a user perspective, this creates a “dead-end” scenario:

• The system detects a modified launch context
• The user removes all modifications
• But the system still behaves as if the modification exists

There is no feedback, no reset mechanism, and no recovery path.

This is especially frustrating because it turns what should be a recoverable configuration issue into a permanent failure state — even on a clean reinstall.

UX / System Design Concern

This feels like a case where:

System state persists across layers, but user control does not.

If the system can detect a “custom launch,” it should also provide a way to:

• Reset launch context
• Rebuild anti-cheat state
• Or at least explain what is being detected

Without that, users are left guessing and repeatedly reinstalling without understanding why nothing changes.

Suggestion

Consider implementing one of the following:

• A “Reset Launch Configuration” option within EA App
• A full AntiCheat state reset tool (not just reinstall)
• Clear diagnostic feedback when a custom launch is detected
• Decoupling mod detection from persistent launch state where possible

I’ve been playing FIFA/FC titles for years without issues, so encountering a situation where the game becomes unlaunchable — with no clear recovery path — is quite disappointing.

This isn’t about modding itself, but about the lack of system resilience when something goes wrong.

I hope this feedback helps improve the reliability and debuggability of the platform.

Thank you.