Your game failed to launch
Product: EA Desktop Platform:PC Error Report ID (learn how to create an Error Report ID in the sticky post) Which client functionality are you experiencing this bug with? Launch Game When did th...
Forum Discussion
EA_Jason
EA SPORTS FC™ Team
EA SPORTS FC™ TeamHey @AK47AssaultWaifu,
That you for already trying to clear the cache via App Recovery and reinstalling the game and app.
I have seen this error message a few times and some community members reported that this happened due to their firewall/vpn/anti-virus.
Could you temporarily disable them and then launch the EA app as an administrator?
You can launch the EA app as an administrator by navigating to:
C:\Program Files\Electronic Arts\EA Desktop\EA Desktop
Then you right click on EADesktop and choose "Run as administrator".
I tried running as an admin and no luck.
Im not using a vpn and an anti-virus (Currently using Windows defender though).
I just renewed my Xbox membership and it was working fine a couple of months ago.
Edit: I should add I disabled Windows Defender and tried to run the client in admin mode. No luck.
- EA_Jason
Hmmm then we need to try a few different things:
Create a new administrator account on Windows and log into that account to perform a clean boot. Then log into the new admin account and only launch the EA app/Madden and let me know if it works.
You might have to choose to run the EA app and Madden as an administrator too.
Community Managers are once again clueless. I face the same problem and none of the suggested actions helped. I have no VPN, no special Anti-Virus software, I re-booted, logged out of EA and logged back in again, tried everything. The issue appeared out of the blue after working fine for while.
From the 5 games managers I run on my PC, (Epic Launcher, Xbox, Ubi, Steam, EA), EA is by far the most embarassing. I own the game but it says it can't launch it. I'm forwarding this to my lawyer, since EA is denying me access to content I own. I'm done dealing with constant error messages.
- EA_Jason
I mean you're not wrong @Exa2911.
Judging by the information that was provided I can't instantly discern what is causing the issue and I am trying to find out through performing the basic troubleshooting steps first.
If those don't work, then we often have a look at the DxDiag and MsInfo32 to find any clues about what causes this.
Have you tried the steps that I provided above and could you let me know what else you have tried?
