Apex Crashes On Launch | Fix Launch Crashes Fast On PC

If the game shows a splash screen, opens a black window for a moment, then drops you back to desktop, you’re dealing with a launch crash. It can feel unpredictable, yet the crash usually happens during file validation, anti-cheat startup, or graphics setup. Steps below.

Start With A Clean Launch Test

Before you reinstall anything, run a short test that removes the usual noise. It gives you a clear signal on what’s failing, and it prevents you from changing three things at once and losing the trail.

• Restart The PC Once — Fully reboot so background hooks and stuck game services reset.
• Unplug Extra USB Gear — Leave only a mouse and one controller to rule out driver conflicts.
• Close Overlay Apps — Shut Discord overlay, GeForce Experience overlay, Steam overlay, and any screen recorder.
• Check Free Disk Space — Keep at least 20 GB free on the drive that holds the game and Windows temp files.
• Launch With Nothing Else Running — Close browsers with many tabs, RGB tools, and hardware monitors for this test run.

If the crash still happens, watch what you see right before the drop. A fast clue can save an hour of guessing. Use the table to match the symptom to the first fix that fits.

Clue	Likely Trigger	First Fix
Closes after Easy Anti-Cheat screen	Anti-cheat blocked by overlay or security tool	Repair anti-cheat, then clean boot
Black screen, then desktop	Driver crash during shader load	Update GPU driver, clear shader cache
Instant crash with an error code	Corrupt files or missing runtime	Verify files, install Visual C++
Stuck on splash screen	Bad config file or cloud sync loop	Reset local settings folder
Crash only after a patch	Hotfix gap or server-side bug	Check status pages, wait for update

Apex Crashes On Launch On PC

On PC, most launch crashes trace back to corrupt game files, a bad start flag, or a third-party hook that trips the anti-cheat layer. Start with the platform tools that fix those fast, then move to local cleanup.

Fix The Install On Steam Or EA App

Steam and the EA app both have repair tools that re-check your install without a full download. Run the repair once, then launch the game with overlays still off.

• Verify Files In Steam — Open Library, right-click Apex, go to Properties, then Installed Files, then run verify.
• Repair In The EA App — Open your Library, pick Apex, open Manage, then run Repair and wait for it to finish.
• Remove Beta Branches — If you joined a beta or test branch, switch back to the default branch before testing.

Remove Launch Options And Overlays

Launch options can solve one issue and create another after an update. If you added command-line flags months ago, wipe them for the test. Keep overlays off until you reach the lobby once.

• Clear Custom Launch Arguments — Remove options such as window mode flags, fps limits, and old DirectX flags.
• Disable In-Game Overlay Toggles — Turn off Steam overlay, Discord overlay, GeForce overlay, and Xbox Game Bar.
• Turn Off Third-Party Injectors — Pause reshade tools, macro apps, and performance overlays for the test.

If apex crashes on launch right after these steps, go next to local settings. Corrupt configs can crash the game even when the install is clean.

Repair Game Files And Local Settings

Apex stores settings, logs, and cached shaders outside the main install folder. A damaged file in that folder can break startup, and a file verify will not fix it. Resetting these files is safe since the game can rebuild them.

Reset The Apex Settings Folder

On Windows, Apex settings live under your Saved Games or user profile folders. The exact path can vary by install method, so use a search inside your user folder for “Apex” and “settings.cfg”. Copy the folder to a backup spot, then clear the active folder so Apex can create a fresh set on the next launch.

• Back Up Your Settings First — Copy the whole Apex settings folder to your desktop so you can restore binds later.
• Delete Config And Cache Files — Remove only the files in the folder, not your entire user profile.
• Launch Once And Rebuild — Start the game, reach the lobby, then reapply settings in small batches.

Clear Shader Cache And Temp Files

A driver update or big game patch can leave old shader cache entries behind. Clearing them forces a rebuild and can stop the black-screen crash during startup.

• Clear GPU Shader Cache — Use your GPU driver panel settings or Windows disk cleanup to remove shader cache files.
• Empty Windows Temp Folder — Press Win+R, type %temp%, delete what will delete, then reboot once.
• Disable Cloud Sync For One Test — If your platform syncs settings, pause sync once to stop a bad file from coming back.

Run Apex With Simple Permissions

Startup can fail if the game can’t write logs or cache files. A simple permission check takes one minute.

• Run As Administrator Once — Right-click the game or launcher, run as admin, then test a single launch.
• Whitelist The Game Folder — Add the install folder to your security tool exclusions for the test, then re-enable scans.
• Check OneDrive Folder Moves — If your Documents or Saved Games moved into OneDrive, try a local path for the test.

Driver, DirectX, And Windows Conflicts

When Apex launches, it loads the graphics stack, audio stack, and several runtime libraries at once. A weak link there can crash the game before you see a menu. This section keeps the steps tight so you can do them in order and stop when the launch is stable.

Update Or Clean Install The GPU Driver

A driver update is the fastest win for a launch crash tied to a black screen or instant desktop drop. If you recently updated and the crash started right after, a clean driver install can fix leftover files.

• Update From The GPU Maker — Download the newest driver from NVIDIA, AMD, or Intel, then reboot after install.
• Use Clean Install Options — Pick the installer option that resets driver settings to default where available.
• Undo Overclocks For Testing — Reset GPU and RAM tweaks to stock for a single test run.

Repair Windows Game Dependencies

Apex relies on Visual C++ runtimes and DirectX components. If those are missing or corrupt, the game can crash on launch with a short error or no message at all.

• Install Visual C++ Redistributables — Install the current x64 package, then reboot and test launch.
• Run Windows Update — Install pending updates, restart, then test again before changing anything else.
• Check System File Health — Run sfc /scannow in an admin Command Prompt, then reboot after it finishes.

Use A Clean Boot To Find Conflicting Apps

If the crash stops in a clean boot, a background app is hooking into the game at launch. You can then add services back in batches until the crash returns, which points to the conflict.

1. Open System Configuration — Press Win+R, type msconfig, then press Enter.
2. Hide Microsoft Services — Open the Services tab and tick the box to hide Microsoft services.
3. Disable Remaining Services — Click Disable all, apply, then restart the PC.
4. Disable Startup Apps — Open Task Manager, disable non-Windows startup items, then restart.
5. Test Apex Launch — Launch the game once, then re-enable items in small groups until you find the conflict.

Easy Anti-Cheat And Integrity Errors

Many launch crashes happen right as Easy Anti-Cheat starts. You might see an integrity error, a short code, or a crash with no warning. The fixes below keep your install intact while resetting the parts that anti-cheat relies on.

Repair Easy Anti-Cheat

Most installs include an EasyAntiCheat setup tool inside the game folder. Running its repair action can fix broken service files and permissions.

• Open The EasyAntiCheat Folder — Browse to the Apex install folder and open the EasyAntiCheat subfolder.
• Run The Setup Tool — Launch the setup executable, pick Apex Legends, then run the repair action.
• Reboot Before Testing — Restart the PC so the service reloads clean, then launch Apex once.

Remove Hooks That Trigger Anti-Cheat

Anti-cheat can block launch when it detects injected overlays, debuggers, or certain capture tools. Even harmless tools can look suspicious during startup.

• Close Hardware Monitor Tools — Exit tools that hook GPU stats into games, then test launch.
• Pause Screen Capture Tools — Turn off recorders and streaming apps until you reach the lobby.
• Check Security Tool Alerts — If your antivirus logged a block on Apex or EAC files, restore and whitelist those files.

Know When It’s A Known Bug

Sometimes the crash is tied to a fresh update, and many players hit it at the same time. If you can’t reach the lobby after clean repairs, check EA’s known-issues tracking and recent crash threads on the official forums. If a hotfix is pending, your smart move is to stop changing your system and wait for the patch.

Console Fixes And Patch Day Checks

Console launch crashes are usually tied to a bad update install, a corrupted local cache, or a sign-in issue. You can fix most of them without losing your account progress.

PlayStation Steps

• Power Cycle The Console — Shut down fully, unplug for one minute, then boot and test launch.
• Clear Stored Cache Data — Restart the console and try again before reinstalling the game.
• Reinstall If The Patch Failed — Delete Apex, reinstall, then let the full update finish before launch.

Xbox Steps

• Do A Full Shutdown — Hold the power button, wait for the console to turn off, unplug, then restart.
• Clear Local Saved Data Cache — Use the storage settings to clear local data, then sign back in and sync.
• Move The Install Drive — If you use external storage, move Apex to internal storage and test.

Patch Day Checklist

If apex crashes on launch right after a new season, event, or hotfix, treat it as a patch-day problem until proven otherwise. You want to rule out server-side trouble before you wipe your install.

• Check Service Status Pages — Confirm the platform network is up, then check EA’s status and known issues.
• Wait For A Small Hotfix Window — Many launch bugs get a quick update within hours or a day.
• Capture The Error And Dump File — Save the error code, take a photo, and keep the crash dump if one is created.

After you can reach the lobby, bring your usual tools back one at a time. Turn on one overlay, play a match, then add the next. If the crash returns, you’ve found the trigger without guesswork.