Satisfactory Multiplayer Stuck on Loading Screen

Confirm the kind of session

These checks apply to Windows PC players on Steam or Epic joining a friend who hosts from the normal game client. They are not dedicated-server setup instructions. If Server Manager, Authenticate or a Server API error is involved, use the dedicated-server checks instead; changing which friend hosts does not test that deployment. We checked the support and patch sources on 14 September 2026 and the cited loading report on 16 September; we have not reproduced this fault in a running session.

The 11 August v1.2.4.0 notes describe improved loading when joining another player’s hosted game. Both players should finish available updates and compare their displayed version and main/Experimental branch before interpreting an older report. An announced improvement is not proof that every loading failure is fixed.

First distinguish a stalled join from a host crash

Ask the host whether they can still move and interact. If their game has closed, preserve its error and follow the PC crash checks. Repeated client reconnects cannot establish the cause of a host crash.

If the host remains active, record what each player sees: loading image, error text, elapsed time, world sounds, and whether the host sees the joining character. A player report describes audible world sounds behind a persistent loading screen. That observation is useful evidence, not proof that the connection has fully succeeded.

There is no verified universal waiting time in the sources reviewed. Record your wait duration. If the screen never progresses, leave normally if possible and coordinate a fresh attempt with the host instead of reconnecting continuously.

Back up before the comparison

The host should close the game and copy %LOCALAPPDATA%\FactoryGame\Saved\SaveGames to a separate dated location. Check the copy exists and leave the main factory untouched. Use distinct temporary session names for every new test factory.

If verification has not been done, complete it on the affected installation: Steam Properties → Installed Files → Verify integrity of game files, or Epic three-dot menu → Manage → Verify. Wait for completion. If both players already verified and reinstalled without improvement, record that and continue below.

Compare saves and hosts one step at a time

This is our suggested comparison sequence, informed by official PC troubleshooting. It narrows the next investigation without proving a root cause.

Keep the same participants and join method while comparing saves. Change the host only in the next comparison. You do not need to transfer your main factory for this initial check.

Record mod lists and versions on both PCs. Use the installed manager’s documented controls to run the temporary sessions without mods. Official support warns that uninstalling mods can leave effects in an existing save. Do not overwrite a modded factory after disabling its dependencies.

Check the join route without resetting everything

For Steam–Epic PC play, the official FAQ supports session IDs or linked Epic friends. Ask the host for the current session ID privately and compare it with your usual friends-list route. Never post an active ID or account token in a public bug report.

Record any exact account error. The official account-relinking advice addresses Multiplayer incompatible account; a loading screen alone is not that diagnosis. Console FAQ account requirements should not be copied into this PC workflow.

Check that the installed game is allowed by the existing firewall rules on the network profile you actually use. Keep security software enabled. If you use an optional VPN or proxy, record one comparison with it disconnected when appropriate for your network, then restore it. Avoid router resets, copied port ranges or hosts-file overrides without current, specific support guidance.

When to stop and report

Stop repeating reinstallations once the same failure remains after verification and the fresh-session comparisons. Search the official Q&A site for the exact symptom and PC version. Report both players’ launcher, build, branch, mod history, host direction, same-network/different-network situation, error, time zone and comparison results. Include the host’s crash text if applicable, with private details removed.

We have not verified a live service outage or the current status of Q&A issues linked by community replies. Preserve the original save and restore optional changes that made no difference.

Related questions

Is randomly disconnecting the same problem? No. If you enter and play before a timeout, record time until disconnection and whether everyone drops. Host and fresh-save comparisons may help, but a persistent loading screen does not establish the same cause.

Can these steps connect a console player to PC? No. The current official console FAQ describes separate PC and console ecosystems. This article covers PC Steam–Epic sessions only.

What if I finally enter, but my inventory is empty? Stop treating it as the same loading failure. Keep the save backed up and use the player-identity and inventory checks; an intact factory with a different character can have a separate account-identity cause.