007 First Light Stuck on Authenticating Screen Fix

What is the 007 First Light "Stuck on Authenticating" Error?

After the 0.6 server-side patch rolled out the week of June 1, 2026, a large share of 007 First Light players on PC and console hit the main menu screen and freeze on a spinning "Authenticating..." indicator — usually for 90 seconds, then either a silent return to the press-any-button screen or a generic Unable to reach IO Interactive services toast. The game itself never crashes, the campaign-only "Press X to skip" shortcut never appears, and the Bond Pass, friends list, and contracts hub all stay locked behind the auth gate.

The root cause is IO Interactive's identity service (IOI Account) handshake timing out before Glacier hands the session token to the platform layer (Steam, Epic, PSN, Xbox Live). IOI confirmed on its [Known Issues page](https://007firstlight-support.zendesk.com/hc/en-us/articles/36203682496413-007-First-Light-Known-Issues) that EU and SA region auth servers were intermittently dropping handshakes after the patch. The fixes below cover both the workaround that lets you reach the campaign immediately and the permanent account-link repair.

When does it occur?

• Immediately on the title screen after pressing any key — the "Authenticating..." spinner never resolves
• After linking a new IOI Account to a fresh Steam, Epic, PSN, or Xbox profile
• When the platform region (Steam/PSN account country) differs from the IOI Account region
• After a console primary-account swap on PS5 or Xbox Series X|S
• During EU prime-time hours when the IOI auth pool gets saturated
• When two-factor authentication on the IOI Account hasn't been confirmed via the email link

Common causes

• IOI Account servers in EU/SA region returning HTTP 502 to the platform handshake
• Steam / Epic offline mode silently engaged after a network blip
• IOI Account email never verified — the back end refuses to issue a session token
• A regional mismatch between the platform store country and the IOI Account country
• IPv6 routing problem on residential ISPs (Comcast/Free/Orange) blocking the WebSocket leg of the handshake
• DNS resolution failing for auth.ioi.dk or identity.ioi.dk because of a stale local DNS cache
• A console primary-account change that invalidated the cached entitlement

Step-by-step fixes

1. Use the campaign "Skip Auth" workaround first — at the spinning indicator, press Spacebar (PC), Options/Menu (PS5/Xbox), or + (Switch 2). The on-screen prompt is currently missing on patch 0.6 but the input still registers and drops you into single-player offline mode so you can play the campaign while the back end recovers.
2. Verify your IOI Account email — go to [account.ioi.dk](https://account.ioi.dk), sign in with the email you used to link, and click the verification banner. An unverified account silently fails the handshake even though the in-game UI never says so. Restart the game after verifying.
3. Force a clean platform login — Steam: top-left menu → Sign out → sign back in (this refreshes the platform ticket Glacier sends to IOI). Epic: log out / log back in from the launcher. PS5: Settings → Users and Accounts → Sign Out → Sign back in. Xbox: Profile → Sign out → Sign in.
4. Re-link the IOI Account in-game — from the title screen press the Account option (top-right gear icon on PC, Y on Xbox, Triangle on PS5) → Unlink Platform Account → confirm → re-link. This forces a fresh handshake instead of replaying the cached, expired token.
5. Flush DNS and switch to Google or Cloudflare DNS on PC — open an admin PowerShell and run ipconfig /flushdns and Clear-DnsClientCache. Then in Network Adapter settings, set DNS to 1.1.1.1 and 8.8.8.8. On router/console, set the same DNS in network settings.
6. Disable IPv6 on the active adapter — Control Panel → Network and Sharing Center → adapter → Properties → uncheck Internet Protocol Version 6 (TCP/IPv6) → OK. On PS5/Xbox, set the connection to IPv4 only in Network Settings. This is the single most common fix on Free, Orange, Comcast, and Virgin Media connections.
7. Check the IOI service status before retrying — open the [IO Interactive Service Status](https://ioi.dk/status) page. If the Identity service is yellow or red, the auth pool is saturated; queue up the campaign offline (step 1) and retry online auth after 20-30 minutes.
8. Switch your IOI Account region to match your store region — log into [account.ioi.dk](https://account.ioi.dk) → Profile → Country. A US Steam account paired with an EU-region IOI profile triggers a region-mismatch loop that the auth server logs as an immediate handshake reject.

If it still doesn't work

If you still get the spinner after every step, capture the HAR log from the in-game network panel (Settings → Network → Export Diagnostic on PC builds 1.0.4.0 and later) and attach it to a [support ticket on the IOI portal](https://007firstlight-support.zendesk.com/hc/en-us). The team has been actively responding to the auth issue threads with manual account resets. Avoid creating a second IOI Account to "start fresh" — the platform link is one-to-one and a duplicate locks both accounts out for 24 hours.

If the campaign skip workaround also fails, the game is hitting the [007 First Light won't launch fault](/en/errors/007-first-light-crash-wont-launch-pc) further upstream — verify game files and force the dedicated GPU first. If you reach the lobby but matchmaking still throws a Connection to multiplayer services failed error, the next leg is the [007 First Light multiplayer connection error](/en/errors/007-first-light-multiplayer-connection-error-online-fix) caused by the same IOI back end.