Unable to launch Past BattleEye ?
Am I the only one experiencing this? I have a 5070ti with an i7 14k .
When I launch the game through Steam, it goes through the updating , launching, via BattleEye , then it does nothing. A silent crash.
I have uninstalled and re-installed a couple times. Cleared cache in steam.
I have updated drivers, updated windows, even went into BIOS to make sure TPM was enabled. I went into the firewall settings and allowed marathon.exe + the launcher.exe as well as battleeye.exe , tried uninstalling and re-installing battleeye etc via program files.
I'm wondering if this has to do with WINscp, or UE5? In the eventviewer, i am seeing a kernel error when the app crashes / doesn't launch. This still happens after a Reboot and a cold launch, there are also no start-up apps etc..
Unplugged second monitor and Capture card.
I disabled some other windows security features as well just to test and still nothing has worked.
I bought it last night and haven't been able to play. Anybody else having this problem?
Comments
Hi there,
Thank you for reaching out.
Since you’re crashing right after the BattleEye splash with no window ever opening, it’s most likely either:
A driver / system‑level issue (especially with the kernel error in Event Viewer), or
Something still blocking BattleEye or the game at startup.
A few focused things you can try next:
Run as admin / disable overlays
Right‑click your Steam shortcut → Run as administrator, then try launching Marathon.
Fully close Discord / Steam / NVIDIA / AMD overlays, capture tools, and any OSD/monitoring apps (Afterburner, RTSS, etc.), then test again.
BattleEye & anti‑virus
In …\Marathon\BattlEye, right‑click the installer and Run as administrator to reinstall BattleEye.
Temporarily disable or create exceptions in any third‑party antivirus/endpoint/security tools for:
marathon.exe
the launcher executable
bedaisy.sys / BattleEye services
Clean boot test
Try a clean boot of Windows (no non‑Microsoft startup services), then launch Steam → Marathon. This helps rule out background software conflicts.
Hello,
I have the same problem and tried the solutions you suggested. Is there a way to access Logs (from Marathon, Battle Eye or something else) to catch where the gmae is being stopped, and maybe guess what's stopping it from launching?
Hi, and thank you for your response Bungie. I have tried all of the above recommended options but to no avail. I did everything recommended except a clean boot / fresh install of Windows, because I just have too many resources and assets I'm developing personally to install a clean version of windows to get this particular game to launch. I'm sure it'll work soon with a patch, but I am contemplating on just going ahead and doing a clean install of Windows and seeing if this solves the problem.. That to me is a last resort option and also I know others may not have the same options or consider them. I do have a newer build PC with good specs, so I just don't see where the problem would be other than developer tools being picked up by the marathon.exe / launcher .
After HOURS of attempting to figure out the problem, I've found the solution AVX was disabled in my BIOS. I enabled it and it worked, instantly..
Please sign in to leave a comment.