007 First Light Won't Launch or Crashes on PC
Fix 007 First Light not launching, black screen, and crash on startup on PC. Force the dedicated GPU, update drivers, disable overlays, and clear the shader cache.
What is the 007 First Light "Won't Launch" Error?
007 First Light is the IO Interactive James Bond origin story released on May 27, 2026 for PC (Steam and Epic), built on the studio's Glacier engine — the same engine behind Hitman. On many PCs the game shows no error at all: you click Play, the launcher closes, and nothing happens — no window, no crash dialog. Others get a black screen with audio still playing, a freeze on the IO Interactive splash, or an instant crash to desktop.
IO Interactive acknowledged the "launch and nothing happens" bug on its [official Known Issues page](https://007firstlight-support.zendesk.com/hc/en-us/articles/36203682496413-007-First-Light-Known-Issues) within a day of release and listed it as "under investigation." In the meantime, the cause on the overwhelming majority of affected machines is the Glacier engine launching on the integrated GPU instead of the dedicated graphics card, compounded by overlay injection and a stale shader/pipeline cache.
When does it occur?
- Immediately after clicking Play in Steam or Epic — the process exits silently with no window
- A black screen while the intro / helicopter cutscene audio keeps playing
- A freeze on the IO Interactive or Glacier splash logo
- Instant crash to desktop on laptops that have both an iGPU and a dedicated GPU
- After a GPU driver update or a Windows graphics-settings reset
- On the very first launch, before the shader pipeline cache has finished building
Common causes
- Glacier engine rendering on the integrated GPU (Intel UHD / AMD Radeon Graphics) instead of the NVIDIA/AMD dedicated card
- Outdated GPU driver missing the May 2026 day-one game profile
- Steam and/or Discord overlay injection conflicting with Glacier's DX12 renderer
- A corrupt
pipeline_cachefolder from an interrupted first-launch shader build - Resizable BAR / Smart Access Memory causing a DX12 init hang on some boards
- Fullscreen-exclusive mode failing to grab the display (black screen)
- Missing or out-of-date Visual C++ runtime / DirectX components
Step-by-step fixes
- Force the dedicated GPU (the #1 fix) — Settings → System → Display → Graphics → Add desktop app → browse to the game EXE (
...\steamapps\common\007 First Light\007FirstLight.exe). Select it → Options → High performance → Save. Reboot and relaunch. - Update your GPU driver with a clean install — NVIDIA: install the latest Game Ready driver and tick Perform a clean installation. AMD: Adrenalin → choose Factory Reset install. Reboot afterward.
- Delete the settings and shader cache — press Win+R, go to
%LOCALAPPDATA%\IO Interactive\007 First Light\, then deletesettings.iniand the entirepipeline_cachefolder. The game rebuilds clean copies on next launch. - Disable the Steam and Discord overlays — Steam → right-click 007 First Light → Properties → uncheck Enable the Steam Overlay while in-game. Discord → Settings → Game Overlay → toggle off Enable in-game overlay.
- Verify the game files — Steam → right-click 007 First Light → Properties → Installed Files → Verify integrity of game files. On Epic: Library → ⋯ → Manage → Verify.
- Force windowed mode for a black screen — launch, then press Alt+Enter. If you only see a black screen with audio, set the in-game resolution to 1280×720 for the intro, get control of Bond, then raise it back up.
- Disable Resizable BAR / Smart Access Memory in your motherboard UEFI/BIOS (Advanced → PCIe → Re-Size BAR Support → Disabled) if the game hangs at DX12 init on RTX 40/50 or RX 7000/9000 cards.
- Repair the runtimes — reinstall the latest [Microsoft Visual C++ Redistributable](https://aka.ms/vs/17/release/vc_redist.x64.exe) (x64) and run the DirectX End-User Runtime web installer, then reboot.
If it still doesn't work
If the process still exits silently, run the game once as administrator and add an exclusion for the install folder in Windows Security → Virus & threat protection → Exclusions — Glacier's anti-tamper layer is occasionally killed by real-time protection. Check Event Viewer → Windows Logs → Application for an Application Error citing ntdll.dll or your GPU driver DLL (nvwgf2umx.dll for NVIDIA), which confirms a driver-level crash rather than a launcher issue.
For shared GPU-driver crashes that also hit other DX12 titles, see our guides on the [RTX 50-series video engine timeout](/en/errors/nvidia-rtx-50-series-driver-crash-video-engine-timeout), the [RTX 5070 Ti black screen driver crash](/en/errors/nvidia-rtx-5070-ti-driver-crash-black-screen), and the [DXGI_ERROR_DEVICE_HUNG fix for all games](/en/errors/dxgi-error-device-hung-fix-all-games). If 007 First Light still won't launch after every step, open a ticket on the IO Interactive support portal and attach your DxDiag report.
Related errors
Fix NVIDIA RTX 5090 and 5080 driver crashes with VIDEO_ENGINE_TIMEOUT_DETECTED error. Resolve black screens, game crashes, and DLSS instability on RTX 50 series GPUs.
Fix NVIDIA RTX 5070 Ti black screens, driver crashes, and TDR errors. DDU clean install, BIOS settings, PCIe Gen 5 fixes, and power connector checks.
Fix DXGI_ERROR_DEVICE_HUNG (0x887A0006) crashing all games on Windows 10 and 11. TDR registry fix, GPU underclocking, DirectX 11 fallback, and driver solutions.