# Fortnite disconnected ~35 seconds after joining **URL:** \ **Category:** Issues and Bug Reporting\ **Tags:** Reso-Invalid, unreal-engine, Status-Closed, bug-report, question, fortnite\ **Created:** [October 19, 2026, 6:17pm UTC](https://forums.unrealengine.com/t/fortnite-disconnected-35-seconds-after-joining/2842592 "2026-10-19T18:17:35Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![LunaV2](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@LunaV2](https://forums.unrealengine.com/u/LunaV2)\ **Post date:** [October 19, 2026, 6:17pm UTC](https://forums.unrealengine.com/t/fortnite-disconnected-35-seconds-after-joining/2842592/1 "2026-10-19T18:17:36Z")
### Summary Since 16 October 2026 this PC is disconnected from every match shortly after joining. Timing: Most sessions: 35–39 seconds Longer sessions: 53s, 63s, 64s, 73s, 106s The kick message is the standard one: “You were removed from the match due to internet lag, your IP or machine, VPN usage, or for cheating.” Error code shown: errors.com.epicgames.common.processing 17 sessions captured across 17 different server IPs. Every single one was disconnected. Why I don’t think this is a client-side fault In all 17 sessions, the client log shows the same sequence: LogEOSAntiCheat: [AntiCheatClient] [BeginSession-003] Mode: 1 ← opens normally LogEOSAntiCheat: [AntiCheatClient] AddNotifyClientIntegrityViolated ← listener bound LogNet: NMT\_CloseReason: (Server Disconnect Reasons) ← SERVER closes it LogEOSAntiCheat: [AntiCheatClient] [EndSession-001] ← ends AFTER the disconnect LogOnlineGame: Warning: ClientWasKicked … ClientIntegrityViolated never fires — not once in 17 sessions. The anti-cheat session starts normally every time and is torn down by the server’s disconnect, not by a detection. Session table Session start Server disconnect Interval Server IP 16 Oct 06:38:19 06:39:22 63s 18.168.69.188:9040 16 Oct 07:21:24 07:22:28 64s 18.168.53.87:9048 16 Oct 07:46:11 07:46:50 39s 18.133.164.113:9049 16 Oct 08:39:47 08:41:33 106s 18.133.165.186:9029 16 Oct 08:57:52 08:58:28 36s 18.168.43.43:9066 16 Oct 09:01:33 09:02:12 39s 18.168.69.73:9043 16 Oct 23:16:12 23:16:47 35s 13.41.11.23:9011 16 Oct 23:27:23 23:28:36 73s 18.133.165.115:9042 17 Oct 00:22:32 00:23:07 35s 18.168.147.158:9034 17 Oct 00:36:02 00:36:39 37s 18.168.147.158:9051 17 Oct 00:41:15 00:41:54 39s 18.170.210.49:9056 17 Oct 05:21:22 05:22:15 53s 18.170.210.49:9052 17 Oct 06:04:30 06:05:05 35s 34.39.117.41:9084 17 Oct 11:58:27 11:59:02 35s 18.157.20.202:9004 19 Oct 07:02:47 07:03:51 64s 51.44.172.149:9042 19 Oct 10:38:29 10:39:00 31s 18.156.219.60:9056 19 Oct 11:29:31 11:30:06 35s 15.188.77.176:9041 Control tests — this is the key part Test Result This PC Disconnected in all 17 sessions Same account on console Plays normally, no disconnect Same account on GeForce Now Plays normally, no disconnect Second account on this PC Also disconnected Second account on GeForce Now Plays normally Mobile hotspot instead of home broadband No change The Texas Chain Saw Massacre (also Easy Anti-Cheat) on this PC Installs, launches, plays normally So: the account is fine, the network is fine, the machine can run Easy Anti-Cheat — but every Fortnite session on this PC ends in a server-issued disconnect. Everything I’ve already tried (none of it changed anything) Clean reinstall of Fortnite and Easy Anti-Cheat, leftover folders deleted, reboots between stages Full uninstall and reinstall of the Epic Games Launcher (including ProgramData\Epic and local appdata) Complete fresh Windows installation with a new user profile Fresh Windows user profile with a fresh game install Clean boot with all third-party services and startup items disabled MSI Afterburner + RivaTuner Statistics Server fully removed, including the RTCore64 kernel driver (verified absent) sfc /scannow → “Windows Resource Protection did not find any integrity violations” DISM /Online /Cleanup-Image /RestoreHealth → completed Microsoft Visual C++ 2010, 2012 and v14 redistributables, x64 and x86, all current Windows Defender is the only security software; Protection history clean; EAC folder excluded Registry writes to HKLM\SOFTWARE verified working from an elevated prompt No VPN, no proxy; public IP confirmed as a normal residential address System Restore: no restore points available Registry findings After the fresh Windows install, the Easy Anti-Cheat EOS registration is present and working: HKLM\SOFTWARE\WOW6432Node\EasyAntiCheat\_EOS ProductsInstalled REG\_SZ prod-fn; ErrRpt\_LastInitProductId REG\_SZ prod-fn ErrRpt\_LastInitSandboxId REG\_SZ fn ErrRpt\_LastInitDeploymentId REG\_SZ 62a9473a2dca46b29ccf17577fcf42d7 ErrRpt\_LastInitBuildId REG\_DWORD 0x35fc ErrRpt\_LastInitInfo1 REG\_QWORD 0xfffff80446c10000 ErrRpt\_LastUnloadDuration REG\_DWORD 0x470 On the first launch the launcher logged WARN msg=“could not open eac eos registry path” — that warning is gone on subsequent launches, and the launcher now loads Settings.json directly instead of falling back to DefaultSettings.json. So the registration issue is resolved, and the disconnect is unaffected. Also relevant: EasyAntiCheat\_EOS service reports START\_PENDING with NOT\_STOPPABLE, NOT\_PAUSABLE, IGNORES\_SHUTDOWN EasyAntiCheat\_EOS\_Setup.exe will not launch in any form — double-click, Run as administrator, elevated Command Prompt, or via a shortcut with install prod-fn in the Target field. No window, no error, no Event Viewer entry Machine ID changed from 27c9a66af8f04e6c9b906b8c23143105 to f39557f158964a5cb5449ef55c27f30f after the fresh install, and the disconnect is unchanged Account history (relevant to the timeline) Sanctioned on 16 October, after the disconnects had already begun at 06:38 that morning Appeal granted — appeal ID 02b2a2d7-6421-466e-81db-85f6ebf66741: “determined that it was applied incorrectly… removed the sanction and cleared it from your account’s sanction history” Ban removed — ban removal ID 66fcb0a5-1c26-4f2b-842e-579a47bec4f1: “has been unbanned from Fortnite and you can now log in and matchmake again” Despite both, the disconnects continue unchanged What I’m actually asking Has anyone seen this pattern — server-issued disconnects on one specific PC, across many different servers, with no client-side anti-cheat violation ever logged? Is there any known issue with the Easy Anti-Cheat EOS registration not initialising, and does ErrRpt\_LastInitInfo1 = 0xfffff80446c10000 mean anything to anyone here? The 0xfffff804… prefix looks like a kernel-mode failure address. Does a machine-level restriction behave like this? If anyone has dealt with one: does it present as server-issued kicks rather than a launch error, and does it survive a Windows reinstall? Is there a channel that actually reaches a technical team, rather than the first-line support chat? Happy to provide full session logs for any of the sessions above. Thanks in advance. ### Please select what you are reporting on: Creative ### What Type of Bug are you experiencing? Matchmaking ### Steps to Reproduce N/A ### Expected Result N/A ### Observed Result N/A ### Platform(s) PC ---
**Author:** ![Dr3kzo](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Dr3kzo](https://forums.unrealengine.com/u/Dr3kzo)\ **Post date:** [October 25, 2026, 1:50pm UTC](https://forums.unrealengine.com/t/fortnite-disconnected-35-seconds-after-joining/2842592/2 "2026-10-25T13:50:47Z")
```auto I have exactly the same problem as you, though for me it started at the beginning of the month. Have you found a solution? ``` ```auto ``` ---
**Author:** ![BackToLife212](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@BackToLife212](https://forums.unrealengine.com/u/BackToLife212)\ **Post date:** [October 27, 2026, 5:32pm UTC](https://forums.unrealengine.com/t/fortnite-disconnected-35-seconds-after-joining/2842592/3 "2026-10-27T17:32:05Z")
happening to me too like nothings even on my pc like i resetted my pc too and still get the error i tried EVERYTHING cus also the account im on i also tested it on another pc it works there. I NEVER downloaded a vpn or cheats im also using ethernet with good speed ---
**Author:** ![LunaV2](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@LunaV2](https://forums.unrealengine.com/u/LunaV2)\ **Post date:** [October 27, 2026, 8:23pm UTC](https://forums.unrealengine.com/t/fortnite-disconnected-35-seconds-after-joining/2842592/4 "2026-10-27T20:23:08Z")
no but u can play fortnite through GeForce Now App ---
**Author:** ![LunaV2](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@LunaV2](https://forums.unrealengine.com/u/LunaV2)\ **Post date:** [October 27, 2026, 8:23pm UTC](https://forums.unrealengine.com/t/fortnite-disconnected-35-seconds-after-joining/2842592/5 "2026-10-27T20:23:49Z")
its a false positive ban epic can resolve it but choose not to ---
**Author:** ![Flak](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/flak/32/769441_2.png) [@Flak](https://forums.unrealengine.com/u/Flak)\ **Post date:** [November 3, 2026, 11:10am UTC](https://forums.unrealengine.com/t/fortnite-disconnected-35-seconds-after-joining/2842592/7 "2026-11-03T11:10:54Z")
Closing, as we are unable to evaluate individual moderation issues. Please check [this](https://safety.epicgames.com/en-US/sanctions-and-appeals) page for information on sanctions and appeals. ---
**Author:** ![Flak](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/flak/32/769441_2.png) [@Flak](https://forums.unrealengine.com/u/Flak)\ **Post date:** [November 3, 2026, 11:11am UTC](https://forums.unrealengine.com/t/fortnite-disconnected-35-seconds-after-joining/2842592/8 "2026-11-03T11:11:22Z")
---
**Author:** ![Bug-Reporter](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/bug-reporter/32/997076_2.png) [@Bug-Reporter](https://forums.unrealengine.com/u/Bug-Reporter)\ **Post date:** [November 3, 2026, 12:00pm UTC](https://forums.unrealengine.com/t/fortnite-disconnected-35-seconds-after-joining/2842592/9 "2026-11-03T12:00:27Z")
FORT-1186378 has been ‘Closed’. The issue reported is not caused by a bug in the tool.