EA App suddenly stopped opening on Windows 11
Hi everyone, About two days ago, the EA App suddenly stopped opening on my computer without any apparent reason. Until then, I was able to play my games normally, but now, when I try to launch the a...
Forum Discussion
EA_Leeuw
Community Manager
Community ManagerHi everyone,
Thanks again for all the detailed troubleshooting you’ve shared.
If the EA app launches on a newly created Windows user account but not on your original one, that confirms the installation itself is working, and the issue is isolated to the Windows user profile.
Before considering creating or migrating to a new profile, please try the following on the affected account:
1. Clear EA app launcher cache only (safe step)
On the account where it fails:
- Press Win + R
- Type: %LocalAppData%\Electronic Arts\EA Desktop
- Delete the EA Desktop folder only
This removes launcher cache/config files but does not remove your installed games or cloud saves.
Restart your PC and test again.
2. Restart EA Background Service
- Press Win + R
- Type: services.msc
- Locate EABackgroundService
- Set Startup Type to Automatic
- If stopped → Start
- If running → Restart
Reboot and test.
3. Check for custom Environment Variables
- Search for “Environment Variables”
- Open “Edit the system environment variables”
- Click Environment Variables
- Remove any custom variables you may have manually added (for example GAME_DATA_DIR)
Restart after changes.
4. Clean Boot test (profile conflict check)
- Press Win + R
- Type msconfig
- Under Services, check “Hide all Microsoft services”
- Click Disable all
- Reboot and test the EA App
If it works in a clean boot, a third-party service tied to that profile is interfering.
If the app continues to launch normally on a new Windows user but not on the original profile after these steps, that confirms the issue is specific to that Windows profile’s configuration. In that case, continuing to use a new Windows account or migrating your files to one may be the most stable long-term solution.
If you're still affected, please share:
- Your Windows version + build
- Whether EABackgroundService was running
- Whether clean boot changed the behavior
We’ll keep monitoring this thread.
Hi EA_Leeuw, thanks very much for replying, I am still affected on my main (administrator) account. the local account works fine, but last time when I migrated to the local account and made it an admin and signed in with my microsoft account this issue resurfaced again after a couple of weeks so I'm afraid it's not a long term soloution for me at this moment. Already done 1-4 of your suggestions and none helped, I will answer your other questions:
- Windows 11 Pro, Version 25H2, OS Build: 26200.8037, Windows Feature Experience Pack 1000.26100.300.0
- It wasn't initially even though I changed it to automatic, but I started it manually and the app still crashed
- Clean boot had no effect, still crashed
I have attached more information about my system incase that is useful. Thank you.
- EA_Leeuw
Really appreciate you taking the time to test all of that and share your system info -- that helps narrow things down a lot.
Since the EA app launches correctly on a separate Windows user account and you've already cleared the cache, services, and performed a clean boot, this confirms the issue is tied specifically to the configuration of the original Windows profile rather than the app installation itself.
Looking at the details you shared, there are a couple of additional things worth trying that can sometimes affect how the app renders:
Disable overlays/device software temporarily
Your system shows Razer and Steam virtual audio/streaming devices. These can sometimes hook into applications at a user level.
As a quick test:
- Fully exit Razer Synapse / Razer software
- Exit Steam completely (make sure it’s not running in the tray)
- Then try launching the EA app again
Check for corrupted Windows user componentsOpen Command Prompt as administrator and run:
sfc /scannow
Then:
DISM /Online /Cleanup-Image /RestoreHealth
Restart after both are complete.
Test with a fresh Microsoft account link (optional check)
Since you mentioned the issue returned after linking back to your Microsoft account:
- Try keeping the new Windows profile as a local account only (no Microsoft account sign-in)
- Test the EA app there over a few launches
This helps confirm whether something synced with the Microsoft profile is causing the issue to recur.
If none of the above changes the behaviour and the app continues to work only on a new Windows profile, that confirms the issue is isolated to that specific user profile environment.
At that point, the options are to continue using the new profile or migrate your data, as you've already tested.
Let us know if anything above changes the behaviour.
Featured Places
