# Fortnite client: process starts but never opens a window (intermittent, ~50% of launches)

**URL:** <https://forums.unrealengine.com/t/fortnite-client-process-starts-but-never-opens-a-window-intermittent-50-of-launches/2857137>\
**Category:** Issues and Bug Reporting\
**Tags:** Status-Open, unreal-editor-for-fortnite, fortnite-creative, fortnite\
**Created:** [November 17, 2026, 2:18pm UTC](https://forums.unrealengine.com/t/fortnite-client-process-starts-but-never-opens-a-window-intermittent-50-of-launches/2857137 "2026-11-17T14:18:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Wertandrew](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/wertandrew/32/916192_2.png) [@Wertandrew](https://forums.unrealengine.com/u/Wertandrew)\
**Post date:** [November 17, 2026, 2:18pm UTC](https://forums.unrealengine.com/t/fortnite-client-process-starts-but-never-opens-a-window-intermittent-50-of-launches/2857137/1 "2026-11-17T14:18:33Z")

</div>

### Summary

- The Fortnite launcher runs, and EAC reports “Launcher finished with: 301, ‘Easy Anti-Cheat successfully loaded  
in-game’”.
- The game process (FortniteClient-Win64-Shipping.exe) starts but never creates a window.
- EAC log after 60 s: “Exit defer time crossed, the bootstrapper will leave the visible state despite the game  
window not being visible.”
- The hung game process:
  - writes no FortniteGame.log (the previous run’s log stays closed);
  - has no TCP or UDP sockets;
  - uses ~0 CPU (0.1 s over 5 s), has 19 threads and ~760 MB working set, and reports Responding = True;
  - stays like this indefinitely, until killed.

- Nothing is written to the Windows Application event log (no crash or WER entry).
- On a good launch, the window appears after 12-26 s. On a bad launch it never appears. Out of ~110 launches since  
2026-11-13, about half fail.
- The launcher-side log is identical for good and bad launches, up to “running fortnite”.

### Please select what you are reporting on:

Unreal Editor for Fortnite

### What Type of Bug are you experiencing?

Live Edit

### Steps to Reproduce

Open a UEFN project and start a session (Launch Session / live edit), or launch Fortnite from the Epic launcher.  
If the Fortnite window opens within ~30 s, close it and launch again.  
Repeat. On the affected PC, about every second launch hangs. It’s not 100% repro, but common.

### Expected Result

The Fortnite client window opens (normally after 12-26 s) and the session connects.

### Observed Result

No window ever appears. UEFN stays on “session loading” and times out after ~5 min because no game client connected.  
EAC log: Launcher finished with: 301, ‘Easy Anti-Cheat successfully loaded in-game’, then after 60 s: Exit defer time crossed, the bootstrapper will leave the visible state despite the game window not being visible.  
The FortniteClient-Win64-Shipping.exe process stays alive indefinitely:  
no FortniteGame.log is written;  
no TCP/UDP sockets, no audio session;  
no GPU device: Windows’ “GPU Engine” counters list no entry for it on either adapter;  
~0 CPU, ~760 MB working set, 19 threads, Responding = True.  
Thread states (read with WMI, no debugger), identical on every hang: all 19 threads are Waiting and none Suspended, so the process was resumed. Wait reasons: 15 x UserRequest, 2 x reason 37, 1 x 4, 1 x 15. The parent FortniteClient-Win64-Shipping\_EAC\_EOS.exe is still alive.  
Nothing appears in the Application or System event log (no crash, WER or display-driver reset).  
The launcher-side log is identical for good and bad launches.  
Only fix: kill the client in Task Manager and launch again. Restarting UEFN alone doesn’t help.

### Platform(s)

PC

### Additional Notes

System: Windows 11 Pro 26200 x64, hybrid laptop with Intel Graphics (driver 32.0.101.6629) and NVIDIA RTX 5090 Laptop GPU (driver 32.0.16.1074). Fortnite client build installed 2026-11-12; EAC EOS bootstrapper 2.0.0.  
Ruled out:  
Antivirus: with Avast folder exceptions it hung 2 of 4 launches, and with all Avast shields off 3 of 5.  
GPU / display driver: no device is ever opened, and there are no driver events.  
Windows updates: none since 2026-10-19.  
Reboots: it still happens after them.  
The EAC module download: “No update needed”.  
The same signature was first seen on 2026-11-04; failures became frequent from 2026-11-14.  
Dismissed Windows firewall prompts left 16 Inbound Block rules named “Fortnite”. The first appeared after the first hang, so they don’t look like the cause.  
Questions:  
Is this FORT-1095451, and is a fix scheduled?  
What early start-up wait between the EAC bootstrapper and the game process can block every thread before the log opens?  
Is there a known issue on hybrid Intel + NVIDIA laptops?  
Should the Inbound Block rules be removed?  
Related: “Can’t open UEFN session in 41.20” (2026-07-16), same UEFN-side timeout.  
Attached logs (the hung client itself writes no log)

EAC logs for 3 hung launches and 1 good launch  
Epic launcher log for the same period  
UEFN editor log showing the session timeout  
The last good FortniteGame.log, for comparison  
README.txt mapping each file to its launch

---

<div class="post-metadata">

**Author:** ![Bug-Reporter](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/bug-reporter/32/1223650_2.png) [@Bug-Reporter](https://forums.unrealengine.com/u/Bug-Reporter)\
**Post date:** [November 17, 2026, 2:39pm UTC](https://forums.unrealengine.com/t/fortnite-client-process-starts-but-never-opens-a-window-intermittent-50-of-launches/2857137/2 "2026-11-17T14:39:44Z")

</div>

FORT-1197637 has been created and its status is ‘Unconfirmed’. This is now in a queue to be reproduced and confirmed.

---

<div class="post-metadata">

**Author:** ![Jimbohalo10](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/jimbohalo10/32/961440_2.png) [@Jimbohalo10](https://forums.unrealengine.com/u/Jimbohalo10)\
**Post date:** [November 18, 2026, 2:30am UTC](https://forums.unrealengine.com/t/fortnite-client-process-starts-but-never-opens-a-window-intermittent-50-of-launches/2857137/3 "2026-11-18T02:30:40Z")

</div>

Same again then

### Nov 14, 2026

[EOS Easy Anti-Cheat Issue](https://status.epicgames.com/incidents/yflbq40410k3)

**Resolved** - We encountered and fixed an issue where Easy Anti-Cheat service was degraded for a small window of time. Service has returned to normal.
