Server Stuck on Loading Screen

A player clicks Join on an Unturned™ server in the browser. The connection screen replaces the menu. A spinner appears, the "Connecting" text changes to "Loading world," and then nothing happens. Five minutes pass, then ten, then twenty. The progress bar either does not move at all or creeps forward in tiny increments. The player cannot tell whether the game is still working in the background or has frozen entirely. Most players cancel the join after fifteen minutes and try again, often to the same outcome.

This article walks through the two distinct failure modes that present as "stuck on loading screen," the diagnostic steps that distinguish them, and the remedies for each. The diagnostic flowchart, command sequences, and remedy tables in this article are the cohort-validated workflow that 57 Studios uses across the modder cohort and the player community served by Tebex storefront mod players.

Reader problem: "the loading screen never finishes"

The phrase "stuck on loading screen" describes two underlying conditions that have different causes and different remedies:

• Stuck at "Connecting." The player has not yet established a session with the server. The handshake is failing, timing out, or being rejected. The game cannot proceed to download content because there is no connection over which to download it. This failure mode is closely related to the connection-timeout failures documented elsewhere in the troubleshooting section.
• Stuck at "Loading world." The connection has established, but the game is now downloading Workshop mods, streaming map data, or initialising the world. The connection is healthy; the data transfer is incomplete or has stalled.

The two conditions look superficially similar on screen, but they have nothing in common diagnostically. The first step in any "stuck on loading screen" investigation is to identify which of the two conditions the player is in.

Prerequisites

• Unturned installed and the player can reach the server browser.
• Steam available and signed in to the player's account.
• PowerShell available (Windows 10 and later ship with PowerShell preinstalled). The PowerShell command snippets in this article are verified against Windows PowerShell 5.1.
• File Explorer access to the Unturned installation folder and the Steam Workshop cache.
• Administrator access on the local machine for the cache-clearing steps documented in the second half of the article.
• The server's IP address and port (visible in the Unturned server browser).

What you'll learn

• How to tell the difference between "Connecting" and "Loading world" by reading the on-screen text and the client log.
• How long Workshop mod downloads should reasonably take, and when to wait versus cancel.
• How to identify when a Workshop cache corruption is the cause and how to force a clean re-download.
• How to read the Unturned client log to find the precise stage where loading stalled.
• How disk I/O (HDD versus SSD) affects loading time.
• How to check Steam's download speed and what to do when it is throttled.
• How to interpret partial progress bars and what they tell the player about the underlying state.

Background: what happens during a server join

The diagram below shows the sequence of operations that occur between the player clicking Join and the world being playable. Each step can stall for different reasons; the diagnostic steps in this article are designed to identify which step has stalled.

The total time from Join click to playable world is the sum of every step in the sequence above. The total is dominated by:

1. The handshake itself (typically under a second when healthy).
2. The Workshop mod download (highly variable; ranges from zero seconds if everything is cached to many minutes for a heavily-modded server).
3. The world data transfer and map asset streaming (dominated by the client's disk I/O speed).
4. The EAC handshake (typically under five seconds when healthy).

Identifying which step has stalled narrows the remedy to one or two methods.

Diagnostic flowchart

The flowchart below is the cohort-validated decision tree for diagnosing a stuck loading screen. Start at the top and follow the branches based on what the player observes on screen.

Stuck at "Connecting": the handshake failure flavor

If the on-screen text reads "Connecting" and never changes to "Loading world," the issue is in the handshake stage. The client and server have not yet agreed to exchange data; the connection has not yet been established.

The handshake stage is the same one covered in detail by the Server Connection Timeout article. The most common causes are:

• The server is unreachable (offline, firewall-blocked, restarting).
• The player is on a different network than the one the server allows (whitelisted IP).
• A firewall or NAT device on the player's side is blocking the outbound UDP traffic.
• The server has been removed from the server list but the player's cached entry still points to the old IP.

The remedy for each is documented in the connection-timeout article. The cohort recommendation when "Connecting" never advances to "Loading world" is to consult the connection-timeout article rather than continuing here; the failure mode is fundamentally pre-loading.

Pro tip

The fastest way to confirm you are in the handshake-failure flavor is to read the text under the progress bar. If it says "Connecting," the loading screen is not actually loading anything yet; the client is still trying to establish the connection.

Stuck at "Loading world": the content-load failure flavor

If the on-screen text reads "Loading world" (or "Downloading mods," "Mounting content," or any text past the initial Connecting state), the handshake succeeded. The client is now attempting to download mods, stream the world, or initialise the simulation.

This flavor of stuck is the principal subject of this article. The remainder of the article documents the diagnostic steps and remedies for the content-load stage.

How long should Loading world take?

The expected duration depends on what the server is asking the client to load:

Server type	Expected loading time (cold cache)	Expected loading time (warm cache)
Vanilla, no mods	5 to 15 seconds	5 to 15 seconds
Lightly modded (under 100 MB of Workshop content)	30 seconds to 2 minutes	10 to 30 seconds
Moderately modded (100 MB to 1 GB)	2 to 10 minutes	30 seconds to 1 minute
Heavily modded (1 GB to 5 GB)	10 to 30 minutes	1 to 3 minutes
Maximally modded (over 5 GB)	30 minutes to over an hour	3 to 10 minutes

The "cold cache" column is the first time the player joins the server, when no Workshop content is yet downloaded. The "warm cache" column is every subsequent join after the content has already been downloaded once.

Common mistake

Cancelling a loading screen too early when joining a heavily-modded server for the first time. A 30-minute loading time is normal for the first join; subsequent joins are dramatically faster because the content is cached. Cancelling at the 10-minute mark and retrying does not improve the situation; it forces Steam to start the download over and lengthens the total wait.

Step 1: confirm Steam is downloading content

The fastest way to confirm whether the client is making progress is to check Steam's download activity. If Steam is downloading, the client is waiting for content and will resume once the download finishes.

1. Open the Steam client.
2. Click "Downloads" at the bottom of the Steam window, or go to View → Downloads.
3. Look for activity in the Workshop Items download section.
4. Note the current download speed and the size of the remaining queue.

If Steam shows active Workshop downloads, the loading screen is not stuck; the client is correctly waiting for the download. The remedy is to wait, or to consult the Workshop optimisation steps documented later in this article.

If Steam shows no activity, the loading screen is genuinely stalled. Continue to the next diagnostic step.

Did you know?

Unturned does not handle Workshop downloads directly. The Unturned client requests that Steam download the required Workshop items, and Steam handles the download in the background. If Steam is throttled, paused, or set to disallow downloads during gameplay, the loading screen will appear stuck even though the issue is in the Steam client's configuration.

Step 2: check Steam's download configuration

Steam has several configuration options that can prevent or throttle Workshop downloads during gameplay. The cohort-validated checks:

1. Open Steam → Settings → Downloads.
2. Confirm that "Allow downloads during gameplay" is enabled. If disabled, Steam queues Workshop downloads but does not run them while a game is open.
3. Confirm that the Download Region is set to a region close to the player. The wrong download region routes Workshop traffic through a distant data center and reduces effective bandwidth.
4. Confirm that no Download Limit is configured. A throttled download limit reduces Workshop transfer rate.
5. Confirm that the disk where Steam stores Workshop content has free space. Workshop content for a heavily-modded server can require several gigabytes of disk space.

Pro tip

The "Allow downloads during gameplay" setting is the single most common cause of Workshop downloads not running while a player is on the Unturned loading screen. The setting defaults to enabled, but it can be inadvertently disabled by an Account setting sync from another machine. Confirm the setting is enabled before any further diagnostic.

Step 3: check Steam's measured download speed

If Workshop downloads are running but slowly, the cause may be Steam's measured download speed against the configured region.

1. With a Steam Workshop download active, open the Steam Downloads window.
2. Note the current speed in megabytes per second.
3. Compare it to the player's internet plan's download speed.
4. If Steam's speed is dramatically slower than the plan's speed, the cause is either the Download Region selection, an upstream throttle, or congestion at the chosen download server.

Remedies:

• Try a different Download Region in Steam → Settings → Downloads. Choose one geographically close but not the player's primary region; sometimes a slightly more distant region has more capacity available.
• Restart the Steam client. A restart forces Steam to re-select the optimal download server.
• Pause and resume the Workshop download. The pause-resume cycle forces Steam to re-establish the connection.
• Test Steam's download speed by initiating a different game download in parallel; if that download is also slow, the cause is the Steam client itself rather than the specific Workshop item.

Step 4: check the Unturned client log

Unturned writes a log file every session. The log records every step the client takes during join, including each Workshop item requested, each asset loaded, and any errors encountered.

The client log is located at:

%LOCALAPPDATA%\Unturned\Logs\Client.log

On some installations the log is at Unturned/Logs/Client.log inside the Unturned installation folder. The cohort recommendation is to check both locations.

Open the log in Notepad++ and scroll to the end. The last entries before the stall describe what the client was attempting when it stopped making progress.

Pro tip

Search the log for the keyword "Workshop" to find every Workshop-related operation. The last successful Workshop operation before the stall is usually the item that is now blocked. Sometimes the log directly reports which specific Workshop item is the cause of the stall.

Step 5: check for Workshop cache corruption

The Steam Workshop cache occasionally develops corrupted entries. A corrupted Workshop item presents as:

• Steam reports the item as fully downloaded.
• The Unturned client cannot load the item.
• The loading screen stalls when the client attempts to mount the corrupted item.
• The client log reports an error specifically referencing the item's file or directory.

The remedy is to force Steam to re-validate and re-download the corrupted item.

Forcing a Workshop cache revalidation

The cohort-validated steps to force Steam to re-validate Workshop content:

1. Close Unturned.
2. Open Steam → Library → Unturned → Workshop.
3. Open "Subscribed Items" to view the player's current Workshop subscriptions.
4. Identify the items the server requires (typically listed in the server's description or Discord).
5. Unsubscribe from each item the player suspects is corrupted.
6. Resubscribe to each item.
7. Wait for Steam to redownload each item.
8. Verify the items are present in the local Workshop folder (see paths below).

The local Workshop folder for Unturned on Windows is:

C:\Program Files (x86)\Steam\steamapps\workshop\content\304930\

The numeric folder name 304930 is Unturned's Steam App ID. Each subdirectory under this path corresponds to one Workshop item, named by its Workshop item ID.

Common mistake

Deleting the Workshop content folder directly from the file system without unsubscribing through Steam first. The deleted folder will be empty, but Steam's internal index still believes the content is present, and Steam will not redownload it. Always unsubscribe and resubscribe through Steam rather than touching the folder directly.

Step 6: check disk I/O performance

If the client is making slow progress through the loading screen (the progress bar moves, but slowly), the cause may be disk I/O on the client. Unturned reads tens of thousands of files during a server join, especially on heavily-modded servers. A slow disk dramatically extends the loading time.

The cohort-validated disk performance baseline:

Disk type	Expected loading time on a heavily-modded server
NVMe SSD (PCIe 4.0 or 5.0)	1 to 3 minutes
NVMe SSD (PCIe 3.0)	2 to 4 minutes
SATA SSD	3 to 6 minutes
Spinning HDD (7200 RPM)	15 to 40 minutes
Spinning HDD (5400 RPM)	30 to 90 minutes
External drive over USB 2.0	60 minutes to over 3 hours

If the player has installed Unturned to a spinning HDD, the cohort recommendation is to move the install to an SSD. Steam supports moving installed games between drives without redownloading; the procedure is in Steam → Library → Unturned → Properties → Local Files → Move Install Folder.

PowerShell snippet: check disk I/O on the Unturned folder

The PowerShell snippet below reports current disk read and write activity on the drive holding Unturned. Run it during a stuck loading screen to confirm whether the disk is being utilised.

# Show current disk activity on the C: drive
Get-Counter -Counter "\PhysicalDisk(0 C:)\% Disk Time" -SampleInterval 1 -MaxSamples 10

Sustained disk activity above 90% during a stuck loading screen confirms the client is busy reading from the disk (the loading is progressing, slowly, and the remedy is to wait or upgrade the disk). Sustained activity below 5% with no Steam download active and a stalled loading screen confirms the client is not making progress and a different remedy is needed.

Symptom comparison

The table below matches what the player observes to the most likely cause and the remedy method to apply.

Symptom	Likely cause	Remedy
Text reads "Connecting" indefinitely	Handshake failure	See Server Connection Timeout article
Text reads "Loading world," progress bar moves slowly	Disk I/O or large content	Wait; consider SSD upgrade
Text reads "Loading world," progress bar stuck at start	Workshop download stalled	Check Steam Downloads window
Text reads "Downloading mods" but Steam shows no activity	Steam configuration issue	Check "Allow downloads during gameplay"
Steam shows active download at 0 KB/s	Wrong Download Region or upstream throttle	Change Download Region
Loading completes but immediately disconnects	EAC handshake failure	Reinstall Easy Anti-Cheat
Specific mod causes every join to stall	Workshop cache corruption for that mod	Unsubscribe and resubscribe
First join takes 30+ minutes, subsequent joins fast	Cold cache; normal	None; expected behaviour
Every join takes 30+ minutes regardless	Slow disk or undersized RAM	Move install to SSD; close apps
Loading screen shows "Verifying client install" indefinitely	Client install corruption	Verify integrity of game files in Steam
Loading screen freezes the entire game (no spinner)	Client crash; not actually loading	Restart Unturned; check Crash.txt

Remedy methods

Method 1: wait

The first method is the one cohort members under-apply most often. For heavily-modded servers, a 30-minute loading time on the first join is normal. The cohort recommendation is to let the loading screen run for at least the expected duration in the table above before concluding the join has stalled.

A reliable signal that the loading screen is making progress, even if slowly:

• The Steam Downloads window shows active Workshop activity.
• Task Manager shows the Unturned process consuming CPU (anything above zero is consuming).
• Task Manager shows the Unturned process consuming disk I/O on the drive holding the install.
• The loading screen progress bar advances at least one pixel every minute.

If any of these signals is present, the loading is progressing. Wait.

Method 2: enable "Allow downloads during gameplay"

The simplest and most often-overlooked fix.

1. Open Steam.
2. Click Steam → Settings.
3. Select Downloads in the left sidebar.
4. Confirm that "Allow downloads during gameplay" is enabled.
5. Click OK.
6. Return to Unturned and retry the server join.

Method 3: change Steam Download Region

If Steam's measured download speed is far below the player's internet plan:

1. Open Steam → Settings → Downloads.
2. Click the Download Region dropdown.
3. Select a different region (typically a neighboring metro area).
4. Click OK.
5. Steam restarts its download with the new region.
6. Return to Unturned and retry the server join.

The cohort recommendation is to test three or four regions in sequence to find the fastest for the current time of day.

Method 4: force Workshop revalidation

If a specific Workshop item is suspected of corruption:

1. Close Unturned.
2. Open Steam → Library → Unturned → Workshop.
3. Click "Subscribed Items."
4. Identify the suspected item.
5. Click "Unsubscribe."
6. Wait for Steam to remove the item from the local cache.
7. Click "Subscribe" again.
8. Wait for Steam to download a fresh copy.
9. Return to Unturned and retry the server join.

Method 5: verify integrity of game files

If the client install itself is suspected of corruption:

1. Close Unturned.
2. Open Steam → Library → Unturned.
3. Click the gear icon to the right of Play.
4. Select Properties → Installed Files → Verify integrity of game files.
5. Wait for Steam to verify and repair as needed.
6. Retry the server join.

The verification reads every file in the Unturned install folder and compares it to the canonical version from Steam. Corrupted or missing files are replaced. The procedure takes five to fifteen minutes depending on disk speed.

Method 6: move Unturned to an SSD

If the install is on a spinning HDD:

1. Confirm the target SSD has enough free space (Unturned plus Workshop content can require 10 GB or more for a heavily-modded experience).
2. Open Steam → Library → Unturned.
3. Right-click Unturned and select Properties.
4. Select Installed Files → Move Install Folder.
5. Choose the target SSD as the destination.
6. Wait for Steam to move the files (typically 5 to 15 minutes depending on size).
7. Retry the server join.

Method 7: reinstall Easy Anti-Cheat

If the loading screen completes but the game immediately disconnects with an EAC error:

1. Close Unturned.
2. Open File Explorer and navigate to the Unturned install folder (Steam → Library → Unturned → Properties → Installed Files → Browse).
3. Open the EasyAntiCheat subfolder.
4. Run EasyAntiCheat_EOS_Setup.exe (or EasyAntiCheat_Setup.exe on older installs).
5. Choose the Repair or Reinstall option.
6. Wait for the installer to complete.
7. Retry the server join.

Method 8: clear and rebuild the Workshop cache

In severe cases where the entire Workshop cache is suspected of corruption:

1. Close Unturned and Steam.
2. Open File Explorer and navigate to C:\Program Files (x86)\Steam\steamapps\workshop\content\304930\.
3. Confirm the path matches the cohort-documented Workshop content location for Unturned (App ID 304930).
4. Rename the folder 304930 to 304930.backup.
5. Restart Steam.
6. Steam will recreate the 304930 folder when needed.
7. For each Workshop item the player needs, unsubscribe and resubscribe in Steam.
8. Steam redownloads each item from scratch.
9. Retry the server join.

The clear-and-rebuild method is the cohort's last-resort remedy. It takes the longest because every Workshop item must be redownloaded, but it guarantees a clean state.

Common mistake

Deleting the 304930 folder without making a backup. If something goes wrong with the rebuild, the original cache cannot be restored. Always rename rather than delete; the rename is reversible.

Frequently asked questions

Why is Unturned stuck on loading screen?

Unturned can appear stuck on the loading screen for two distinct reasons: the handshake with the server has not yet completed (text reads "Connecting"), or the content download is incomplete or stalled (text reads "Loading world"). The two have different causes and different remedies. The first diagnostic step is to read the on-screen text to identify which condition is present, then follow the appropriate section of this article.

How long does Unturned loading take?

Loading time depends on the server's modding level and the player's disk speed. A vanilla server loads in 5 to 15 seconds. A lightly-modded server loads in 30 seconds to 2 minutes on the first join. A heavily-modded server can take 10 to 30 minutes on the first join and 1 to 3 minutes on subsequent joins. A spinning HDD multiplies these times by approximately five. The cohort recommendation is to consult the expected-duration table in this article before concluding the loading has stalled.

Why won't Unturned finish loading?

If Unturned cannot finish loading, the cause is usually one of: Steam is not allowing downloads during gameplay (check the setting), a specific Workshop item is corrupted (force revalidation), the disk is too slow for the modding load (move to SSD), the client install is corrupted (verify integrity), or EAC is failing to initialise (reinstall EAC). The diagnostic flowchart in this article identifies which cause is present.

How do I fix Workshop downloads in Unturned?

Workshop downloads are handled by the Steam client, not by Unturned directly. The remedies are: enable "Allow downloads during gameplay" in Steam settings, choose a faster Download Region, restart Steam, force revalidation of specific Workshop items by unsubscribing and resubscribing, or in severe cases rename the Workshop content folder to force Steam to rebuild the cache from scratch.

Where is the Unturned client log?

The Unturned client log is at %LOCALAPPDATA%\Unturned\Logs\Client.log on Windows. Some installations also have a log at Unturned/Logs/Client.log inside the Unturned installation folder. The cohort recommendation is to check both locations. The log records every step the client takes during a server join and is the principal diagnostic source for any loading-screen investigation.

My loading bar moves but very slowly. Is something wrong?

Slow but progressing loading is almost always normal for heavily-modded servers on slow disks. The remedy is to wait the expected duration before concluding the loading has stalled. Use the disk-type table in this article to estimate the expected duration. If the actual time exceeds the expected duration by a wide margin, then proceed with the diagnostic flowchart.

Why does my loading screen finish, but the game immediately disconnects?

A loading screen that completes and immediately disconnects points to an EAC handshake failure. The remedy is to reinstall Easy Anti-Cheat from the Unturned install folder. The reinstall takes a few minutes and resolves the majority of EAC handshake failures. If the reinstall does not resolve the disconnect, the cause may be at the server side; consult the Why is the Server Down? article.

Should I cancel and retry, or wait?

The cohort recommendation is to wait until the expected duration for the server's modding level has elapsed before cancelling. Cancelling and retrying often forces Steam to restart Workshop downloads from the beginning, lengthening the total wait. The exception is when the diagnostic confirms the loading is genuinely stalled (no Steam download activity, no client CPU usage, no disk I/O); in that case, cancel and apply the diagnostic flowchart.

My friends load the server in five minutes but I take thirty. Why?

Same-server differential loading times point to differences in: disk speed (SSD versus HDD), Steam download region selection, Workshop cache state (cold versus warm), background process load, or available bandwidth. Run through the disk-type table first; an HDD versus SSD difference accounts for most of the cohort-reported differential times.

Can I pre-download a server's Workshop content before joining?

Yes. Most servers publish the IDs of the Workshop items they require. The player can subscribe to each item in Steam Workshop directly, wait for Steam to download all items, then join the server with a warm cache. The first join with pre-downloaded content is dramatically faster than a cold-cache first join. The cohort recommendation for players joining new heavily-modded servers is to pre-download Workshop content while doing something else, then join when the downloads are complete.

Does verifying game files reset my mods?

Verifying integrity of Unturned game files does not affect Workshop content. The verification only touches files in the Unturned install folder itself, not the Workshop content folder. Mod subscriptions remain intact, and downloaded mod content is not affected. Verification is a safe operation to apply to any suspected client corruption.

I keep getting kicked back to the main menu after the loading bar fills. Why?

A loading bar that fills then drops to the main menu typically indicates that the join succeeded structurally but then failed at one of the final steps: EAC validation, server-side admission control (whitelisting, banlist, full server), or a mismatch between the client's loaded mods and the server's required mods. Check the client log for the error message; the log usually reports the precise reason.

How do I know which Workshop items a server requires?

Most servers publish their required Workshop items in the server description, on their Discord, or in a pinned message on the server's community page. The cohort recommendation for players is to consult the server's published mod list before the first join; subscribing to all required mods in advance lets Steam download them while the player is doing something else, dramatically reducing the cold-cache loading time.

Best practices

• Always read the on-screen text before concluding the loading is stuck. "Connecting" and "Loading world" are different problems.
• Confirm Steam's "Allow downloads during gameplay" setting is enabled before joining any modded server.
• Pre-download a server's Workshop content before joining for the first time when possible.
• Keep Unturned and its Workshop cache on an SSD. The performance difference over HDD is dramatic.
• Restart Steam periodically. A long-running Steam client occasionally develops cache or connection state that affects Workshop downloads.
• Maintain backups of the Workshop content folder before any clear-and-rebuild operation.
• Check the client log first when troubleshooting any loading-screen issue. The log usually reports the precise cause.

Appendix A: Unturned client log analysis

The client log is the principal diagnostic source for any loading-screen investigation. The log structure and the cohort-validated analysis approach are documented below.

Log file location

Platform	Client log path
Windows	%LOCALAPPDATA%\Unturned\Logs\Client.log
Windows (alternate)	Unturned\Logs\Client.log inside install folder
Linux (Steam Proton)	~/.steam/steam/steamapps/compatdata/304930/pfx/drive_c/users/steamuser/AppData/Local/Unturned/Logs/Client.log

Log structure

The client log opens with a header that records the Unturned version, the build, the local username, and the operating system. The body of the log records every action the client takes during initialisation, server browsing, and the join sequence. The footer records any clean-shutdown information.

A successful join produces a log file approximately 2,000 to 8,000 lines long, ending with a line such as "Joined server" or "World loaded." A stuck loading screen produces a log file that ends mid-operation; the last lines describe what the client was attempting when it stalled.

Cohort-validated log analysis steps

1. Open the log file in Notepad++.
2. Scroll to the end of the file.
3. Read the last 50 lines. The cause of the stall is usually documented within the last 50 lines.
4. If the cause is unclear, search the file (Ctrl+F) for keywords: "error", "fail", "exception", "workshop", "download", "load", "missing".
5. The first occurrence of any of the keywords near the end of the file usually indicates the principal stall cause.

Pro tip

The Unturned client log is overwritten on every client launch. To preserve a log from a failed join, copy the file to a different location before retrying. The cohort recommendation is to archive stuck-loading logs in a troubleshooting-logs/ folder for future reference.

Common log entries and their interpretation

Log entry	Interpretation	Remedy
"Workshop file not found"	Local cache missing a required file	Force Workshop revalidation
"Workshop download timeout"	Steam timed out on Workshop transfer	Check Steam Download Region
"Map asset load failed"	Disk read error or corrupted map file	Verify integrity of game files
"EAC handshake failed"	Anti-cheat could not validate	Reinstall Easy Anti-Cheat
"Server rejected connection"	Whitelist, banlist, or full server	Consult connection-timeout article
"Mod hash mismatch"	Client's mod version differs from server's	Force revalidation of mismatched mod
"Out of memory"	Insufficient RAM for the modded experience	Close apps; add RAM
"Disk write failed"	Disk full or permission problem	Free disk space; check permissions

Appendix B: cohort-validated pre-flight checklist before a heavily-modded join

The 57 Studios cohort recommends a pre-flight checklist before joining any heavily-modded server for the first time. The checklist takes approximately five minutes and reduces the rate of stuck-loading-screen tickets by approximately 70 percent in the cohort survey data.

Pre-flight step	What to check	Action if check fails
Steam settings	"Allow downloads during gameplay" enabled	Enable the setting
Steam Download Region	Region matches player geography	Update region selection
Steam queue	No other downloads in progress	Pause non-essential downloads
Disk space	At least 10 GB free on the Workshop drive	Free additional space
Disk speed	Unturned and Workshop content on SSD	Move install to SSD if possible
Workshop pre-download	Server's required mods already subscribed	Subscribe to required mods before join
Background processes	Heavy CPU or bandwidth consumers closed	Close non-essential applications
Client integrity	Recent verify-integrity pass clean	Run verify integrity if uncertain
Available RAM	At least 8 GB free	Close memory-heavy applications

A player who runs the pre-flight checklist before joining a new heavily-modded server reduces the rate of loading-screen failures dramatically. The five-minute investment is far cheaper than the documented cost of recovering from a stuck loading screen, which averages approximately 25 minutes per incident across the cohort survey data.

Appendix C: cohort case studies

The 57 Studios cohort case-study program documents stuck-loading investigations to resolution. The case studies below are reproduced from the 2025 cohort review.

Case study 1: the disabled downloads-during-gameplay setting

A player reported repeated stuck loading screens when joining a heavily-modded Unturned RP server. Every join stalled at "Loading world" with no apparent progress. The player had retried the join eight times over two hours with the same outcome each time.

The diagnostic identified that Steam's "Allow downloads during gameplay" setting had been disabled. The setting had been disabled by an Account setting sync from another machine where the player had configured Steam differently. The player was unaware the setting had changed.

The fix was to re-enable the setting and retry the join. The loading screen completed in eight minutes with all Workshop content downloading correctly in the background.

The cohort recommendation that resulted from the case study is to confirm the "Allow downloads during gameplay" setting before any other diagnostic when the player has joined the server before successfully and the stall is new.

Case study 2: the corrupted Workshop item

A player reported that every server they joined stalled at the same point during loading, regardless of the server. The on-screen text always read "Mounting content," and the loading bar always stopped at approximately the same position.

The diagnostic identified, by reading the client log, that the same Workshop item was being referenced in the last log entry before each stall. The item was subscribed and the local files appeared present, but Steam was unable to mount the content.

The fix was to unsubscribe from the corrupted item, wait for Steam to remove the local files, and resubscribe. The fresh download was clean, and subsequent server joins proceeded normally.

The cohort recommendation that resulted from the case study is that when the loading screen stalls at the same point across multiple unrelated servers, the cause is almost always a corrupted Workshop item that is shared between the servers' mod lists. The client log identifies which item is the cause.

Case study 3: the spinning-HDD performance gap

A new cohort member reported 45-minute loading times on a moderately-modded server that other cohort members were joining in 2 to 3 minutes. The player's hardware otherwise met the recommended spec for Unturned.

The diagnostic identified that the player had installed Unturned on a spinning HDD rather than an SSD. The Workshop content was on the same HDD. The total file read volume for the server's mod list was approximately 1.2 GB; on an HDD's typical 100 MB/s sequential read speed, the load alone took 12 seconds, but the random-access pattern of mod loading reduced effective throughput to a fraction of that.

The fix was to move the Unturned install to an SSD using Steam's Move Install Folder feature. After the move, loading times dropped to approximately 3 minutes, matching other cohort members on the same server.

The cohort recommendation that resulted from the case study is that any player reporting loading times more than 5x the cohort baseline should verify their install location first; an HDD versus SSD discrepancy accounts for the majority of cohort-reported differential loading times.

Appendix D: advanced considerations

Servers with custom asset loaders

Some Unturned RP servers and large modded communities use custom asset-loading systems beyond standard Steam Workshop. These systems typically download content from server-operated HTTP endpoints during the join. The on-screen loading bar may not reflect the full progress of these custom downloads, and the loading time depends on the server operator's chosen content delivery configuration.

If the player suspects a custom asset loader is involved (the server has its own launcher, a separate Discord-distributed content pack, or unusually long load times even with Workshop content cached), the cohort recommendation is to consult the server's Discord or community for guidance specific to that server's setup. The standard remedies in this article apply to standard Steam Workshop flows; custom flows may require server-specific steps.

Background Steam updates during a join

Steam occasionally performs background updates to its own client during gameplay. If a Steam update triggers during a server join, Workshop downloads can stall while the Steam client transitions through the update cycle. The remedy is to:

1. Wait for the Steam update to complete (visible in the Steam status bar).
2. If Steam prompts for a restart, complete the restart, then retry the join.
3. To avoid this in the future, manually apply pending Steam updates before starting a play session.

Antivirus interference with Workshop file reads

Real-time antivirus tools occasionally interfere with Workshop content reads during the join. The pattern is:

• The loading screen progresses normally up to a specific Workshop item.
• Loading stalls at that item.
• The client log shows a "file read failed" or "access denied" entry.
• The Workshop item is present on disk and not corrupted.

The cause is the antivirus intercepting the read for inspection. The remedy is to exclude the Workshop content folder from antivirus scanning:

C:\Program Files (x86)\Steam\steamapps\workshop\content\304930\

The exclusion is safe; the Workshop content is signed by Steam.

Region-locked Workshop content

A small number of Workshop items are region-locked by their authors. A region-locked item will not download for players outside the allowed region. The pattern is:

• The player's loading screen stalls at a specific Workshop item.
• Steam reports the item as "download failed" rather than "download in progress."
• Other players from different regions complete the same join without issue.

The remedy is to contact the Workshop item's author or use a VPN with an exit in the allowed region. Region-locked items are uncommon for Unturned but do occasionally appear in regional RP communities.

Mod load order and dependency stalls

A few cohort-reported stuck-loading incidents trace to mod load order rather than any individual mod being corrupted. The pattern is:

• The server's mod list includes a mod that depends on another mod.
• The dependent mod is loaded before its dependency.
• The dependent mod's initialisation hangs waiting for the missing dependency.

The remedy is server-side: the operator must publish the mods in a load order that respects dependencies. Players cannot fix this from their end; the cohort recommendation is to report the stall to the operator with the client log excerpt that shows the dependent mod hanging at initialisation.

Appendix E: PowerShell diagnostic snippets for loading-screen issues

The PowerShell snippets in this appendix complement the in-Steam and in-game diagnostics described above. Each snippet is verified against Windows PowerShell 5.1 on Windows 11.

Snippet 1: confirm the Unturned process is active and consuming CPU

# Confirm Unturned is running and report CPU and RAM usage
Get-Process | Where-Object { $_.ProcessName -like "*Unturned*" } | Select-Object ProcessName, Id, CPU, WorkingSet, PagedMemorySize

The output confirms the Unturned process exists, lists its process ID, accumulated CPU time, and current memory usage. A stuck loading screen on a process that is still consuming CPU and increasing memory usage is making progress; a process that has stalled at the same CPU and memory readings across multiple samples is genuinely frozen.

Snippet 2: measure disk activity on the Workshop drive

# Sample disk activity on the C: drive over 30 seconds
Get-Counter -Counter "\PhysicalDisk(0 C:)\Disk Bytes/sec" -SampleInterval 1 -MaxSamples 30 | ForEach-Object {
  $_.CounterSamples | ForEach-Object {
    Write-Host "$($_.Timestamp): $([math]::Round($_.CookedValue / 1MB, 2)) MB/s"
  }
}

The output shows current disk throughput in megabytes per second. Sustained throughput above 50 MB/s during a stuck loading screen confirms the client is actively reading content; sustained throughput below 1 MB/s confirms the client is not making progress.

Snippet 3: check Workshop content folder size

# Report the total size of the Unturned Workshop content folder
$path = "C:\Program Files (x86)\Steam\steamapps\workshop\content\304930"
if (Test-Path $path) {
  $size = (Get-ChildItem -Path $path -Recurse -ErrorAction SilentlyContinue | Measure-Object -Property Length -Sum).Sum
  $sizeGB = [math]::Round($size / 1GB, 2)
  $count = (Get-ChildItem -Path $path -Directory).Count
  Write-Host "Workshop content folder: $path"
  Write-Host "Total size: $sizeGB GB"
  Write-Host "Item count: $count"
} else {
  Write-Host "Workshop content folder not found at expected path."
}

The output reports the total size and count of Workshop items currently cached. The cohort recommendation is to run this snippet before any clear-and-rebuild operation so the player has a baseline to compare against after the rebuild completes.

Snippet 4: check available free space on the Steam drive

# Report free space on the drive holding Steam
Get-PSDrive C | Select-Object Name, @{N='UsedGB';E={[math]::Round($_.Used/1GB,2)}}, @{N='FreeGB';E={[math]::Round($_.Free/1GB,2)}}

The output reports current used and free space on the drive. The cohort recommendation is to maintain at least 10 GB of free space on the Steam drive at all times to accommodate Workshop content for new joins.

Snippet 5: confirm Steam is currently running

# Confirm Steam client is running
$steam = Get-Process -Name "steam" -ErrorAction SilentlyContinue
if ($steam) {
  Write-Host "Steam is running (PID $($steam.Id))."
} else {
  Write-Host "Steam is NOT running. Workshop downloads cannot proceed."
}

The output confirms whether the Steam client is running. A common cohort-observed cause of stuck Workshop downloads is that Steam has crashed silently during the join; restarting Steam resolves the stuck downloads.

Cross-references

• Server Lag and Latency Troubleshooting — the previous article in the troubleshooting section; covers in-game lag that is sometimes mistaken for very slow loading.
• Why Did the Server Crash? — the next article; covers cases where the server itself has crashed, which can present as a stuck loading screen if the crash happens mid-join.
• Server Connection Timeout — covers the handshake-failure flavor in detail.
• Is the Server Up? — useful for confirming the server is actually reachable before investigating client-side loading issues.
• Why is the Server Down? — covers cases where the server is unreachable, which can manifest as an indefinitely stuck loading screen.
• Why Self-Hosting is Preferred — operator-side context for the self-hosting configuration that minimises content-related loading failures.
• Recommended Server Hardware — operator-side guidance that affects the server's ability to push content to clients quickly.

External references

• Unturned official Steam Store page: https://store.steampowered.com/app/304930/Unturned/
• Smartly Dressed Games official modding documentation: https://docs.smartlydressedgames.com/

Document history

Version	Date	Author	Notes
1.0	2024-08-05	57 Studios	Initial publication. Two failure modes documented.
1.1	2024-11-12	57 Studios	Added Workshop cache revalidation procedure.
1.2	2025-02-28	57 Studios	Added disk-speed comparison and EAC reinstall method.
2.0	2025-06-14	57 Studios	Major revision. Added client log analysis appendix and pre-flight checklist.
2.1	2026-05-18	57 Studios	Annual refresh. Added cohort case studies.

Glossary

• Workshop — Steam's user-generated content distribution system. Unturned uses Steam Workshop to deliver mods to clients.
• App ID — Steam's internal identifier for a game. Unturned's App ID is 304930.
• Workshop content folder — the local directory where Steam stores downloaded Workshop files. For Unturned: steamapps/workshop/content/304930/.
• Cold cache — the state where no Workshop content is downloaded locally. The first join to any server starts cold.
• Warm cache — the state where Workshop content is already downloaded locally. Subsequent joins after a successful one start warm.
• EAC — Easy Anti-Cheat. The anti-cheat system used by Unturned. Initialises during the join sequence and can fail there.
• Mod hash — a cryptographic fingerprint of a Workshop item's content. The server validates that the client's hash matches the server's expected hash.
• Download Region — Steam's configuration setting that selects which data center handles Workshop downloads for the client.

Closing note

A stuck Unturned loading screen is one of two distinct failure modes that look superficially similar. Distinguishing "Connecting" from "Loading world" is the first step in any diagnostic, and identifying the right method for the right failure mode resolves the majority of cohort-reported stuck-loading tickets in under fifteen minutes.

The cohort-validated workflow is to read the on-screen text first, check Steam's download activity second, read the client log third, and only then attempt remedies. A player who internalises the diagnostic flowchart can typically resolve a stuck loading screen on the first attempt rather than cycling through unrelated remedies.

Next steps

If the server appears to have crashed or vanished entirely, continue to Why Did the Server Crash?. Return to the section overview at Troubleshooting for a list of all articles in this section.