Star Wars Battlefront II (Steam) fails to start/ silent crash to EA App
Proposed Title for the Forum:
Star Wars Battlefront II (Steam) fails to launch / silent crash to EA App / Exhaustive Troubleshooting done
Problem Description:
* The game launched via Steam briefly opens the loading screen or starts the process, then closes silently without any error message.
* The EA App pops up afterwards as if nothing happened.
* The game does not generate any configuration files on startup. The folder "STAR WARS Battlefront II" under Windows "Documents" is completely missing.
Troubleshooting steps performed (without success):
1. Launcher, Cache and Reinstallation
* Complete reinstallation of Steam and the EA App.
* Cleared EA App cache via App Recovery.
* Completely deleted EA App certificates and temporary files under LocalAppData.
* Removed old Origin folder remnants in ProgramData and AppData.
* Manually restarted the EABackgroundService and verified it is set to automatic start.
* Verified game file integrity via Steam multiple times.
2. System Environment and Drivers
* Updated all system and graphics drivers to the latest version.
* Created a new local Windows user with administrator privileges and attempted launch there.
* Moved the installation to the primary system drive (C:) to rule out symlink or secondary drive issues.
* Completely uninstalled and cleanly reinstalled ALL Visual C++ Redistributables (all versions from 2005 to current for both x86 and x64) as well as the full DirectX SDK and DirectX End User Runtimes (this fixed an initial 0xc000007b error with ActivationUI.exe but the silent crash persists).
3. Permissions and UAC (User Account Control)
* Ran Steam and EA App synchronously as administrator.
* Completely revoked admin rights for both launchers for testing.
* Tested asymmetrical permissions (EA App as Admin, Steam without).
* Strictly disabled compatibility mode for ActivationUI.exe and starwarsbattlefrontii.exe.
4. Folder Permissions and Antivirus
* Checked Windows Ransomware Protection (Controlled folder access) and set exceptions for the game.
* Disabled antivirus and whitelisted complete folder structures.
* Disabled OneDrive synchronization to rule out path redirections for the Documents folder.
* Manually created the folder structure under Documents ("STAR WARS Battlefront II\settings") to bypass permission issues during automatic creation.
5. Engine Workarounds and Interfaces
* Disabled all in game overlays (Steam, EA App, Discord).
* Forced DirectX 11 launch by manually creating the boot file ProfileOptions_profile with the parameter GstRender.EnableDx12 0.
* Set Intel OpenSSL Environment Variable for newer CPUs (OPENSSL_ia32cap = ~0x200000200000000).
* Manually triggered the game launch via Link2EA.exe, EALauncher.exe, and directly via EADesktop.exe.
* Verified and confirmed the link between the Steam and EA account in the web browser.
With this level of technical detail, I hope the developers or community managers will immediately recognize that the issue lies deep within the Frostbite engine or the API interface between Steam and EA. And yeah, I summarized everything I did with AI because I am completely burned out with this issue. It makes no sense that EA doesn't do anything about it, considering how many people have this exact problem and are asking for help on different platforms. But nothing happens.