How to Install Steam

Running the Steam installer places the Steam client onto your computer's storage and registers it with Windows. The installation process takes approximately three to ten minutes, depending on the speed of your internet connection and your storage device. This article covers every step from double-clicking SteamSetup.exe through the first time the Steam client window appears on your screen.

57 Studios™ recommends installing Steam to its default location for most users. Custom install locations are useful for advanced configurations, but they complicate later troubleshooting because community guides and Unturned™ mod development tutorials assume the default path. The 57 Studios contributor support log records that approximately one in every fifteen support requests for new modders involves a path-related issue stemming from a non-default Steam install location, and the resolution typically requires the user to provide the custom path before any further assistance can be rendered.

The installer flow itself is well-engineered and progresses smoothly for most users. The principal sources of friction are the User Account Control prompt at the very start, the install location choice in the middle, and the initial client update at the end. Each of these three friction points is documented in detail below along with the recommended response.

Prerequisites

• The Steam installer downloaded as SteamSetup.exe per the previous article
• Administrator access on the Windows account you are using
• At least 1 gigabyte of free space on the install drive (the client itself is small, but it expands with downloads)
• An active internet connection for the initial client update
• A connection that will remain stable for several minutes during the client update
• The understanding that the installation includes a self-update step that downloads several hundred megabytes

What you'll learn

• How to launch the Steam installer safely and verify it is the legitimate version
• How to respond to the User Account Control prompt and what to verify before accepting
• How to choose an installer language and what that choice affects later
• When to accept the default install location versus selecting a custom path
• How the initial client update behaves and how long it typically takes
• Where Steam places its files after installation and what each folder contains
• How to handle a failed installation and recover from a partial install
• How to install Steam to a non-default drive when the system drive is constrained
• How the Windows registry is modified by the installer and what those modifications enable
• How to verify the installation completed successfully

Background

The Steam installer is a small bootstrapper that does three things in sequence. First, it copies a minimal set of files to your chosen install location. Second, it registers Steam with Windows so that the operating system knows how to launch the client and handle steam:// protocol links. Third, it triggers the Steam client to launch for the first time and download the rest of its files directly from Valve's content delivery network.

The bootstrapper architecture is documented in the previous article in this series, How to Download Steam. Understanding the architecture helps make sense of the installation flow: the installer itself is small and finishes quickly, but the subsequent self-update by the launched Steam client is much larger and accounts for the bulk of the total elapsed time.

The diagram above outlines the eight-stage installation flow. The longest stage by far is the final client update, which can range from thirty seconds to several minutes depending on your connection speed.

Step 1: Launch the installer

Open File Explorer and navigate to the folder where you saved SteamSetup.exe. By default, this is C:\Users\<YourUsername>\Downloads. Double-click the file to launch the installer.

Common mistake

If nothing happens when you double-click the file, the file may not have downloaded completely. Return to the previous article and verify the file size is approximately three megabytes. A truncated file will not launch.

Pre-launch verification

Before launching the installer, perform a quick verification that the file is the one you downloaded from the official Valve source. The verification is the same as the post-download verification documented in the previous article and is repeated here for completeness:

1. The file name is exactly SteamSetup.exe.
2. The file size is approximately 3 megabytes.
3. The file's digital signature, visible in the Properties dialog's Digital Signatures tab, is from Valve Corp.
4. The signature's "View Certificate" detail shows a valid certificate chain.

If any of these fail, do not run the installer. Return to the download article and re-download from the official source.

Pro tip

If you maintain a personal installers archive (described in the previous article), launch the installer from the archive rather than from the Downloads folder. The archive copy has been verified once at the time it was placed in the archive, and using it ensures consistency across installations on different machines.

Step 2: Respond to the User Account Control prompt

Windows displays a User Account Control prompt asking whether you want to allow the installer to make changes to your device. The prompt shows the file name SteamSetup.exe and the verified publisher "Valve Corp." Confirm the publisher is "Valve Corp." before clicking "Yes".

If the prompt shows an unverified publisher or any name other than Valve Corp., click "No" immediately. The file you downloaded is not the legitimate Steam installer.

Critical warning

Never click "Yes" on a User Account Control prompt without first reading the publisher name. The UAC prompt is one of the last defenses against running malicious software. A few seconds of attention here prevents serious problems later.

Understanding the UAC prompt anatomy

The UAC prompt displayed for SteamSetup.exe contains several pieces of information that warrant brief explanation:

Element	What it shows	What to verify
Application name	SteamSetup.exe or similar	Matches the file you downloaded
Verified publisher	"Valve Corp."	Reads exactly "Valve Corp."
File origin	Sometimes shows the source URL	Domain matches Steam
Yes/No buttons	Accept or deny elevation	Read prompt before clicking
Show details / More info	Expands the prompt	Reveals full information

The "verified publisher" line is the single most important element. The "verified" part means that Windows has checked the file's digital signature against the publisher claim, and that the signature is valid and chains to a trusted root. An unverified publisher line ("Unknown publisher" in red) indicates that the file is unsigned or that the signature is invalid; do not proceed under either condition.

Did you know?

The UAC prompt is colour-coded. A blue title bar indicates a Microsoft-signed application. A yellow title bar indicates a verified non-Microsoft publisher (which is what Steam's installer should show). A red title bar indicates either an unverified publisher or a blocked application. The colour is a quick visual cue that complements the textual publisher line.

Step 3: Choose the installer language

After UAC, the installer's welcome window appears. The first screen asks you to choose a language for the installer itself. This is the language used during the installation process only. You can change the Steam client's display language later from within the client.

The language list contains approximately thirty options. Select your preferred language and click "Next". For most readers of this knowledge base, the default selection of English is appropriate.

Installer language versus client language

The installer language and the Steam client display language are two distinct settings. The installer language applies only to the installation flow itself (the language of the welcome screen, the install path prompt, the progress messages). The Steam client display language applies to everything inside the Steam client itself after installation completes (the menus, the store, the friends list, the settings).

Setting	Where set	Effect	Changeable later
Installer language	During install	Installer UI only	No (re-install required)
Steam client display language	Inside client	All client UI	Yes
Game language	Per-game settings	Per-game text/audio	Yes (per game)
Browser language	Browser settings	Web-based Steam pages	Yes

The installer language selection is committed for the duration of the installation only. It does not persist into the Steam client or affect any future setting.

Step 4: Choose the install location

The next screen asks you to choose where to install Steam. The default location is C:\Program Files (x86)\Steam. The installer offers a "Browse" button to select a different location.

Default versus custom location

The following table outlines the practical differences between accepting the default install location and selecting a custom path.

Consideration	Default C:\Program Files (x86)\Steam	Custom Location
Setup difficulty	None	Requires path selection
Storage drive	Always system drive (C:)	Any drive you choose
Permissions	Standard for installed programs	May require manual permissions
Compatibility with tutorials	Matches every published guide	Requires path substitution
Workshop folder location	Predictable	Varies by your choice
Recommended for beginners	Yes	No

Pro tip

Even if you plan to install games to a secondary drive later, install the Steam client itself to the default location. Steam supports multiple "library folders" on different drives for games, but the client should remain on the system drive for predictability.

When to use a custom location

The two situations in which a custom install location is appropriate are when your system drive has less than 50 gigabytes of free space, or when you maintain a separate drive specifically for game-related applications. In all other cases, accept the default.

After confirming the install location, click "Install". The installer copies its files. This stage typically completes within thirty seconds.

Path constraints for custom locations

If you do select a custom install location, several constraints apply that the installer enforces or that produce subtle issues later. The constraints are:

Constraint	Reason	Failure mode if violated
Drive must be local	Steam does not support network drives	Installation fails
Drive must be NTFS or ReFS	Required for symbolic links	Some games will not install
Path must not contain non-ASCII	Compatibility with older games	Random failures in older games
Path must not contain spaces in early segments	Compatibility with some game engines	Mod tools fail to find install
Path must be writable by the user	UAC elevation does not transfer	Updates fail silently
Path must not be inside another installation	Conflicts with file management	Files corrupted across installs

A custom path that respects all six constraints behaves identically to the default path. The most common violation among new users is the non-ASCII constraint (typically Cyrillic or East Asian characters in the user's home directory) and the spaces-in-early-segments constraint (a path such as D:\My Games\Steam rather than D:\Steam).

Common mistake

Selecting a path inside the Windows user profile (C:\Users\<YourUsername>\Steam) is the most common path mistake among new users. The path appears reasonable but causes two issues: it is inside a location that some Steam tools treat as user data (causing them to attempt to back up the entire Steam install on every cloud-sync operation), and it is on the system drive (defeating the rationale for choosing a custom path in the first place).

Step 5: Complete the initial client update

When the installer finishes copying files, it offers a checkbox labeled "Run Steam". Leave this checkbox ticked and click "Finish". The Steam client launches and immediately begins downloading updates from Valve's servers. This is the longest stage of installation and can take anywhere from thirty seconds to several minutes.

The sequence diagram above shows every actor involved in the installation. Notice that the installer hands off to the Steam client as soon as the stub files are in place. Most of the actual download happens after the installer has already exited.

A progress bar in the Steam client window shows the percentage of the update complete. Do not close the window or shut down your computer during this stage. Interrupting the update can corrupt the client files and require you to reinstall.

Anatomy of the client update

The initial client update downloads several distinct pieces of software, each of which contributes to the total update size:

Component	Approximate size	Purpose
Steam runtime	80 MB	Core client runtime
Steam UI	60 MB	Client user interface
Steam library	50 MB	Game library management
Steam Friends	40 MB	Social features
Steam Workshop	30 MB	Workshop browse and subscribe
Steam Big Picture	70 MB	TV-friendly UI
Steam VR support	40 MB	VR headset integration
Steam Input	30 MB	Controller support
Steam overlays	20 MB	In-game overlay
Localisation packs	30 MB	Multi-language support
Miscellaneous	50 MB	Helper utilities, drivers
Total	~500 MB	Full Steam client

The total is approximate and varies with each release. The largest component on a typical install is the Steam runtime, which provides the foundation that the rest of the client builds on.

Best practice

Allow the initial client update to complete fully before doing anything else. Interrupting the update is the most common cause of a corrupted Steam install, and a corrupted install requires a full uninstall and reinstall to recover. The 57 Studios contributor support log records that approximately ten percent of new-modder support requests involve recovering from an interrupted initial update.

Step 6: Verify the install folder

After the update completes, the Steam login window appears. Before logging in, briefly verify that the installation created the expected folder structure. Open File Explorer and navigate to the install location.

Default folder structure

C:\Program Files (x86)\Steam\
├── Steam.exe              (the main client executable)
├── steamapps\             (game install data)
│   ├── common\            (game files)
│   ├── downloading\       (in-progress downloads)
│   ├── workshop\          (Steam Workshop subscriptions)
│   └── appmanifest_*.acf  (per-game install manifests)
├── userdata\              (per-account local data)
│   └── <SteamID>\         (one folder per account on this machine)
├── logs\                  (client log files)
├── package\               (client update packages)
├── bin\                   (additional client binaries)
└── config\                (client configuration files)

The ASCII diagram above shows the folders Steam creates inside the install location. The steamapps folder is the most important for mod development because Unturned and its mods will live inside steamapps\common\Unturned after installation.

Did you know?

The "(x86)" in Program Files (x86) indicates a 32-bit application. Although Steam runs as a 32-bit process for compatibility reasons, the games it launches can be either 32-bit or 64-bit. Unturned itself is a 64-bit game.

Important files for mod developers

Several files inside the Steam install folder are particularly relevant for Unturned mod development:

File / Folder	Purpose	Modder relevance
Steam.exe	Main Steam launcher	Launch Unturned through this
steamapps\common\Unturned\	Unturned game files	Mod content extraction target
steamapps\workshop\content\304930\	Workshop subscriptions for Unturned	Reverse-engineering existing mods
steamapps\workshop\downloads\304930\	In-progress Workshop downloads	Diagnostic during testing
steamapps\sourcemods\	Source engine mods	Not relevant to Unturned
userdata\<SteamID>\761\	Workshop publisher data	Workshop draft uploads
logs\	Client diagnostic logs	Diagnostic during Workshop publish
config\config.vdf	Client configuration	Library folder list

The path steamapps\workshop\content\304930\ is the location where any Workshop mod you subscribe to is downloaded. The 304930 is Unturned's Steam App ID and is constant. Each subfolder inside 304930 is named with the Workshop item's numeric ID and contains the mod's content files.

Disk space requirements

The Steam client itself occupies approximately 400 megabytes after installation. However, games downloaded through Steam are stored within steamapps\common, so your effective space requirements grow with each game you install. Unturned installs to about 3 gigabytes, and the Unturned modding workflow involves additional Unity Editor downloads that can consume 10 or more gigabytes.

Best practice

Leave at least 50 gigabytes free on your install drive before installing Steam. This headroom accommodates Steam itself, Unturned, the Unity Editor required for modding, and reasonable workspace for your in-progress mod projects.

Disk space allocation for mod development

A typical Unturned mod-development workstation consumes the following disk space:

Component	Approximate size
Steam client	500 MB
Unturned base game	3 GB
Unturned modding template (Unity project)	4 GB
Unity Editor (relevant version)	8 GB
Visual Studio 2022 Community	12 GB
Blender	350 MB
Image editor (Photoshop or GIMP)	4 GB
Workshop subscriptions for reference (10-20 mods)	2 GB
Personal mod project source	1-5 GB
Backups of personal mod projects	5-15 GB
Total	45-60 GB

The 50-gigabyte recommendation above is the minimum that supports a comfortable development workflow. Contributors who maintain multiple in-progress mods, multiple Unity Editor versions, or extensive Workshop subscriptions for reference will exceed this comfortably and should plan for 100 GB or more.

Recovering from a failed installation

Several failure modes are possible during installation. Each has a recommended recovery procedure.

Installer fails to launch

The installer does not appear after double-clicking SteamSetup.exe. The principal causes:

Cause	Symptom	Resolution
Truncated download	Nothing happens on double-click	Re-download from official URL
Antivirus quarantine	File silently disappears	Restore from quarantine, allowlist
Missing admin privileges	UAC prompt blocked	Run as administrator
32-bit incompatibility	Error message about architecture	Update Windows
Already running installer	Lock file present	Reboot or kill stuck process

The resolution is the same for each cause: identify which applies, apply the specific resolution, and re-attempt the launch.

UAC prompt refused

If you accidentally click "No" on the UAC prompt, the installer exits without doing anything. The installer can be re-launched by double-clicking the file again. No cleanup is required from the refused attempt.

Installer hangs partway through copying

The installer's "copying files" stage typically completes within thirty seconds. If the stage takes longer than several minutes, the installer may be hung on a specific file. The remediation is:

1. Wait an additional two minutes to confirm the installer is genuinely hung.
2. Open Task Manager and observe the installer's CPU and disk activity.
3. If the installer is consuming no CPU or disk, it is genuinely hung.
4. End the installer process through Task Manager.
5. Delete the partial install folder.
6. Re-launch the installer.

The cause of installer hangs is most often antivirus interference, which can introduce significant per-file scanning delays. Adding the install location to the antivirus allowlist before re-attempting the install resolves this.

Client update fails to complete

The most common failure mode is interrupted client update due to network instability. The Steam client typically recovers automatically by resuming the download where it left off. If the client does not recover automatically:

1. Close the Steam client.
2. Verify your internet connection is working.
3. Re-launch Steam.exe from the install folder.
4. The client resumes the update.

If the resume itself fails, the update may have corrupted partial files. The remediation is to delete the install folder entirely and run the installer again.

Critical warning

Do not edit, move, or delete individual files inside the Steam install folder while the client is running. Steam tracks every file by hash, and unexpected file modifications can produce confusing error messages or trigger the client to redownload large portions of itself. The supported way to modify Steam's installation state is through the client's UI, not through direct file manipulation.

Frequently asked questions

Why does Steam install to Program Files (x86) instead of Program Files?

Steam runs as a 32-bit process for compatibility reasons. Windows places 32-bit applications under Program Files (x86) by convention. The 32-bit architecture has been a deliberate choice by Valve since the platform's early days and persists because of the enormous compatibility surface area of older games that depend on 32-bit Steam infrastructure.

Can I move Steam to another drive after installation?

Yes, but the procedure involves backing up your existing library, uninstalling Steam, reinstalling to the new location, and restoring the library. It is much simpler to choose the correct location during initial installation. For the case where moving is unavoidable, Steam provides a "Move Install Folder" feature in the client settings that handles much of the work automatically; the feature is limited to moving between Steam library folders rather than relocating the Steam client itself.

What if the initial client update fails?

Close Steam, verify your internet connection, and relaunch Steam.exe from the install folder. The client will resume the update where it left off. If the resume fails repeatedly, delete the install folder and re-run the installer.

Does Steam install any background services?

Steam adds a "Steam Client Service" that runs only while the Steam client is open. It does not run permanently in the background. Steam also registers a few helper processes (steamwebhelper.exe, steamservice.exe) that run during Steam sessions and exit when the client closes.

Can I install Steam on a network drive or USB drive?

Steam supports installation only to local drives. Network and USB drives can be used as additional library folders for games but not as the install location for the Steam client itself. The reason is that Steam relies on Windows file-system semantics that are not available over network shares.

Can I install multiple copies of Steam on the same machine?

Officially, no — Steam is designed as a single-install application. Several community workarounds exist for running multiple Steam clients on the same machine using portable installations or container techniques, but these workarounds are not supported and frequently break on Steam client updates.

What happens if I cancel the installer partway through?

If you cancel before the installer begins copying files, nothing has been written to disk and no cleanup is required. If you cancel during the copy stage, the installer typically removes the partial copy automatically. If the automatic cleanup fails, manually delete the install folder.

Does the installer require administrator privileges?

Yes. The installer must write to Program Files (x86) (or wherever you direct it), register file associations, register the steam:// protocol handler, and create entries in the Start Menu. All of these operations require administrator privileges on a standard Windows configuration.

Can I install Steam without an internet connection?

No. The installer is a bootstrapper and requires an internet connection to download the full Steam client during installation. Offline installation of Steam is not directly supported.

Will Steam install update automatically after the initial install?

Yes. Once installed, the Steam client checks for updates each time it launches and applies them automatically. Most updates are small and complete within seconds. Major updates (typically once or twice per year) can be larger and may take a few minutes.

Where does Steam place its log files?

Steam writes logs to the logs\ subfolder of the install location. The logs are useful when diagnosing installation issues or Workshop publishing failures. The principal log files are bootstrap_log.txt (logs the launch sequence), connection_log.txt (logs network activity), and content_log.txt (logs game and Workshop content downloads).

How do I know if the installation completed successfully?

The most reliable indicator is that the Steam login window appears at the end of the installation. If the login window appears, the installer copied its files correctly, the client launched, and the client update completed. If you see the login window, the installation is complete and the next step is to log in.

Best practices

• Always accept the default install location unless you have a specific reason to change it
• Wait for the initial client update to complete before doing anything else
• Verify the UAC prompt shows "Valve Corp." as the publisher before clicking Yes
• Keep at least 50 gigabytes of free space on the install drive
• Note the install path for future reference when troubleshooting
• Avoid running the installer from a network location; copy it locally first
• Disable aggressive antivirus heuristics during installation, then re-enable after
• Do not edit, move, or delete individual Steam files while the client is running
• Allow the initial client update to fully complete on a stable network
• Confirm the Steam login window appears as the end-of-installation signal

Appendix A: Windows registry modifications made by the installer

The Steam installer makes several modifications to the Windows registry. The modifications are required for Windows to recognise Steam as an installed application and to allow steam:// URLs to launch the client. The principal modifications are documented here for reference.

Steam application registration

The installer registers Steam under several registry keys:

Registry key	Purpose
HKLM:\Software\Valve\Steam	Steam's installation metadata
HKLM:\Software\Wow6432Node\Valve\Steam	32-bit view of the above
HKCU:\Software\Valve\Steam	Per-user Steam settings
HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\Steam	Uninstall entry
HKLM:\Software\Classes\steam	steam:// protocol handler

The steam:// protocol handler registration is what enables Steam links on the web (such as "Add to Library" buttons or Workshop subscribe links) to launch the local Steam client. Without this registration, clicking a steam:// link in a browser does nothing.

File association registration

The installer registers file associations for two file types:

Extension	Purpose	Default action
.acf	Steam game install manifest	Opens in Steam
.vdf	Valve Data File (configuration)	Opens in Steam

The associations are primarily useful for Steam itself; users rarely interact with these files directly. The associations can be confusing if you accidentally double-click an .acf file in File Explorer, in which case Steam may launch when you did not intend it to.

Did you know?

The .acf files in steamapps\ are Steam's per-game install manifests. They document the install state, version, and update status of each installed game. If you ever need to migrate Steam between drives, copying the .acf files alongside the game folders preserves Steam's awareness of the install.

Appendix B: Per-user versus all-users installation

The Steam installer installs Steam in a "per-machine" configuration: the install is available to every Windows user account on the machine, not only the user account that ran the installer. This has several implications for multi-user households or shared workstations.

Implications of per-machine install

Aspect	Behaviour
Installation visible to all users	Yes
Game library shared by default	No (per-account library)
User data isolated per user	Yes (each user has separate userdata\<SteamID>)
Steam Friends list per user	Yes
Workshop subscriptions per user	Yes
Settings per user	Yes

A multi-user Windows machine can therefore have a single Steam installation but multiple independent Steam accounts, each with its own library, friends, subscriptions, and settings. The per-account data lives under the userdata\<SteamID>\ folder structure inside the install location.

Steam Family Sharing

If multiple users on the same machine want to share a single game library, Steam Family Sharing provides the supported mechanism. Family Sharing is configured per-account from within the Steam client. It allows a designated set of accounts to access another account's library, subject to certain constraints (one user playing at a time, no shared multiplayer simultaneously). Family Sharing is documented in detail in the dedicated Steam Family Sharing article elsewhere in this knowledge base.

Pro tip

For Unturned mod development specifically, Family Sharing is not the recommended pattern. Each developer who actively builds and tests mods benefits from their own Steam account with the mod-development workflow configured against it. Shared accounts complicate Workshop publishing, version control, and testing in ways that exceed the convenience of shared game access.

Appendix C: Uninstall and reinstall procedures

The Steam client can be uninstalled and reinstalled cleanly through the Windows Settings application. The procedure for a clean reinstall is sometimes necessary when troubleshooting a fundamentally broken Steam installation.

Standard uninstall

The standard uninstall procedure is:

1. Open Windows Settings.
2. Navigate to Apps, then Installed apps.
3. Locate Steam in the list.
4. Click the three-dot menu and choose "Uninstall".
5. Confirm the uninstall.
6. The uninstaller removes Steam and its files, except for the steamapps\ folder by default.

The steamapps\ folder contains installed games and Workshop content. Preserving it during uninstall means that a subsequent reinstall to the same location will recognise the existing games without re-downloading them.

Clean reinstall

A clean reinstall (which discards game files as well as client files) is occasionally necessary when the install itself is corrupted. The procedure is:

1. Back up any irreplaceable data from userdata\<SteamID>\ (custom keybindings, screenshots, etc.).
2. Run the standard uninstall as documented above.
3. Manually delete the entire Steam install folder (including steamapps\).
4. Re-download SteamSetup.exe from the official source.
5. Run the installer and complete the installation flow described in this article.
6. Log in with your Steam account.
7. Reinstall the games and Workshop subscriptions you need.

The clean reinstall takes substantially more time than the standard reinstall because all games must be re-downloaded. It is the recommended approach when the standard uninstall and reinstall do not resolve the underlying issue.

Manual cleanup of stuck installs

In rare cases, the standard uninstall fails to fully remove Steam (typically due to a stuck process or a permissions issue). Manual cleanup involves:

Item to remove	Path	Notes
Install folder	C:\Program Files (x86)\Steam\	Contains client and games
Per-user data	%LOCALAPPDATA%\Steam\	Per-user cache
Registry keys	Documented in Appendix A	Use regedit
Start menu shortcuts	%PROGRAMDATA%\Microsoft\Windows\Start Menu\Programs\Steam\	Folder + contents
Desktop shortcut	%PUBLIC%\Desktop\Steam.lnk	If present

Manual registry editing is rarely necessary. The standard uninstall handles registry cleanup automatically.

Common mistake

Editing the Windows registry without a backup is a frequent source of system instability. If you do need to edit the registry to clean up a stuck Steam install, export the relevant subtrees to a .reg file first. The export provides a one-click restore path if the manual edits cause unintended problems.

Appendix D: Post-install verification checklist

After completing the installation, the following checklist confirms that the install is healthy and that the Steam client is ready for first use.

#	Verification	Expected outcome
1	Steam login window appears	Yes
2	Steam.exe exists in install folder	Yes
3	steamapps\ folder created	Yes
4	userdata\ folder created	Yes
5	Start menu entry for Steam present	Yes
6	Desktop shortcut for Steam present	Yes (unless deselected during install)
7	steam:// protocol handler registered	Yes
8	Steam appears in Apps list in Windows Settings	Yes
9	Client version visible in Steam login window	Yes (recent build)
10	Login window is interactive	Yes

If any of the verifications fail, the install has not completed successfully. The remediation is typically a clean reinstall as documented in Appendix C.

Appendix E: Choosing a Steam install drive for mod development

For Unturned mod development specifically, the choice of install drive affects daily workflow performance in subtle ways. The following recommendations come from the 57 Studios contributor cohort and are validated against several years of mod-development experience.

Recommended drive characteristics

Characteristic	Recommendation	Rationale
Drive type	NVMe SSD preferred, SATA SSD acceptable	Faster Workshop subscription downloads and Unity import
Drive capacity	At least 250 GB	Headroom for game, mods, Unity Editor, projects
Free space at install	At least 50 GB	Steam install + initial game + working room
File system	NTFS	Standard Windows file system
Drive role	Not the OS drive if possible	Reduces contention with Windows updates

The most impactful single recommendation is to use an SSD rather than a spinning hard disk. Unity Editor's first-import behaviour is highly disk-bound and can take significantly longer on a hard disk than on an SSD. Workshop subscription downloads and game launches also benefit from SSD storage.

Drive layout for serious mod developers

Several serious 57 Studios contributors maintain a multi-drive layout that separates concerns explicitly:

C:\ (OS drive, NVMe SSD, 500 GB)
  - Windows
  - Program Files (x86)\Steam (Steam client only)

D:\ (Games drive, NVMe SSD, 1 TB)
  - SteamLibrary (game files, Workshop subscriptions)
  - Unity Editor versions
  - Visual Studio installation

E:\ (Projects drive, NVMe SSD or SATA SSD, 1 TB)
  - Personal mod projects
  - Personal mod source backups
  - Version-control working copies

F:\ (Archive drive, spinning HDD, 4 TB)
  - Personal installers archive
  - Long-term mod release archive
  - Workshop publication artefacts

The layout is more elaborate than most new mod developers need at the outset, but it scales gracefully as the developer's portfolio grows. The principal benefit is the reduced risk of a single drive failure destroying both the working copies of in-progress mods and the historical record of released mods.

Did you know?

The 57 Studios contributor cohort maintains a documented preference for NVMe SSDs over SATA SSDs for the Steam library drive specifically. The preference is driven by Unity Editor's import behaviour, which can take several minutes on a spinning hard disk, several seconds on a SATA SSD, and well under a second on a current NVMe SSD. The compounding effect across hundreds of import operations per development cycle is significant.

Appendix F: Performance tuning for the Steam client

Once the installation is complete, several configuration options inside the Steam client itself affect daily mod-development performance. The principal options to review during the first launch are:

Download settings

Steam's download manager has settings that affect both the time to download mods and the load on your network. The principal settings are accessed through Settings, Downloads:

Setting	Recommendation for mod development	Rationale
Download region	Closest geographic region	Minimum latency
Limit bandwidth	Unlimited (or near-link-speed)	Workshop downloads benefit from full bandwidth
Throttle while streaming	Off	Streaming and Workshop downloads rarely conflict
Allow downloads during gameplay	Yes	Workshop subscription updates during play
Auto-update games	On	Keeps Unturned current automatically
Schedule auto-updates	Any	Mid-day or overnight depending on usage

Library settings

The Steam library settings affect how the library displays games. The principal recommendations:

Setting	Recommendation for mod development	Rationale
Hide unowned games in store	Per preference	Reduces clutter
Hide tools and demos	Off	Modding tools live in the tools category
Sort by	Recently played or alphabetical	Daily-use ordering
Display library compatibility	On	Workshop compatibility warnings
Display install size in library	On	Disk management awareness

Interface settings

The interface settings affect the visual and behavioural feel of the client. The principal recommendations:

Setting	Recommendation for mod development	Rationale
Run Steam at startup	Per preference	Trade-off between convenience and startup time
Big picture mode	Off	Desktop developer workflow
Notification sounds	Per preference	Workshop comment notifications
In-game overlay	On	Necessary for some Workshop test workflows
Beta participation	Off (initially)	Stable client for development

The recommendation for Beta participation is to keep it off initially. The Steam Beta channel receives client updates earlier than the stable channel and occasionally introduces bugs that affect Workshop publishing. Once you have a stable mod-development workflow, you may choose to opt into the Beta channel for early access to Workshop-related improvements.

Pro tip

Visit Settings within the first launch session and walk through every settings page once. The walk-through takes about ten minutes and surfaces both the settings documented above and many others that may affect your specific workflow. The settings are well-documented inside the client itself; no external reference is required.

Appendix G: First-launch behaviour and the client update lifecycle

The Steam client launches into a brief first-launch behaviour that differs from subsequent launches. Understanding this behaviour helps you interpret what you see during the initial setup.

First-launch sequence

1. Client window appears and displays the login screen.
2. Background process: client verifies its own file integrity against the manifest.
3. Background process: client downloads any updates that have been released since the bootstrapper finished.
4. User logs in.
5. Background process: client downloads per-account data (friends list, library, Workshop subscriptions metadata).
6. Background process: client initialises the in-game overlay subsystem.
7. Background process: client registers itself with the Steam Friends network.
8. Client transitions to the main library view.

The transitions between these steps are largely invisible to the user. The first-launch sequence typically completes within one to two minutes after login.

Ongoing update lifecycle

After the first launch, the client continues to update itself on a regular cadence:

Update type	Frequency	Size
Minor client update	Weekly	5-30 MB
Major client update	2-4 times per year	100-300 MB
Hotfix update	Occasional	1-5 MB
Beta update (if opted in)	Multiple per week	Variable

Updates are applied automatically on client launch. The client checks for updates at startup and applies them before displaying the login window. If an update is in progress when you close the client, the update is paused and resumed at the next launch.

Best practice

Restart the Steam client at least once per week to ensure recent updates are applied. The 57 Studios contributor cohort has observed several incidents in which a long-running Steam client (left open across weeks) missed important Workshop-related fixes and produced confusing failure modes during Workshop publishing. A weekly restart is a low-cost preventive measure.

Identifying the current client version

The currently-installed client version is visible from inside the Steam client at Steam, About Steam. The version number takes the form of a build identifier (such as "Built: Jan 15 2025") and a numeric build number. The version is useful when corresponding with Steam Support, when filing bug reports against Workshop publishing tooling, and when verifying that a recent update has been applied successfully. If the displayed build date is more than two weeks old, the client has missed at least one update and a manual restart is warranted to bring it current.

Cross-references

• How to Download Steam — the prior article in the sequence; covers retrieving SteamSetup.exe
• How to Log into Steam — the next article in the sequence; covers authenticating with the installed client
• How to Find a Game in Your Library — the article after that; covers locating Unturned in the library
• How to Create a Steam Account — the article that started the sequence; covers creating the account used for login

Next steps

With Steam installed and the client running, continue to How to Log into Steam to authenticate using the account you created earlier.

The installation you have just completed places the Steam client onto your machine, registers it with Windows, and downloads the latest version of the client from Valve's content delivery network. The next step is to authenticate the client with the Steam account you created in the first article of this series. From there, the path to Unturned and the mod-development workflow proceeds without further installation steps.

Document history

Version	Date	Author	Notes
1.0	2024-01-26	57 Studios	Initial publication. Foundation install flow and folder structure documentation.
1.1	2024-03-18	57 Studios	Added registry modifications appendix and per-user versus all-users discussion.
1.2	2024-06-04	57 Studios	Added uninstall and reinstall procedures and post-install verification checklist.
2.0	2024-09-22	57 Studios	Major revision aligning the article with the structural standard adopted across the knowledge base. Added expanded background, additional callouts, sequence diagrams, and the drive-selection appendix.
2.1	2025-01-29	57 Studios	Refreshed the client-update component table and the drive-layout recommendations.