@HandsUpRunIt First, please uninstall Jedi Survivor and the EA App with Revo Uninstaller (the free version is fine).
Restart your computer, and before reinstalling the App, temporarily disable your antivirus. As long as you're not doing anything else at the same time, your computer should be safe. Even if you haven't installed an antivirus, please check the Task Manager anyway—many prebuilt computers come with one pre-installed.
Install the App, and create a new folder where you'll install Jedi Survivor. This folder should be on the root level of the drive of your choice: C:\Games is fine, but not C:\Program Files\Games. Choose that folder when installing JS, and try to launch the game once before reenabling the antivirus. If it works, you can set exceptions for the game and EADesktop.exe.
I tried the steps above, did not work. I've tried everything at this point- probably have reinstalled the game 20 times- full windows 11 reinstall, multiple installations of various windows C++ redistributes, etc. Nothing has worked.
EA told me the developers are "Aware of the issue, and to be patient.". They act like there is a fatal flaw somewhere in EA or the game, and that essentially I'm unhelpable. There is an entire thread with 120 responses of people that can't get past this error (https://answers.ea.com/t5/Technical-Issues/How-to-fix-Jedi-Survivor-quot-Your-Game-Failed-to-Launch-error/td-p/12512359).
It's been months, the game has not launched once since I bought it on day 1 of its release.
Attached is my DxDiag- if there is a soul out there willing to try to help, let me know.
Thanks-
@LancetMage Your error is different than the one in the original post, and it might be an EA-side issue that you can't fix on your own. I don't know either way; I'm just saying it's possible that there isn't in fact a solution here.
Still, try setting your monitor to run at 3840x2160, its native mode, rather than its current 4096x2160. Jedi Survivor is finicky about resolutions.
Your dxdiag lists a number of generic Windows errors, which is odd after a full reinstall of Windows. Did you create a fresh ISO of the newest build of Windows 11, or did you use another approach?
