Ok I can provide an update.
I manged to get SWBF2 to launch by creating a new local Windows User Profile, opening the EA App with it, and the game would launch fine, as I outlined up thread here (https://answers.ea.com/t5/STAR-WARS-Battlefront-II/Battlefront-2-won-t-launch-with-new-EA-app-PC/m-p/12351629#M105696). Hence for the last 3 weeks or so that is how I've been playing it.
Yesterday, my PC downloaded and installed a Windows 10 Optional update, specifically update KB5023773 (link to update on MS's site - https://support.microsoft.com/en-us/topic/march-21-2023-kb5023773-os-builds-19042-2788-19044-2788-and-19045-2788-preview-5850ac11-dd43-4550-89ec-9e63353fef23) which was released on 21 March 2023. When I started up my PC today, I tried launching the game and guess what? It launched and I could play it like I used to with EA Origin on my usual Windows Profile.
So if you are still having launch problems, see if installing the update I mentioned helps resolve your issue.
I too purchased both Battlefront and Battlefront II from Steam some time ago. At first, both ran just fine. Then they stopped loading! I searched the net for answers and tried just about every suggested fix - all to no avail. I contacted EA support and after many emails and a phone call, they too could not resolve the problem. So, I gave up, and resigned myself to the fact that both games, for some reason, just weren't going to be played any more. Then, just out of interest, I was reading the posts on this Forum, and saw this one which said that after a Windows Update the games were working. I have Windows 11, but checked for the update, and saw it was installed. I clicked on the game icons - and yes - both games magically ran with no problem! Amazing, I thought. Obviously a Windows problem that has at last been resolved. I checked from time to time - and indeed, both games running just fine. However, now for the bad news. After the latest Windows Update (25/04/2023), both games have stopped loading again! Anyone got any ideas? or do we just wait for another random Windows Update to sort the problem out for us!
