Hi robovelcro ,
Thanks for the detailed breakdown. Based on what you’ve described, this does not sound like the normal “launch on startup” behaviour, especially if:
- Run on startup is disabled in the EA app
- EA app is not listed/enabled under Windows Startup Apps
- Continue updates when the app is closed is disabled
- You fully exited the app from the notification area
- No EA-linked game, Xbox app, Ubisoft app, or EA app game launch is involved
The EA app should not be forcing itself into the foreground over unrelated activity after you have exited it.
A few things are worth separating here:
- EA app UI
This is the visible app window.
- EA Background Service
This can still be used for app/game maintenance, update checks, entitlement handling, and launch-related tasks. Disabling it through msconfig may stop the symptom, but it can also break expected EA app behaviour, so I would not recommend that as a first troubleshooting step.
- Automatic app update checks
Your test with disabling Install updates automatically is a good one, because if the app is being woken by an update-check path, that setting may help isolate it.
For now, could you please try the following and let us know what happens?
- Keep Install updates automatically disabled temporarily.
- Fully exit the EA app from the notification area.
- Reboot Windows.
- Do not manually open the EA app after reboot.
- Check whether the EA app still opens itself later.
- If it does, note roughly how long after reboot it happens and whether EA app.exe or EABackgroundService.exe was already running in Task Manager before the window appeared.
Also, please share:
- Your EA app version
- Your Windows 11 version/build
- Whether this happens once per session or repeatedly
- Whether the app opens to the Home page, a login screen, an update screen, or a blank/loading window
If disabling automatic app updates stops it from happening, that would be useful information, because it would point more towards an app update/check trigger rather than a normal startup setting.
I’ll pass this along as well, because the app unexpectedly opening in the foreground after being manually exited is not behaviour we’d want.