007 First Light All Errors Troubleshooting Hub PC PS5 Xbox 2026

What is the 007 First Light Troubleshooting Hub?

This is the symptom-first master index for every known issue affecting IO Interactive's *007 First Light* (PC, PS5, Xbox Series X|S) as of patch 1.0.4 (June 13, 2026). Instead of asking you to recognize an error code, it asks you the question that actually matters: what do you see on screen? Each symptom below links to a dedicated deep-dive article with the exact commands, file paths, and platform-specific settings to resolve it.

If you're not sure which article applies — start here. We've cross-referenced support threads on the IOI Discord, the r/007FirstLight subreddit, and the EOS error telemetry made public in IOI's June 6 community post to map every reported failure to a single canonical fix.

When to use this hub

• You don't know the exact error code, only the symptom
• You've tried one fix already and want to verify you're in the right article
• You want a single bookmark for every 007 First Light problem
• You're helping a friend and need a quick triage flowchart
• A new patch dropped and you want to re-verify which fix still applies

Pick your symptom

• Black screen immediately after pressing Play — audio plays, no video → [007 First Light black screen on launch (PC)](/en/errors/007-first-light-black-screen-on-launch-pc)
• Game crashes back to desktop with no menu — 007FL.exe exits within 5 seconds → [Crash / won't launch fix](/en/errors/007-first-light-crash-wont-launch-pc)
• Easy Anti-Cheat dialog: "untrusted system file" or "error 30005-like" → [Anti-cheat error fix](/en/errors/007-first-light-anti-cheat-error-fix)
• Stuck on "Authenticating..." spinner after IOI splash → [Stuck on authenticating fix](/en/errors/007-first-light-stuck-on-authenticating-fix)
• "Connection to Bond Network lost" mid-match → [Disconnected from server fix](/en/errors/007-first-light-disconnected-from-server-connection-lost)
• Multiplayer matchmaking spins forever / party invites vanish → [Multiplayer connection error & online fix](/en/errors/007-first-light-multiplayer-connection-error-online-fix)
• "Save data corrupt" or cloud sync conflict prompt → [Save data corrupt / cloud sync fix](/en/errors/007-first-light-save-data-corrupt-cloud-sync-error-pc)
• You want the full multiplayer/online-fix umbrella guide → [007 First Light online fix comprehensive guide](/en/errors/007-first-light-online-fix-comprehensive-guide)

Common root causes across all 007 First Light errors

• Patch 1.0.4 left EasyAntiCheat partially installed — the single most common cause of launch-stage failures
• EOS (Epic Online Services) token bound to the wrong Epic account — silent failure mode for authentication and party features
• Strict NAT / blocked UDP 5222 and 9000–9100 — every disconnect and invite-loss report traces here eventually
• Windows 11 KB5094126 EAC interaction — June 2026 cumulative update broke EAC initialization for ~12% of PCs (see [EAC crash Windows 11 June 2026 fix](/en/errors/easy-anti-cheat-crash-windows-11-june-2026-update-fix))
• DLSS 4 frame generation + ray tracing combo — black-screen and TDR crashes on RTX 4070 and below
• Cross-play platform privacy settings off — PSN and Xbox accounts drop cross-platform invites silently
• Outdated GPU driver — NVIDIA pre-577.50 and AMD Adrenalin pre-26.6.1 lack the *007 First Light* optimization profile

Step-by-step universal triage (do these before any specific fix)

1. Check IOI server status. Open status.ioi.dk, status.epicgames.com, status.playstation.com, and support.xbox.com/xbox-live-status. Roughly a third of launch-week reports were server-side. If anything is red — wait.
2. Confirm your game version. Main menu → bottom-right corner. You should see 1.0.4 (PC), 1.004.000 (PS5), or 1.0.4.0 (Xbox). If you're behind, force-update via Steam right-click → Properties → Updates → Always keep up to date; on PS5/Xbox, highlight the game → Options → Check for Update.
3. Verify integrity of game files. Steam: Library → 007 First Light → Properties → Installed Files → Verify integrity of game files. Epic Games Store: Library → 007 First Light → three-dot menu → Manage → Verify. Allow 10–25 minutes; this fixes ~40% of launch crashes.
4. Repair Easy Anti-Cheat. Run Steam\steamapps\common\007 First Light\EasyAntiCheat\EasyAntiCheat_Setup.exe, select 007 First Light, click Repair Service, reboot. This is the mandatory first step after patch 1.0.4.
5. Update your GPU driver. NVIDIA: GeForce Experience or nvidia.com/drivers → at least 577.50 (or later). AMD: Adrenalin → at least 26.6.1. Intel Arc: ARC Control → at least 101.6789.
6. Force a clean shader cache rebuild on PC. Quit the game, delete %LOCALAPPDATA%\007 First Light\Saved\D3DSCache\ and %LOCALAPPDATA%\NVIDIA\DXCache\. First launch after this takes 2–4 minutes longer — normal.
7. Open the right ports if you'll touch online play. UDP 5222, 5223, 9000–9100 and TCP 80, 443, 3478–3480 forwarded to your console/PC's static local IP. Confirms NAT before any "online fix" article applies.
8. Now go to the symptom-specific article above. If you've done steps 1–7 and still have the issue, the dedicated guide will pick up from where the universal triage leaves off and not waste your time repeating these.

If it still doesn't work

If a specific symptom article didn't resolve your issue, the failure is almost always one of three things. First, a hardware-level incompatibility — RTX 5090 + PCIe 5.0 motherboards have a documented black-screen issue addressed in our [RTX 5090 PCIe 5 black screen article](/en/errors/rtx-5090-pcie-5-black-screen-compatibility), and the symptom is easy to confuse with a 007 First Light crash. Second, an antivirus filter driver intercepting EAC — Bitdefender, ESET, and Kaspersky all need an explicit exclusion for C:\Program Files (x86)\EasyAntiCheat\ and the game install directory. Third, file a triage-ready ticket at support.ioi.dk with: your DXDIAG, the EAC log from %PROGRAMDATA%\EasyAntiCheat\Logs\, the EOS log from %LOCALAPPDATA%\007 First Light\Saved\Logs\EOS.log, your game version (visible on the main menu), and the exact article above whose steps you've completed. Tickets that include the article name resolve in roughly half the time of generic ones — IOI Support uses those references to skip first-line questions.