Since this update I have noticed Fortnite is not closing correctly after launching a session through UEFN. This causes the Epic Games Launcher to show Fortnite as running and you not being able to launch the game. You cannot even end the process manually in Task Manager
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Other
Steps to Reproduce
Launch a session in UEFN, and attempt to close both the editor and fortnite, potentially the editor first and then the client.
Expected Result
Fortnite client fully closes and is not remaining in background processes.
Observed Result
Fortnite client remains open in a background process, unable to be force ended.
Try closing âurcâ or âcrashhelperâ or something like that, some times they are left running as well. If you have vs code or any IDE open, you might have to close those.
Each major update from 36.00 has required the Epic Games Launcher to be manually updated.
This could be because the C:\Users\%USERNAME\AppData\Local\Epic Games files are old, but installing a new version of Epic Launcher has fixed this.
The status of UEFN and Fortnite is updated only; launch status updates no more frequently than every 30 seconds.
Fortnite cannot be stopped by Task Manager, as the Fortnite images have a protected image status to stop malicious attempts to attack Fortnite.
The way to force closure is to right-click the Fortnite icon on the taskbar and select âClose Windowâ.
Since 37.00, the Red X in the top right has worked, and a message asking if you want to close Fortnite.
Phones and Switch 1 Fortnite do not close, just continue when the UEFN session is closed, and now Windows Fortnite possibly works that way.
The consoles can fall back to the lobby or carry on without the editor, or let the island run like a published island, but you cannot have others join, just a debug local version
Same issue. Iâve gone as far as finding all the active processes and making sure I have full permissions, but I still get âaccess deniedâ error when attempting to end task for fortniteclient-win64-shipping.exe (after giving all users full control).
If you close everything else related to the game, then go to:
Wherever the game is stored \Fortnite\FortniteGame\Binaries\Win64 and then open FortniteClient-Win64-Shipping_EAC_EOS, Fortnite should be able to be closed using the task-manager. Then it can be relaunched using the Epic Games Launcher.
Fortnite runs as a Protected Process Light (PPL) in Windows.
This prevents malicious programs or cheats from injecting code or forceâterminating the game.
Because of this, even tools like taskkill or Process Explorer cannot end the process.
Correct Ways to Close Fortnite
Use the inâgame interface
Click the Red X in the topâright corner (available since version 37.00).
Confirm the prompt asking if you want to close Fortnite.
Use the taskbar icon
Rightâclick the Fortnite icon on the Windows taskbar.
Select Close window.
End the UEFN session
If you are running Fortnite through UEFN (Unreal Editor for Fortnite), closing the editor session will eventually shut down the Fortnite client.
Note: this may take up to 30 seconds due to delayed status updates.
Restart Windows
If Fortnite becomes unresponsive and wonât close through the above methods, a system restart is the only guaranteed way to terminate the process.
Important Notes
Do not attempt to bypass PPL protection using thirdâparty tools or drivers.
This can corrupt Fortnite files.
It may trigger antiâcheat detection and lead to account suspension.
The new closing behavior is intentional: Epic is aligning PC with console/mobile, where the game continues running in the background after UEFN sessions.
Same here, and it does not happen once, not twice, not three times. But this is the seventh time⌠in just 3 days. I am ANNOYED and FRUSTRATED. They dont fix it. I have to restart my pc AGAIN. I might as well delete this game.
@Flak Is there an update on this bug?
Itâs still not fixed and itâs getting frustrating. I closed out the game properly and it still says that it is running.
Iâve been getting this constantly since 39.11. Even bumping into the PPL issue a few times needing a full reboot, that that is after figuring out it used to happen more with Alt-F4. Now it happens every time the app closes, even using the legitimate method.