Thanks for the response and the helpful link!
Following the suggestion, I used Task Manager on my Windows 11 (UEFN development environment) to kill the Fortnite task, then restarted Fortnite manually.
As a result, launching Fortnite first allowed the session to connect properly. However, starting a session from UEFN didn’t automatically launch Fortnite.
Since I haven’t installed any other game launchers on this machine, I was curious about why this happens — but it doesn’t seem to affect the integration with UEFN, so it’s only a minor issue.
With the settings shown in the attachment, selecting “Platform: This PC” successfully launched the main Fortnite client.
It seems that when it wasn’t launching before, I had selected “Connect to Platform” instead.
Thanks again for your help!
hi @mtaro02050305 ,
The reason for this is that the Fortnite sets up the Windows 11 firewall every time that Fortnite starts. UEFN cannot setup the firewall because of protection issues. Maybe this would work if you ran as administrator for EPGL and therefore UEFN. Fortnite works by using a special certificate to allow access to the Windows 11 Firewall.
Launch will NOT run if Fortnite has NOT been run after a reboot/restart, EPGL will correct/reet firewall settings.