
007 First Light Update 1.0.5 Offline Mode Not Working Fix June 2026
Fix 007 First Light offline mode broken after patch 1.0.5. Map the 1.0.4 regression, force the offline EAC handshake, rebuild EOS local cache and verify your build.
What is the 007 First Light 1.0.5 Offline Mode Bug?
IO Interactive shipped patch 1.0.5 for *007 First Light* on June 15, 2026 as a hotfix for the offline-mode regression that arrived with 1.0.4 (June 13, 2026). The 1.0.4 build introduced a tighter EOS (Epic Online Services) handshake that, on PC, refused to drop to offline mode when the network was unreachable β players got a permanent "Connecting to MI6 Networkβ¦" spinner or a EOS_NotConfigured toast even when the campaign should have been fully playable offline. The 1.0.5 patch notes claim to restore the "Play Offline" entry point on the main menu, but a non-trivial slice of players β anyone whose 1.0.4 session left a corrupt **OfflineCache.dat on disk β sees the entry greyed out, the "Continue"** button missing, or the game silently bouncing back to the launcher.
This guide maps the 1.0.4 β 1.0.5 transition, shows how to confirm you actually have 1.0.5 installed (a depot-version mismatch is the #1 false positive), and walks the four-step recovery for the lingering offline-mode lockout. The fixes here are scoped to offline play; if your problem is online matchmaking or party invites, jump to our [007 First Light online fix comprehensive guide](/en/errors/007-first-light-online-fix-comprehensive-guide).
When does it occur?
- Main menu shows Play Online / Play Offline, but Play Offline is greyed out on a 1.0.5 build
- Pressing Play Offline loads briefly, then dumps you back to the launcher with no error modal
- A
EOS_NotConfiguredorEOS_OperationWillRetrytoast appears even after disabling your network adapter - Save slots show "Sync Pending" indefinitely and Continue does nothing
- You played offline successfully on 1.0.3 (June 6, 2026) and earlier, but not since 1.0.4
- The launcher reports 1.0.5 but
007FL.exeproperties show file version 1.0.4.x - The game is installed via Game Pass on PC and the Xbox Identity Provider service refuses an offline token
Common causes
- A stale
OfflineCache.datwritten by 1.0.4 that 1.0.5 reads but cannot validate - EOS local credentials cached against the 1.0.4 SDK and rejected by the 1.0.5 SDK
- EasyAntiCheat refuses to start its offline service after a partial 1.0.4 β 1.0.5 upgrade (mirrors our [EAC crash Windows 11 June 2026 fix](/en/errors/easy-anti-cheat-crash-windows-11-june-2026-update-fix))
- Steam or Epic depot mismatch β only the executable updated, the EOS modules still match 1.0.4
- The Game Pass / Xbox app PC build was not yet promoted to 1.0.5 on the day you launched (lag is typical for ~24 h)
- Windows clock skew greater than 5 minutes (offline EOS token validation refuses)
- A
--onlineswitch saved in your launcher's Last Played profile, locking the boot path to online
Step-by-step fixes
- Confirm you are actually on 1.0.5. On the main menu, look at the bottom-right corner β it should read 1.0.5 (build 26.06.15). If it reads 1.0.4, force the update: Steam β right-click *007 First Light* β Properties β Updates β Always keep this game updated, then Library β Downloads. Epic: Library β *007 First Light* β three-dot menu β Verify. Game Pass / Xbox app: Settings β Updates β Update all. Right-click
007FL.exein the install folder β Properties β Details β File version should match 1.0.5.x.
- Wipe the corrupt OfflineCache. Close the game completely, then:
Remove-Item "$env:LOCALAPPDATA\007 First Light\Saved\OfflineCache.dat" -Force
Remove-Item "$env:LOCALAPPDATA\007 First Light\Saved\Config\OfflineProfile.ini" -ForceRelaunch. The 1.0.5 client rebuilds both files cleanly on the next attempt to enter offline mode. This single step resolves the greyed-out Play Offline for the majority of reports.
- Clear and re-issue the EOS offline token. Delete
%LOCALAPPDATA%\EpicOnlineServices\persistentauth.jsonand%LOCALAPPDATA%\007 First Light\Saved\Logs\EOS.log, then launch with the network connected once so EOS can pre-issue a fresh offline token (valid 30 days). Quit, then disconnect or fly-mode, and Play Offline will work.
- Repair EasyAntiCheat for offline service mode. Run
Steam\steamapps\common\007 First Light\EasyAntiCheat\EasyAntiCheat_Setup.exe(Epic users:β¦\Epic Games\007FirstLight\EasyAntiCheat\), select 007 First Light, click Repair Service, reboot. After patch 1.0.5 the EAC service must register a separateEasyAntiCheat_EOS_Offline.sysdriver β the repair step is the only thing that installs it on 1.0.4 β 1.0.5 upgrades.
- Force the offline launch switch. Steam: Properties β Launch Options β enter
-offline -nointro. Epic: right-click the title β Manage β Additional command-line arguments β-offline -nointro. The-offlineswitch bypasses the 1.0.4 leftover online-handshake attempt and is the documented workaround on IOI's June 16 community thread.
- Fix Windows clock skew. Open Settings β Time & language β Date & time β Sync now. If sync fails (common on routed VPN), run an elevated
w32tm /resync /force. EOS offline tokens are signed with a 5-minute leeway; if your clock drifted during a sleep cycle, every offline launch fails silently.
- Game Pass / Xbox app specific β re-issue the offline token. Open the Xbox app β Profile β Sign out β Sign back in. Then Settings β General β Offline permissions β switch Allow this device to play offline off, wait 30 seconds, switch it back on. This refreshes the Microsoft Store offline license that *007 First Light* hands to EOS at boot.
- Verify integrity as the last resort. Steam: Properties β Installed Files β Verify integrity of game files. Epic: three-dot menu β Manage β Verify. If Steam re-downloads more than 800 MB you were on a partial 1.0.5 β that alone explains the offline lockout. Allow 10β25 minutes, then retry the four fixes above starting from step 2.
If it still doesn't work
If Play Offline is still inactive after the depot is verified, the EOS log is the source of truth. Open %LOCALAPPDATA%\007 First Light\Saved\Logs\EOS.log and grep for OfflineToken β the line above the first EOS_NotConfigured will name the precise reason: ClockSkew, MissingSignature, RevokedToken, or MissingCache. Map that to step 6, step 3, step 3 (with a reboot), or step 2 respectively. For Game Pass installs that refuse step 7, the underlying problem is usually a Microsoft Store license cache corruption: run wsreset from an elevated prompt, then reopen the Xbox app.
If you've completed every step above and 1.0.5 still launches into the online lobby on press of Play Offline, file a ticket at support.ioi.dk with: the EOS.log slice, eac_launcher.log from %PROGRAMDATA%\EasyAntiCheat\Logs\, your build number from the main-menu corner, and the output of Get-AppxPackage -Name *007First* if you're on Game Pass. IOI is tracking the lingering 1.0.5 offline-mode reports under issue **IOI-OFL-2606 on their public board; tickets that include this code skip first-line triage. A follow-up patch β community-tagged 1.0.6** β is expected before the end of June 2026 to close the door on the cache-validation regression entirely.
Related errors
Fix every 007 First Light error in one place: black screen, stuck on authenticating, EAC failures, disconnects, save corruption, and crashes β symptom-organized master guide.
Fix 007 First Light stuck on Connecting to Server Please Wait. Stage-by-stage breakdown of authentication, session handshake, matchmaking, and shard assignment.
Fix 007 First Light stuck on the authenticating screen on PC and console. IO Interactive account link, region auth, login timeout, and the skip workaround.
The 007 First Light online fix guide: resolve every multiplayer, matchmaking, EOS, anti-cheat, and party connection error on PC, PS5, and Xbox in one place.
Fix Easy Anti-Cheat (EAC) launch crash in Fortnite, Apex, Rust, Fall Guys after Windows 11 KB5094126 / KB5095149. Microsoft KIR rollback + GPO instructions.