How to Launch Unturned for the First Time

Launching Unturned™ for the first time is the final step in the install pipeline and the prerequisite for nearly every modding activity the 57 Studios™ Knowledge Base covers in later sections. The first launch is distinct from every subsequent launch because the game performs one-time initialization tasks: it compiles a shader cache, bootstraps the Easy Anti-Cheat client, generates default configuration files in the user-data folder, and registers itself with Steam for play-time tracking. This reference walks through each of those tasks in order, explains what each one does, and concludes with a checklist of files you should see in your user-data folder once the first launch completes successfully.

The first launch is also the first time the game writes files outside its install folder. The user-data folder at %AppData%\Unturned is created during this launch and becomes the home for settings, saves, logs, and Workshop subscription metadata for the rest of the game's lifetime on this machine. Understanding the first-launch sequence is the foundation for understanding the user-data folder, which is referenced repeatedly across the rest of the knowledge base.

Pro tip

Complete your first launch on a wired internet connection rather than wireless. Easy Anti-Cheat bootstrapping involves network handshakes that are sensitive to packet loss, and a stable wired connection reduces the chance of a first-launch failure.

Prerequisites

You need Unturned installed and verified (covered in previous articles), Steam running and signed in, and a stable internet connection. The article assumes you have located the install folder and read the previous articles in this section.

What you'll learn

By the end of this article you will be able to:

• Launch Unturned from Steam for the first time
• Recognize each phase of the first-launch initialization
• Navigate the main menu and confirm the game is running correctly
• Locate the configuration files written to your user-data folder
• Reference Smartly Dressed Games' official getting-started documentation for next steps
• Diagnose common first-launch failures
• Maintain a clean first-launch state across multiple machines

Background: what happens on first launch

The first launch of Unturned is not a single event but a sequence of distinct initialization phases. Each phase produces specific output on disk, and understanding the sequence helps you diagnose problems if the launch does not complete cleanly.

The sequence diagram above shows the full first-launch flow. The Steam client launches Easy Anti-Cheat first, then launches Unturned with the anti-cheat client attached. The Unturned executable then performs its own initialization: shader compilation, configuration file creation, and Unity runtime startup. The total first-launch time on a typical machine ranges from thirty seconds to several minutes depending on hardware.

Did you know?

Shader compilation only happens on the first launch and on launches that follow a graphics-driver update. On subsequent launches the shaders are read from a cache on disk, which makes those launches significantly faster.

The first-launch phases in detail

Each phase of the first launch has its own duration profile and its own failure modes. The following table summarises the phases.

Phase	Typical duration	Primary bottleneck	Most common failure mode
Steam pre-launch	Less than a second	Steam client	Steam not running
EAC bootstrap	A few seconds	Anti-cheat service	EAC permission denied
Process launch	A few seconds	Operating system	Anti-virus interception
Shader compilation	30 seconds to several minutes	CPU	Shader cache write failure
Configuration file creation	A few seconds	Disk write	User-data folder permission denied
Unity runtime initialization	A few seconds	CPU and GPU	Graphics driver mismatch
Splash screen	A few seconds	GPU	Display configuration mismatch
Main menu	A few seconds	All systems	Network failure

The phase table above is the diagnostic reference for first-launch failures. If a phase takes longer than the expected duration or fails entirely, the table maps the symptom to the most likely cause.

Step 1: Click Play

From the Steam Library, locate Unturned and click the blue Play button. Steam will:

1. Display a brief "Launching Unturned" overlay
2. Launch the Easy Anti-Cheat service
3. Launch Unturned with anti-cheat attached
4. Track the launch in your Steam play time

Common mistake

Beginners sometimes click Play repeatedly when the game appears to be doing nothing during the first launch. Each click can spawn a new launch attempt, which competes for the same resources and slows everything down. Wait at least sixty seconds before assuming the launch has failed.

The Steam launching overlay

When you click Play, Steam displays a small overlay showing "Launching Unturned." This overlay confirms Steam has received the click and is initiating the launch sequence. The overlay disappears as soon as Unturned's process starts.

If the overlay appears and then disappears immediately without the game starting, the most likely cause is an anti-virus tool intercepting the launch. Check the anti-virus quarantine for Unturned-related entries; add Unturned and Steam to the exclusion list if entries are present.

Alternative launch methods

Beyond the Steam Library Play button, several alternative launch methods exist. Each has specific use cases.

Launch method	When to use
Steam Library Play button	Default; works for every user
Desktop shortcut to Steam URL	Convenient for frequent launches
steam://run/304930 URL	Triggers the same launch from any application
Direct execution of Unturned.exe	Not supported; requires Steam authentication
Big Picture mode	For controller-driven workflows
Command-line via Steam	For automated workflows

The Steam Library Play button is the recommended method for the first launch. Alternative methods are useful for subsequent launches but introduce variables that complicate first-launch troubleshooting.

Step 2: Allow Easy Anti-Cheat to bootstrap

Easy Anti-Cheat (EAC) is a third-party anti-cheat service that runs alongside Unturned. On the first launch, EAC may display a brief dialog asking for permission to install. Accept the dialog.

EAC's bootstrap process performs the following actions:

• Registers a Windows service that runs in the background while Unturned is open
• Validates the integrity of Unturned's executable files
• Establishes a connection to EAC's verification servers
• Generates a per-machine identifier used for anti-cheat reporting

Critical warning

Do not attempt to bypass, disable, or modify Easy Anti-Cheat. Many official multiplayer servers refuse connections from clients without EAC running, and tampering with anti-cheat files can result in a game ban that affects your Steam account.

What EAC creates on disk

EAC's bootstrap leaves files in several locations. Understanding what gets created is useful for diagnosing EAC-related problems.

EAC artifact	Location
EAC client files	<install folder>\EasyAntiCheat
EAC Windows service	Registered with the Windows service manager
EAC configuration	Per-game configuration stored in the install folder
EAC machine identifier	Stored in a system-level location
EAC log files	<install folder>\EasyAntiCheat\Logs

The EAC artifacts above are normal and expected. The Windows service is started automatically when Unturned launches and stops when Unturned closes.

Common EAC bootstrap problems

EAC bootstrap is the most common source of first-launch failures. The following table maps common EAC failures to their recovery procedures.

EAC failure symptom	Most likely cause	Recovery procedure
UAC prompt denied	User declined the elevation request	Retry the launch and accept the UAC prompt
EAC service installation fails	Anti-virus interception	Add EAC and Unturned to anti-virus exclusions
EAC validation reports modified files	Install folder tampering or corruption	Run a Steam verification
EAC cannot contact servers	Firewall or network problem	Check firewall rules; ensure outbound HTTPS is allowed
EAC reports unsupported system	Operating system not on EAC's compatibility list	Confirm Windows version is supported
EAC repeatedly crashes	EAC client corruption	Re-install EAC through the launcher in the install folder

The EAC failure table above covers the common cases. Less common failures usually require contacting Smartly Dressed Games support or consulting the official documentation at https://docs.smartlydressedgames.com/en/latest/about/getting-started.html.

Step 3: Wait for shader compilation

After EAC initializes, Unturned begins compiling its shader cache. This phase produces no obvious visual indicator. The game window may appear black, blank, or unresponsive while shader compilation runs. This is normal and is not a sign of failure.

The flowchart above shows the expected progression. A blank window for up to five minutes is normal on the first launch. A blank window beyond five minutes, especially if Task Manager shows no CPU activity from Unturned.exe, suggests the launch has stalled.

Best practice

Open Task Manager on your second monitor (if available) during the first launch. Observing Unturned.exe's CPU usage gives you confidence that the process is doing real work even when the game window appears blank.

What shader compilation actually does

Shader compilation translates the game's high-level shader source code into the binary format the specific GPU on your machine can execute. The translation is hardware-specific, which is why shaders are compiled on each new machine and after each driver update rather than shipped pre-compiled.

Shader compilation aspect	Description
Input	High-level shader source code shipped with the game
Output	GPU-specific binary shaders cached on disk
Trigger	First launch; graphics driver update; clearing the shader cache
Duration	30 seconds to several minutes depending on CPU
Cache location	Per-machine in a Steam-managed shader cache
Cache size	A few hundred MB for Unturned

The shader compilation table above is the reference for what is happening during the blank-window phase. The phase is CPU-intensive rather than GPU-intensive; a fast CPU shortens this phase noticeably.

Why the screen appears blank

The blank screen during shader compilation is a function of how Unity initialises rendering. Unity creates the game window before shaders are ready, then waits for shader compilation to complete before rendering anything. The window exists but has nothing to display until shaders are ready.

This is normal Unity behaviour and is not specific to Unturned. Other Unity games exhibit similar blank-window phases on first launch. The behaviour is correct even though it looks like a failure.

Pro tip

On a slow CPU, the shader compilation phase can take several minutes. The compilation runs in parallel with other Unity initialisation, so the apparent freeze is less severe than it looks. Patience during the first launch saves the trouble of restarting and re-running the compilation.

Step 4: Reach the main menu

Once shader compilation finishes and Unity finishes initializing, Unturned displays its splash screen briefly, then transitions to the main menu. The main menu contains the standard set of options:

• Play — open the single-player or multiplayer menus
• Workshop — browse and subscribe to community-created content
• Configure — adjust graphics, audio, controls, and other settings
• Multiplayer — connect to a server or host a local game
• Singleplayer — start a single-player session on an official or custom map
• Quit — exit the game

Pro tip

The first thing experienced modders do at the main menu is open Configure to Graphics and lower the graphics preset to Low. Mod development involves frequent restarts, and a fast launch matters more than visual fidelity during development.

Reading the main menu state

The main menu shows several status indicators that confirm the game is in a healthy state. Reading these indicators on the first launch establishes a baseline for what a normal main menu looks like.

Main menu indicator	Healthy state
Game version number in the corner	Matches the version Steam reports
Steam connection icon	Connected
EAC status	Active or running
Workshop button	Enabled and clickable
Multiplayer button	Enabled and clickable
Singleplayer button	Enabled and clickable
Background animation or art	Rendering smoothly
Audio	Background music playing

The indicators above are a quick sanity check. Any disabled button or missing indicator suggests a problem that should be addressed before proceeding to gameplay.

Initial configuration recommendations

The first time you reach the main menu, several configuration changes are worth making before any gameplay. The following list is the modder-recommended initial configuration.

1. Open Configure to Graphics. Lower the graphics preset to Low for faster launches during development.
2. Open Configure to Audio. Confirm audio is routed to the expected output device.
3. Open Configure to Controls. Familiarise yourself with the default key bindings.
4. Open Configure to Display. Confirm the display mode (fullscreen, windowed, borderless) matches your preference.
5. Open Workshop. Subscribe to a starter set of community content if desired.

The initial configuration above is a one-time investment that pays back across every subsequent launch. The Low graphics preset is the most impactful single change; subsequent launches reach the main menu in seconds rather than tens of seconds.

Step 5: Confirm configuration files were written

After reaching the main menu for the first time, Unturned writes a set of default configuration files to your user-data folder. The user-data folder lives at %AppData%\Unturned (which expands to C:\Users\<your username>\AppData\Roaming\Unturned on a typical Windows install).

File or folder	Purpose
Settings.json	Graphics, audio, and control settings
Bindings/	Keyboard and gamepad input mappings
Players/	Per-player save data
Logs/	Log files from each play session
Servers.json	Saved multiplayer server entries
Maps/	User-created or downloaded map source folders
Workshop/	Subscribed Workshop content
Cloud.json	Steam Cloud sync state
Crashes/	Crash dump files

The table above lists the files and folders Unturned creates during its first launch. Not every file appears immediately; some are created the first time their feature is used. The presence of Settings.json and the Logs folder is the most reliable confirmation that the first launch completed successfully.

Did you know?

Most Windows applications store user data under %AppData%. The Roaming portion of the path means that if your Windows account is part of an enterprise domain with roaming profiles, your Unturned settings would follow you to any other domain-joined computer. Most home users do not have roaming profiles, so the data stays on the local machine.

Verifying the user-data folder contents

Open File Explorer and navigate to %AppData%\Unturned. The folder should contain the expected files and subdirectories listed in the table above. The verification is a small step that confirms the first launch wrote everything it was supposed to write.

Verification check	Pass criterion
%AppData%\Unturned folder exists	Folder is present
Settings.json file present	File is present at the folder root
Logs subfolder present	Folder is present
At least one log file in Logs	Log file from the first launch is present
Players subfolder present	Folder is present
Bindings subfolder present	Folder is present
Crashes subfolder	Created the first time a crash happens; may not be present yet
Steam Cloud sync indicator	Cloud icon visible in folder if Steam Cloud is enabled

The verification checks above confirm a clean first launch. Missing files or folders should be investigated before declaring the first launch successful.

Reading the first log file

The first log file in %AppData%\Unturned\Logs contains the diagnostic output from the first launch. Opening the log file in a text editor reveals the sequence of events the game went through.

A clean first launch produces a log file with a successful initialisation sequence: graphics device created, audio system initialised, Workshop client connected, main menu loaded. Errors or warnings in the log file are worth investigating; they often indicate problems that will surface during later gameplay.

Pro tip

Keep the first log file as a baseline reference. Future log files can be compared against this baseline to spot anomalies introduced by mods, drivers, or system changes. The log files are plain text and small; storing them takes minimal space.

Step 6: Read the official getting-started documentation

Smartly Dressed Games, the developer of Unturned, maintains official documentation that complements this knowledge base. The official getting-started page lives at https://docs.smartlydressedgames.com/en/latest/about/getting-started.html. The 57 Studios Knowledge Base is written to be read alongside the official docs, not as a replacement for them.

The official documentation covers:

• Overview of Unturned's modding architecture
• Reference for the asset file format
• Reference for the configuration file format
• Guidance on publishing to the Steam Workshop
• API documentation for plugin developers

Best practice

Bookmark the Smartly Dressed Games documentation in your browser before starting any modding work. You will reference it constantly throughout your modding career, and the official documentation is the authoritative source for any topic on which this knowledge base and the official docs disagree.

How the two documentation sources relate

The 57 Studios Knowledge Base and the Smartly Dressed Games official documentation serve complementary purposes. Understanding the relationship clarifies which source to consult for a given question.

Topic category	Primary source
Step-by-step workflow walkthroughs	57 Studios Knowledge Base
Asset file format specifications	Smartly Dressed Games documentation
Troubleshooting common problems	57 Studios Knowledge Base
API reference for plugin development	Smartly Dressed Games documentation
Mod publishing procedures	Smartly Dressed Games documentation
Drive layout and Steam configuration	57 Studios Knowledge Base
Game version-specific changes	Smartly Dressed Games documentation
Best-practice patterns from active modders	57 Studios Knowledge Base

The relationship table above shows the division of labour. The knowledge base is workflow-oriented; the official documentation is specification-oriented. Both are necessary for comprehensive coverage.

Advanced considerations

A few advanced points are worth noting for users who plan to launch Unturned frequently during mod development.

Launch options

Steam supports per-game launch options that pass command-line arguments to the game. Mod developers frequently set launch options that disable the loading splash, force a window mode, or enable detailed logging. Launch options are configured through Right-click to Properties to General to Launch Options.

Launch option	Effect
-nosplash	Skip the splash screen on launch
-windowed	Force windowed mode regardless of saved setting
-noeac	Disable Easy Anti-Cheat (single-player only)
-verbose	Enable detailed logging
-skipupdates	Skip update checks on launch
-debug	Enable debug mode for development

The launch option table above is a partial reference; the Smartly Dressed Games official documentation maintains the authoritative list. Use launch options sparingly during development; they can mask problems that would otherwise surface and be caught.

Headless server launches

In addition to Unturned.exe, the install folder contains Unturned_Headless.exe. This executable launches the game in dedicated-server mode without rendering graphics. Mod developers who test server-side plugins use the headless executable. The headless executable does not require a first-launch initialization separate from the client first launch.

The headless executable shares the install folder with the client. It does not require its own EAC bootstrap or its own shader cache because it renders no graphics. The first headless launch is therefore faster than the first client launch.

Verifying the EAC installation

If you suspect Easy Anti-Cheat is not running correctly, you can verify the EAC installation through the EasyAntiCheat subfolder inside the Unturned install folder. The folder contains an installer executable that can be run to repair the EAC client.

EAC repair scenario	Recommended action
EAC bootstrap fails on launch	Run the EAC installer in the install folder
EAC reports modified files	Run Steam verification first; then run EAC installer
EAC service not present in Windows	Run the EAC installer with administrator privileges
EAC repeatedly crashes Unturned	Run a clean re-install of EAC through the installer

The EAC repair scenarios above are the documented recovery paths. The EAC installer in the install folder is the supported tool for EAC maintenance.

Subsequent launches versus first launches

Every launch after the first is dramatically faster than the first. The following table compares the two.

Launch aspect	First launch	Subsequent launches
EAC bootstrap	Full bootstrap; UAC prompt	Service already running; instant
Shader compilation	Full compilation	Read from cache; instant
Configuration file creation	Defaults written	Existing files loaded
Unity runtime initialisation	Full initialisation	Faster after first launch
Total time	30 seconds to several minutes	A few seconds

The comparison table above shows why the first launch is so much slower than subsequent launches. The cost of the first launch is paid once per machine and once per major graphics-driver update; every other launch benefits from the cached state.

FAQ

My first launch is taking ten minutes. Is something wrong?

Probably not. Shader compilation on slower CPUs can take longer than five minutes. If the game window shows any activity in Task Manager and the process has not crashed, wait longer. If the process is using zero CPU for an extended period, investigate.

Why does the screen go black between the splash and the main menu?

This is normal during Unity initialization. The black screen is a brief gap between phases of the engine startup.

I see a Windows User Account Control prompt. Should I accept it?

Yes, if the prompt is for Easy Anti-Cheat. EAC needs elevated permissions to install its background service. Subsequent launches will not show this prompt.

Where do I find the log files from my first launch?

Inside %AppData%\Unturned\Logs. The log file for the most recent session is the one with the most recent timestamp.

Can I skip the first-launch initialization by copying configuration files from another computer?

This is possible for some files (such as Settings.json and Bindings), but the shader cache and EAC bootstrap are machine-specific and cannot be transferred. A full first launch on each machine is the supported path.

What if Unturned crashes during the first launch?

Check the log file in %AppData%\Unturned\Logs for diagnostic information. The most common causes of first-launch crashes are graphics driver problems, EAC bootstrap failures, and anti-virus interception. Each cause has a specific recovery procedure documented in this article.

Can I launch Unturned without Steam running?

No. Steam must be running and signed in for Unturned to launch. The launch flow requires Steam authentication and EAC bootstrap, both of which depend on Steam.

How do I make the first launch faster?

Several preparation steps reduce first-launch time:

• Use a wired internet connection rather than wireless
• Add Steam and Unturned to your anti-virus exclusions
• Close other CPU-intensive applications during the first launch
• Use an SSD rather than a mechanical hard drive
• Update graphics drivers before the first launch

The preparation steps above each shave time off the first launch. Combined, they can reduce a first launch from several minutes to under a minute on capable hardware.

Does the first launch send data to Smartly Dressed Games?

Yes, in a limited form. The first launch establishes the EAC machine identifier and registers the install with Steam. The data exchange is described in Smartly Dressed Games' privacy documentation; the data sent is the minimum necessary for anti-cheat verification and play-time tracking.

Can I run Unturned in offline mode after the first launch?

Yes. Once the first launch completes, Steam can be put into offline mode and Unturned will launch from the cached authentication state. Some online features (multiplayer, Workshop) require an active connection, but single-player gameplay works offline.

What happens if I close Unturned mid-first-launch?

The first launch resumes from the same starting point on the next launch. The shader cache is incremental, so partial progress is preserved. The EAC bootstrap may need to re-run if it had not completed.

How do I confirm the first launch was successful?

Three criteria together confirm a successful first launch: the main menu appears and is responsive; Settings.json exists in %AppData%\Unturned; the first log file in %AppData%\Unturned\Logs ends with a clean shutdown entry rather than a crash entry. All three together is a reliable confirmation.

Best practices

• Use a wired internet connection for the first launch
• Wait at least sixty seconds before assuming a stalled launch
• Lower the graphics preset to Low immediately for faster subsequent launches
• Bookmark the Smartly Dressed Games official documentation
• Confirm Settings.json and the Logs folder appear in %AppData%\Unturned before declaring the first launch successful
• Run Task Manager during the first launch to monitor process activity
• Save the first log file as a baseline reference
• Update graphics drivers before the first launch
• Close other CPU-intensive applications during the first launch
• Accept the EAC UAC prompt on the first launch

Appendix A: first-launch troubleshooting reference

The following table maps common first-launch failure symptoms to their most likely cause and recommended response.

Symptom	Most likely cause	Recommended response
Game does not start at all	Steam not running or signed out	Confirm Steam is running and signed in
Game starts and immediately closes	EAC bootstrap failure	Check Easy Anti-Cheat installer in install folder
Game window appears black for too long	Shader compilation in progress	Wait; verify CPU activity in Task Manager
Game crashes during shader compilation	Graphics driver problem	Update graphics drivers; reboot; retry
Main menu appears with errors visible	Network or asset problem	Run Steam verification
Main menu does not respond	UI thread frozen	Wait; restart if frozen longer than a few minutes
Configuration files not written	Permission problem on AppData	Confirm AppData folder permissions for current user
Steam play-time not tracked	Steam offline mode	Put Steam into online mode for first launch
EAC reports installation failure	Anti-virus interception	Add Steam and Unturned to anti-virus exclusions
First launch never reaches main menu	Combination of factors	Check log file in AppData; address specific errors

The troubleshooting reference above covers the common cases. Less common failures usually require log file analysis or support contact.

Appendix B: first-launch timing reference

The following table shows typical first-launch durations for different hardware configurations.

Hardware configuration	Typical first-launch duration
High-end modern PC (recent CPU, NVMe SSD, modern GPU)	30 to 60 seconds
Mid-range modern PC	1 to 2 minutes
Budget modern PC	2 to 4 minutes
Older PC (CPU 5+ years old)	4 to 8 minutes
Laptop with integrated graphics	5 to 12 minutes
Steam Deck or similar handheld	3 to 6 minutes

The timing reference above is a planning tool. If your first launch significantly exceeds the value for your hardware tier, the most likely cause is anti-virus interception or a graphics driver problem.

Pro tip

A first launch that takes more than twice the expected duration is a strong signal of a configuration problem. The most common culprit is anti-virus software scanning every shader as it is compiled. Adding Unturned to the anti-virus exclusions is a single-change fix that can reduce the first-launch time by half or more.

Appendix C: first-launch artefacts reference

The first launch creates artefacts in several locations. The following table is a comprehensive list.

Artefact	Location	Purpose
Settings.json	%AppData%\Unturned\	Graphics, audio, and control settings
Bindings folder	%AppData%\Unturned\Bindings\	Input mappings
Players folder	%AppData%\Unturned\Players\	Per-player save data
Logs folder	%AppData%\Unturned\Logs\	Session log files
Servers.json	%AppData%\Unturned\	Multiplayer server list
Maps folder	%AppData%\Unturned\Maps\	User maps
Workshop folder	%AppData%\Unturned\Workshop\	Workshop subscriptions
Cloud.json	%AppData%\Unturned\	Steam Cloud sync state
Crashes folder	%AppData%\Unturned\Crashes\	Crash dumps (created on first crash)
Shader cache	Steam-managed shader cache	Pre-compiled GPU shaders
EAC service registration	Windows service manager	Anti-cheat service
Steam play-time entry	Steam Library	Play-time tracking

The artefacts table above is the canonical list of what the first launch creates. Modders refer to this list when diagnosing problems that may originate in any of the first-launch artefacts.

Appendix D: first-launch best practices for multiple machines

Modders who develop on multiple machines (a primary desktop and a laptop, for example) face the question of how to handle first launches across machines. The following practices describe the recommended approach.

Per-machine first launch

Each machine requires its own complete first launch. The shader cache is machine-specific, the EAC machine identifier is machine-specific, and the user-data folder is per-Windows-user. Attempting to copy these artefacts between machines is not supported and usually fails.

Sharing settings across machines

The portable artefacts are the user-level settings: Settings.json, Bindings, and Servers.json. These files can be copied between machines after each machine's first launch. The result is a consistent user experience across machines without violating the per-machine first-launch requirement.

Artefact	Portable across machines	Why
Settings.json	Yes	Plain configuration
Bindings	Yes	Plain configuration
Servers.json	Yes	Plain configuration
Players	Sometimes; depends on Steam Cloud	Save data
Logs	No	Machine-specific runtime data
Maps	Yes, if hand-managed	User content
Workshop	No; managed by Steam per machine	Subscription state
Cloud.json	No	Machine-specific sync state
Crashes	No	Machine-specific runtime data
Shader cache	No	Machine-specific GPU output
EAC identifier	No	Machine-specific anti-cheat state

The portability table above shows which artefacts can be shared. Maintaining a personal git repository or cloud-sync folder containing the portable artefacts is a common pattern among modders who work across multiple machines.

Setting up a new machine

The recommended sequence for setting up a new machine is:

1. Install Steam
2. Install Unturned
3. Verify the install
4. Run the first launch through the steps in this article
5. Copy portable user settings from your reference machine
6. Verify the settings are loaded correctly

The sequence above is the supported path. It produces a consistent user experience across machines while respecting the per-machine first-launch requirement.

Appendix E: first-launch mental model

The first launch can be thought of as a four-stage initialisation: external services (Steam and EAC), local executable launch, internal initialisation (shader compilation and Unity runtime), and user-data folder creation.

                              The Unturned first-launch mental model


              +-------------------+         +-------------------+
              |                   |         |                   |
              |  STAGE 1          |  ====>  |  STAGE 2          |
              |  EXTERNAL         |         |  PROCESS LAUNCH   |
              |  SERVICES         |         |                   |
              |                   |         |                   |
              |  Steam + EAC      |         |  Unturned.exe     |
              +-------------------+         +-------------------+
                                                      |
                                                      v
              +-------------------+         +-------------------+
              |                   |         |                   |
              |  STAGE 4          |  <====  |  STAGE 3          |
              |  USER-DATA        |         |  INTERNAL INIT    |
              |  FOLDER           |         |                   |
              |                   |         |                   |
              |  %AppData%\       |         |  Shaders + Unity  |
              |  Unturned         |         |                   |
              +-------------------+         +-------------------+

The four-stage model above is the mental scaffold for understanding the first launch. Each stage has its own duration and its own failure mode; the diagnostic procedure for any first-launch problem starts by identifying which stage failed.

Stage	Approximate duration	Output
Stage 1: External services	A few seconds	Steam authentication; EAC service running
Stage 2: Process launch	A few seconds	Unturned.exe process started
Stage 3: Internal init	30 seconds to several minutes	Shader cache; Unity ready
Stage 4: User-data folder	A few seconds	%AppData% folder populated

The stage breakdown above is the diagnostic scaffold. Most first-launch problems map cleanly to one of these four stages.

Appendix F: glossary of first-launch terms

The following terms appear throughout this article. The working definitions provided here align with Smartly Dressed Games' official documentation.

• AppData folder — Windows per-user directory at %AppData%. Unturned's user-data folder lives inside it.
• EAC — Easy Anti-Cheat; the third-party anti-cheat service that runs alongside Unturned.
• First launch — The first time a game is run after install. Performs one-time initialisation that subsequent launches skip.
• Headless executable — Unturned_Headless.exe; the dedicated-server version of Unturned that runs without graphics.
• Launch option — Command-line argument passed to Unturned by Steam. Configured per game in Steam's Properties dialog.
• Main menu — The top-level UI screen Unturned displays after initialisation. The endpoint of a successful first launch.
• Roaming profile — Windows feature that follows a user's settings across domain-joined computers. Most home users do not have a roaming profile.
• Shader cache — Machine-specific cache of pre-compiled GPU shaders. Built during the first launch and reused thereafter.
• Steam play-time — Cumulative time the Steam client has tracked the game as running. First launch starts the play-time counter.
• User-data folder — %AppData%\Unturned; the per-user directory containing settings, saves, and logs.

The glossary above is the vocabulary used by Steam, Smartly Dressed Games, and the rest of the install pipeline. Familiarity with these terms makes the rest of the knowledge base easier to navigate.

Appendix G: closing the install pipeline

The first launch is the last article in the install pipeline. With Unturned installed, verified, located on disk, library folder configured, and launched once successfully, the install pipeline is complete.

The next section of the knowledge base covers Windows file management skills that build on the install pipeline. The skills are prerequisites for the modding sections that follow.

Section	Builds on
File management	Install pipeline (this section)
Modding fundamentals	Install pipeline plus file management
Mapping	Modding fundamentals
Item creation	Modding fundamentals
Vehicle creation	Modding fundamentals
Module development	Modding fundamentals plus programming skills
Workshop publishing	Modding fundamentals plus Smartly Dressed Games documentation

The section dependency table above shows the knowledge base's overall structure. The install pipeline is the foundation; every subsequent section depends on the install pipeline being complete and well understood.

Appendix H: first-launch user experience by hardware tier

The first-launch experience varies substantially across hardware tiers. The following narrative descriptions capture what each tier of user typically observes.

High-end modern PC

The Play button is clicked. Within a few seconds, the Steam launching overlay appears and disappears. The Easy Anti-Cheat prompt appears briefly; the user accepts it. The game window appears and is blank for about 30 seconds while shaders compile. The splash screen briefly displays. The main menu appears, fully responsive. Total elapsed time is under a minute.

The user-data folder is populated immediately. Settings.json is present. The first log file shows a clean initialisation sequence. The user lowers graphics to Low and is ready for modding work.

Mid-range PC

The same sequence unfolds over 90 seconds to 2 minutes. The shader compilation phase is the longest single phase. The user may pause to check Task Manager during the blank-window phase, observe that Unturned.exe is using CPU, and wait through the remaining compilation.

The user-data folder is populated normally. The first log file is similar to the high-end case. The user adjusts graphics settings and proceeds.

Budget PC

The first launch can take 3 to 5 minutes. The shader compilation phase is significant. The user may be concerned that the launch has stalled; checking Task Manager confirms active CPU usage. Patience is the operative word.

Once the main menu appears, the user-data folder is populated correctly. The first log file may include warnings about graphics capability that are worth noting but not necessarily addressing.

Laptop with integrated graphics

The first launch on a laptop with integrated graphics can take 5 to 10 minutes. Integrated graphics often share system memory and have lower thermal headroom, which extends the shader compilation phase substantially.

The user-data folder is populated correctly after the main menu appears. The first log file may include performance warnings; the user should expect lower-than-typical frame rates and consider the Low graphics preset as the default rather than the development-time choice.

Steam Deck or handheld

The Steam Deck and similar handhelds typically take 3 to 6 minutes for the first launch. The handheld's CPU is competitive with mid-range desktop hardware; the shader compilation phase is the limiting factor. The first launch on a handheld is performed once and the cached shaders are reused for every subsequent launch.

Touch-based main menu interaction works correctly on handhelds. The user-data folder location is the same on Linux-based handhelds with case-sensitive path conventions adjusted.

Appendix I: post-first-launch workflow integration

After a successful first launch, the modder transitions from install to active development. The following workflow patterns are observed among productive Unturned modders.

Daily startup sequence

On a day with planned modding work, the daily startup sequence is approximately:

1. Boot the machine
2. Open Steam; sign in if not already signed in
3. Launch Unturned from the Steam Library
4. Confirm the game reaches the main menu in the expected subsequent-launch duration
5. Briefly enter and exit a single-player session to confirm gameplay works
6. Close Unturned
7. Open the install folder and the user-data folder
8. Begin the day's modding work

The startup sequence above takes about 2 minutes on a modern machine. It establishes the day's working state and confirms the install is healthy.

Pre-development check

Before starting work on a specific mod, the recommended pre-development check is:

1. Open Steam and confirm Unturned is up to date
2. Run a verification if a major update has been installed since the last work session
3. Confirm the install folder permissions are unchanged
4. Confirm the user-data folder is populated correctly
5. Open the Smartly Dressed Games documentation in a browser tab for reference
6. Open File Explorer windows pinned to the relevant subdirectories
7. Begin the day's work

The pre-development check is a small investment that catches problems before they affect the day's work. Most days the check produces no findings; on the rare day when something is amiss, catching it early saves substantial debugging time.

Session shutdown

At the end of a modding session, the recommended shutdown sequence is:

1. Save any unsaved work in mod tools
2. Back up modified custom subdirectories to your backup destination
3. Close Unturned cleanly through the main menu Quit option
4. Note any anomalies observed during the session in a personal log
5. Close associated File Explorer windows and mod tools

The shutdown sequence preserves the day's work and creates a clean baseline for the next session. The personal log is a high-value habit; reviewing accumulated notes weekly catches patterns that would otherwise go unnoticed.

Appendix J: relationship with the Smartly Dressed Games documentation

The Smartly Dressed Games official documentation at https://docs.smartlydressedgames.com/en/latest/about/getting-started.html provides additional reference material relevant to the first launch.

Specifically, the official documentation covers:

• The Unturned modding architecture overview that complements the first-launch material in this article
• Detailed reference for the asset file format used in mod development
• Detailed reference for the configuration file format that this article touches on briefly
• Guidance on publishing custom content to the Steam Workshop
• API documentation for plugin developers writing server-side modules

When the knowledge base and the official documentation disagree on any topic, the official documentation is authoritative. This article aligns with the official documentation as of its most recent revision.

The official documentation does not cover certain practical workflow topics that the knowledge base covers in depth: drive layout selection, library folder management, verification cadence, multi-machine modding workflows. The two resources together provide comprehensive coverage; reading both in parallel is the recommended approach for serious modders.

Best practice

Use the Smartly Dressed Games documentation as the authoritative reference for file formats, API specifications, and Workshop publishing procedures. Use the 57 Studios Knowledge Base for workflow patterns, setup decisions, and troubleshooting procedures. The two roles are complementary, and the productive modder consults both.

Cross-references

• How to Install Unturned — the install procedure
• How to Verify Unturned Game Files — verification before first launch
• How to Find Your Unturned Install Folder — locating the install folder
• Where Steam Installs Games by Default — library folder model
• How to Open File Explorer — the next section of the knowledge base

Document history

Version	Date	Author	Notes
1.0	2024-09-20	57 Studios	Initial publication
1.1	2024-12-15	57 Studios	Added sequence diagram and EAC bootstrap details
1.2	2025-04-22	57 Studios	Added user-data folder reference table
2.0	2026-05-17	57 Studios	Major expansion. Added first-launch mental model, troubleshooting reference, multi-machine guidance, and glossary. Expanded FAQ from 5 to 12 questions.

Next steps

With Unturned installed, verified, located on disk, and launched once successfully, the install pipeline is complete. Proceed to How to Open File Explorer to begin the file-management section of the knowledge base, which covers the Windows skills you will use throughout mod development.