EA App fails to start in Windows 11

Since the latest update to the EA App, this is still not fixed, but I get a slightly different error. "15 [2023-05-02T14:43:57.037Z] PID: 31348 TID: 11636 ERROR (eax::components::gameLocalServices::GlsComponent::handleQtApplicationReady) An unrecoverable error happened when starting the app, handlers are not initialized. errorCode[101]" -- This only happens once the Connecting to the EA App screen goes, and I try again to load the EA App.

I have another Windows 11 device, a Surface Pro, which also has this same problem. I don't know if there's been a new update since I last posted, but that one has even more specific log entries, which are:
"10 [2023-05-06T21:41:02.274Z] PID: 25580 TID: 22868 ERROR (eax::apps::DesktopComponent::mainLoop) Error during initialization, code[101]

13 [2023-05-06T21:41:02.294Z] PID: 25580 TID: 20616 ERROR (eax::components::gameLocalServices::GlsComponent::handleQtApplicationReady) An unrecoverable error [ErrorSideBySideDesktop] happened when starting the app, handlers are not initialized."

I've tried a clean install of all Visual C++ redists from the Microsoft Website (x64 and x86 versions of 2005, 2008, 2010, 2012, 2013 and 2015-2022), a clean install of the EA App and updating it to the latest version (12.174.0.5431), using App Recovery, making sure Windows Update in Windows 11 is up to date (it wasn't, KB5025305 [2023-24 Cumulative Update Preview for Windows 11 Version 22H2 for x64-based Systems] was installed), and trying to Run as Administrator. After doing all of this, I still get the aforementioned "ErrorSideBySideDesktop" error.

I also have this problem. I have found restarting the computer or shutting it down and rebooting it as a short term solution.

I noticed it takes a bit of time to generate the EA login screen so perhaps we are not waiting long enough for it to load. Either way, it's annoying to do when I've just booted up for the day to have to constantly restart my computer.

@SquishyGrapes19 I've never been able to get this to work. Even with the update that released today, it isn't fixed! Weirdly, no matter how long I leave it, if I stop the "EABackgroundService" service in Services, or the Task Manager, the login screen pops up for a few seconds and then the app shuts down.

As of the most recent update to the EA App, 12.184.0.5441, the same issue exists and the "ErrorSideBySideDesktop" still appears in "AppData\Local\Electronic Arts\EA Desktop\Logs\EADesktop.log"! I hope to one day be able to report that it is working, but today is not that day. 😞

I've found a potential cause of this issue, but I do not know how to fix this. In 'C:\ProgramData\EA Desktop\Logs\EABackgroundService.log', I get these errors:
'8 [2023-05-12T21:03:03.318Z] PID: 2768 TID: 25884 ERROR (eax:😕ervices::localStorage::logOnError) Operation [reading]: Could not find file or could not create containing folder for category "IQ", file path [C:\ProgramData\EA Desktop\530c11479fe252fc5aabc24935b9776d4900eb3ba58fdc271e0d6229413ad40e\IQ]
10 [2023-05-12T21:03:03.320Z] PID: 2768 TID: 26324 ERROR (eax:😕ervices::localStorage::logOnError) Operation [reading]: Could not find file or could not create containing folder for category "IS", file path [C:\ProgramData\EA Desktop\530c11479fe252fc5aabc24935b9776d4900eb3ba58fdc271e0d6229413ad40e\IS]
11 [2023-05-12T21:03:03.320Z] PID: 2768 TID: 26496 ERROR (eax:😕ervices::localStorage::logOnError) Operation [reading]: Could not find file or could not create containing folder for category "CATS2", file path [C:\ProgramData\EA Desktop\530c11479fe252fc5aabc24935b9776d4900eb3ba58fdc271e0d6229413ad40e\CATS2]
16 [2023-05-12T21:03:03.322Z] PID: 2768 TID: 24296 INFO (eax:😕ervices::TelemetryDispatcher::Impl::logTelemetryEvent) Telemetry Event: [{"authenticated":false,"criticalOffline":true,"criticality":false,"disableCulling":false,"enabled":true,"offline":false,"params":{"category":"IQ","ecode":1,"estr":"Storage file doesn't exist","src":"decrypt"},"taxonomy":"user.cache.erro","throttleCount":0,"timestamp":"2023-05-12T21:03:03.318","weight":0.0}]
23 [2023-05-12T21:03:07.094Z] PID: 2768 TID: 24296 INFO (eax:😕ervices::TelemetryDispatcher::Impl::logTelemetryEvent) Telemetry Event: [{"authenticated":false,"criticalOffline":true,"criticality":false,"disableCulling":false,"enabled":true,"offline":false,"params":{"category":"IS","ecode":1,"estr":"Storage file doesn't exist","src":"decrypt"},"taxonomy":"user.cache.erro","throttleCount":0,"timestamp":"2023-05-12T21:03:03.320","weight":0.0}]
25 [2023-05-12T21:03:07.094Z] PID: 2768 TID: 24296 INFO (eax:😕ervices::TelemetryDispatcher::Impl::logTelemetryEvent) Telemetry Event: [{"authenticated":false,"criticalOffline":true,"criticality":false,"disableCulling":false,"enabled":true,"offline":false,"params":{"category":"CATS2","ecode":1,"estr":"Storage file doesn't exist","src":"decrypt"},"taxonomy":"user.cache.erro","throttleCount":0,"timestamp":"2023-05-12T21:03:03.320","weight":0.0}]'

@EA_Kent Can you or another EA Community Manager handle this? I had a lengthily conversation with EA Support last night, where I went through all of their troubleshooting steps, including uninstalling and re-installing the EA App with a registry and file cleanup between installs, same with all VC++ redistributables, re-installing or updating Graphics Card Driver, checking I have the latest version of DirectX, doing a clean boot, temporarily disabling Antivirus, and much more; I was advised to add my latest error to this bug report, as they're potentially related to each other (I.e: The EABackgroundService fails to create files, and so the EA App fails to start), and to get the attention of a Community Manager so this can be escalated, as none of the troubleshooting we tried, changed or fixed the issue.

@MilesSmilesD Yeah, and as of the most recent update from EA, "12.188.1.5443", its still an issue. I cannot play The Sims 4 or FIFA 23, and I also can't play EA Sports PGA Tour (I haven't even bought it, because why would I buy a game that I can't play?), so EA are missing out on my money (not that they probably care all that much!!), because they can't put together a functioning EA App for all.