Cannot connect to UEFN session since 36.10 update.

[hoskijdev]

Summary

Cannot connect to UEFN session since 36.10 update.
Connection fails 90% of the time. I got in once over the past few days.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Matchmaking

Steps to Reproduce

1. Launch fortnite
2. Launch UEFN and open project
3. Launch UEFN session
4. Fortine gets stuck on loading screen for 10 minutes (600 seconds), before crashing.

Expected Result

1. Launch fortnite
2. Launch UEFN and open project
3. Launch UEFN session
4. Load into uefn project in fortnite

Observed Result

After launching UEFN session, Fortine gets stuck on a loading screen for 10 minutes (600 seconds), before crashing.

Platform(s)

PC

Upload an image

Additional Notes

I’ve already tried:

• verifying game and uefn files
• adding ports to firewall exceptions
• disabling firewall
• resetting router
• updating windows
• updating graphics drivers
• re-installing UEFN
• opening fortnite first, then uefn, then launching session
• opening UEFN, then launching fortnite from “launch session”
• deleting my gamesettings
• testing with a clean boot
• launching epic games launcher as admin
• testing on a new windows user

[hoskijdev]

FortniteGame-backup-2025.06.23-07.18.38.log (2.7 MB)
The fortgame log (attached)

[hoskijdev]

Session not starting

Summary Since v36.10, it has become impossible to start a UEFN session. We hope that you will be able to start a session and return to the usual UEFN. Please select what you are reporting on: Unreal Editor for Fortnite What Type of Bug are you experiencing? Matchmaking Steps to Reproduce I try to open uefn and start a session, but it does not start. Expected Result Could the v36.10 update be preventing sessions from starting? Observed Result Session does not start in UEFN Platform(s) UEFN

[hoskijdev]

Bug Report: UEFN Stuck on "Connecting..." – Cannot Launch Any Session

Summary UEFN is completely unable to launch a session. On any project — including brand new, empty projects — clicking Launch Session causes the editor to hang indefinitely on “Connecting…”. This occurs on a fresh install with no Verse scripts, plugins, or modifications. Please select what you are reporting on: Unreal Editor for Fortnite What Type of Bug are you experiencing? Assets Steps to Reproduce Fresh install of UEFN via Epic Games Launcher Launch UEFN Create a new blank project Clic…

[LargeRedApe]

This fixed it for me:

1. Logged into a different Epic account in UEFN.,

2. Logged back into my main account.,

3. Went to Epic Account Settings → Password & Security → clicked “Sign Out Everywhere.”,

Sessions now launch normally.

[hoskijdev]

(post deleted by author)

[hoskijdev]

In addition to troubleshooting steps metioned previously:

• At the time, reinstalling the Epic Games Launcher didn’t work

I was half way through trying a clean install on a different drive (the integrity of my drives were fine btw, sfc /scannow returned nothing) when the tuesday update happened.

Mine works 100% of the time now (I’m in OCE servers).

I suspect it had something to do with the FortniteStatus twitter account investigation, or the update.

[hoskijdev]

Now that my issue is solved, for future reference attached is a screenshot of my support ticket conversation.

Here are the links they sent in that screenshot in order:

• https://www.epicgames.com/help/en-US/c-Category_EpicGamesStore/c-EpicGamesStore_LauncherSupport/how-do-i-disable-background-applications-a000084766
• https://www.epicgames.com/help/en-US/c-Category_Fortnite/c-Fortnite_TechnicalSupport/how-do-i-update-graphics-card-drivers-a000085408
• https://www.epicgames.com/help/en-US/c-Category_EpicGamesStore/c-EpicGamesStore_LauncherSupport/how-do-i-reinstall-the-epic-games-launcher-a000085741
• https://www.epicgames.com/help/en-US/c-Category_Fortnite/c-Fortnite_TechnicalSupport/why-isn-t-reinstalling-fortnite-fixing-the-corrupted-data-has-been-discovered-in-the-game-files-error-a000094268

[Bug-Reporter]

FORT-928794 is ‘Closed’ as ‘Fixed’. The issue will be addressed in 36.10.