Quick answer: Steam error codes cover six main areas — connection errors (error 118, error 138 — check steamstat.us and restart router), download errors (disk write error — run Steam as administrator; error 16 — delete and re-download), cloud sync errors (conflict dialog — choose carefully between local and cloud save), payment errors (declined card — update payment method in Steam account), update errors (Steam client update failed — clear download cache), and VAC errors (authentication error — restart as administrator and verify files; VAC ban — permanent). Most Steam errors are fixed by running Steam as administrator and checking server status.
The Disk Write Error That Appeared Every Time I Tried to Install a New Game
For three months, every new game I tried to install on Steam failed with a disk write error partway through the download. The error appeared at different points — sometimes at 20%, sometimes at 80% — but always the same message: “An error occurred while installing [game name] (disk write error).” I tried changing the download region, clearing the download cache, and reinstalling Steam. Nothing worked. A post on the Steam community forums for one of the affected games mentioned checking the drive health with CrystalDiskInfo. I downloaded it, ran it, and found the installation drive had 47 reallocated sectors — a sign of a failing drive. I moved the Steam library to a different drive, and every game installed without errors. The failing drive failed completely two weeks later.
That experience taught me the most important thing about Steam error codes: a disk write error that persists across multiple games and multiple reinstallation attempts is not a Steam problem — it is a drive health problem. Steam’s error messages are accurate: when Steam says it cannot write to the disk, it usually means exactly that. Checking drive health with CrystalDiskInfo is the diagnostic step that most Steam troubleshooting guides skip, and it is the one that matters most for persistent disk write errors.
How Steam Error Codes Are Generated
Steam error codes are generated by three different systems within the Steam client. The Steam network layer generates connection error codes (error 118, error 138, error 130) when the Steam client cannot establish or maintain a connection to Valve’s servers. The Steam download and file management layer generates disk write errors, disk read errors, and error 16 (corrupt download) when the client cannot write game files to the installation drive or when a downloaded file fails its integrity check. The Steam platform services layer generates cloud sync errors, VAC errors, payment errors, and account errors when the client cannot communicate with Steam’s backend services for save synchronization, anti-cheat verification, or transaction processing.
Steam also displays plain-language error messages for many faults — “Steam must be running to play this game,” “This game is currently unavailable,” “No connection to Steam servers” — alongside numbered error codes. Both formats point to the same underlying systems. The numbered error codes (118, 138, 16) are more specific and easier to look up in Steam’s support documentation at help.steampowered.com.
The 5 Steam Error Code Categories
1. Connection Errors — Error 118, Error 138, and Server Unavailable
Steam connection errors indicate that the Steam client cannot reach Valve’s servers. Common connection error codes: error 118 (cannot connect to Steam network — the most common Steam connection error), error 138 (connection timed out — the connection was established but timed out before completing), error 130 (failed to load webpage — Steam’s built-in browser cannot reach the Steam store), error 137 (failed to load webpage — similar to 130, often a DNS issue). These errors appear when Steam launches, when accessing the Steam store, or when attempting to download games.
The first step for any Steam connection error is checking Steam’s server status at store.steampowered.com/stats (shows current player counts — a sudden drop indicates a server issue) or steamstat.us (shows historical uptime and current status by region). If Steam’s servers are operational, the issue is local: restart Steam completely (right-click taskbar icon → Exit, then relaunch), restart the router and modem (60-second unplug), flush DNS (Command Prompt as administrator: ipconfig /flushdns), and check that Steam.exe and SteamService.exe are allowed through Windows Firewall (Windows Security → Firewall and network protection → Allow an app through firewall).
2. Download and Installation Errors — Disk Write Error and Error 16
Download and installation errors occur when Steam cannot write game files to the installation drive or when a downloaded file fails its integrity check. The disk write error is the most common download error — it appears when Steam lacks write permission to the installation folder, when the drive has insufficient free space, when the drive’s file system has errors, or when the drive is failing. Error 16 (download corrupt) appears when a downloaded file’s checksum does not match the expected value — caused by a network interruption, a failing drive, or RAM errors.
For disk write errors: run Steam as administrator (right-click Steam → Run as administrator) — this resolves the majority of permission-related write errors. Also add Steam’s installation folder to antivirus exclusions (Windows Security → Virus and threat protection → Manage settings → Exclusions → Add a folder). Check drive health with CrystalDiskInfo (download from crystalmark.info) — a drive showing yellow or red status, reallocated sectors, or pending sectors is failing and should be replaced before data loss occurs. For error 16: delete the partial download (Steam Library → right-click game → Manage → Delete local content) and re-download from scratch.
3. Cloud Sync Errors — Save Conflict and Synchronization Failure
Steam Cloud sync errors occur when Steam cannot synchronize save data between the local PC and Steam Cloud storage. Common cloud sync scenarios: the sync conflict dialog (“Steam Cloud and local files disagree”) appears when the local save file is newer than the cloud save (or vice versa) — this happens when playing on multiple PCs or when Steam was closed without syncing. The “Unable to sync” error appears when Steam cannot reach the cloud sync servers — check Steam server status. The “Steam Cloud is temporarily unavailable” message appears during Steam maintenance.
For the sync conflict dialog: choose carefully. “Upload to Steam Cloud” keeps the local save and overwrites the cloud version. “Download from Steam Cloud” keeps the cloud save and overwrites the local version. If unsure which save is more recent, locate the local save file (Steam Library → right-click game → Properties → Local Files → Browse — save files are typically in the game’s installation folder or in Documents/My Games) and check the file modification date before choosing. For persistent cloud sync failures: disable and re-enable Steam Cloud for the game (Steam Library → right-click game → Properties → General → Steam Cloud checkbox).
4. Payment and Account Errors — Declined Transactions and Purchase Failures
Steam payment errors occur when a purchase cannot be completed. Common payment error messages: “Your purchase has failed” (payment method declined or Steam’s fraud detection flagged the transaction), “There was an error processing your credit card” (card declined or expired), “You have made too many purchases in a short period of time” (Steam’s purchase rate limit — wait 24 hours), “This item is not available in your region” (regional restriction on the game or DLC). Steam account errors: “Your account does not meet the requirements to use this feature” (Steam account not meeting the minimum spend threshold for certain features — Steam requires a minimum purchase history for some account features).
For payment failures: verify the payment method in Steam account settings (Steam → Account Details → Store and Purchase History → Manage payment methods). Try a different payment method — Steam Wallet funds (purchased via Steam gift cards) bypass card processing entirely and are the most reliable payment method for Steam purchases. For “too many purchases” rate limit errors, wait 24 hours before attempting another purchase. For regional restriction errors, the game is not available for purchase in the account’s registered country — this cannot be bypassed through VPN without violating Steam’s Terms of Service.
5. VAC and Game Launch Errors — Anti-Cheat Conflicts and Launch Failures
VAC (Valve Anti-Cheat) errors fall into two distinct categories. VAC bans are permanent, account-specific bans applied when the VAC system detects cheat software — a VAC ban cannot be removed and affects only VAC-secured servers (the account can still play non-VAC games). VAC authentication errors (“VAC was unable to verify your game session”) are not bans — they indicate a system conflict between VAC and another application running on the PC. Common causes of VAC authentication errors: antivirus software interfering with VAC’s memory scanning, overlay applications (Discord, GeForce Experience, MSI Afterburner) conflicting with VAC, corrupted game files, and drive errors.
For VAC authentication errors (not bans): restart Steam as administrator, verify game files (Steam Library → right-click game → Properties → Local Files → Verify Integrity of Game Files), disable overlay applications temporarily (Discord: Settings → Game Overlay → disable; GeForce Experience: Settings → General → disable In-Game Overlay), and run chkdsk on the drive containing the game. For game launch errors (“Steam must be running to play this game” — even when Steam is open): exit Steam completely (right-click taskbar icon → Exit), then relaunch Steam as administrator before launching the game.
How to Fix Steam Error Codes: Step-by-Step
Step 1: Check Steam Server Status and Restart Steam
Before attempting any local fix, check Steam’s server status at store.steampowered.com/stats or steamstat.us. If Steam’s servers are degraded or undergoing maintenance, wait for the issue to resolve. If servers are operational, restart Steam completely: right-click the Steam icon in the system tray → Exit (not just close the window — Exit terminates all Steam processes). Wait 10 seconds, then relaunch Steam. If Steam is not in the system tray, open Task Manager (Ctrl+Shift+Esc) → find all Steam processes → End task on each one before relaunching. This resolves the majority of temporary connection and launch errors.
Step 2: Run Steam as Administrator
Running Steam as administrator resolves the majority of disk write errors, permission errors, and VAC authentication errors. Right-click the Steam shortcut on the desktop or in the Start menu → Run as administrator. To make this permanent: right-click the Steam shortcut → Properties → Compatibility → check “Run this program as an administrator” → Apply. Also right-click the Steam executable (typically C:\Program Files (x86)\Steam\Steam.exe) → Properties → Compatibility → check “Run this program as an administrator.” After enabling administrator mode, test whether the error recurs.
Step 3: Clear the Steam Download Cache
The Steam download cache stores temporary data from downloads and updates. A corrupted download cache causes connection errors, download failures, and Steam client update failures. Clear the cache: Steam → Settings → Downloads → Clear Download Cache → OK. Steam will restart and ask you to log in again — this is normal. After clearing the cache, test whether the error recurs. Also try changing the download region: Steam → Settings → Downloads → Download Region → select a different region (choose a region geographically close to you). A different download region uses different Valve CDN servers and can resolve download errors caused by a specific CDN server issue.
Step 4: Verify Game Files and Check Drive Health
For game-specific errors (launch failures, in-game crashes, corrupted game data): verify the game’s files through Steam. Steam Library → right-click the game → Properties → Local Files → Verify Integrity of Game Files. Steam will check each game file against its expected checksum and re-download any files that fail the check. For persistent disk write errors across multiple games: download CrystalDiskInfo from crystalmark.info and check the health status of the drive containing the Steam library. A drive showing yellow (caution) or red (bad) status, or showing non-zero values for “Reallocated Sectors Count” or “Current Pending Sector Count,” is failing and should be replaced. Move the Steam library to a healthy drive: Steam → Settings → Storage → Add Drive.
Step 5: Fix Antivirus, Firewall, and Network Settings
For persistent connection errors and download failures after confirming servers are operational: add Steam’s installation folder (typically C:\Program Files (x86)\Steam) to antivirus exclusions (Windows Security → Virus and threat protection → Manage settings → Exclusions → Add a folder). Check Windows Firewall: Windows Security → Firewall and network protection → Allow an app through firewall → ensure Steam.exe and SteamService.exe are checked for both Private and Public networks. Flush DNS: Command Prompt as administrator → ipconfig /flushdns. Set DNS to Google (8.8.8.8 / 8.8.4.4) or Cloudflare (1.1.1.1 / 1.0.0.1) in network adapter settings if DNS resolution errors persist.
Frequently Asked Questions About Steam Error Codes
What are the most common Steam error codes?
The most common Steam error codes are error 118 (cannot connect to Steam network), error 138 (connection timed out), disk write error (cannot write game files — run as administrator and check drive health), error 16 (download corrupt — delete and re-download), cloud sync error (save conflict — choose carefully between local and cloud save), and VAC authentication error (system conflict — restart as administrator and verify files).
How do I fix Steam error 118?
Check Steam server status at steamstat.us. If servers are operational: restart Steam completely (right-click taskbar icon → Exit, then relaunch), restart the router and modem (60-second unplug), flush DNS (Command Prompt as administrator: ipconfig /flushdns), and ensure Steam.exe is allowed through Windows Firewall. Try Steam in offline mode (Steam → Go Offline) — if offline mode works, the issue is server-side or network-side.
How do I fix Steam disk write error?
Run Steam as administrator (right-click → Run as administrator) — this resolves most permission-related write errors. Add Steam’s folder to antivirus exclusions. Run chkdsk on the installation drive (Command Prompt as administrator: chkdsk C: /f /r). Check drive health with CrystalDiskInfo — a failing drive must be replaced. Move the Steam library to a healthy drive if the current drive is failing.
How do I fix Steam cloud sync errors?
Check Steam server status first. For the sync conflict dialog: check the local save file modification date before choosing between “Upload to Steam Cloud” and “Download from Steam Cloud.” For persistent sync failures: disable and re-enable Steam Cloud for the game (Steam Library → right-click game → Properties → General → Steam Cloud checkbox). Ensure the PC has a stable internet connection when closing games — Steam syncs saves on game exit.
What is the difference between a VAC ban and a VAC authentication error?
A VAC ban is permanent and account-specific — the VAC system detected cheat software. It cannot be removed. A VAC authentication error (“VAC was unable to verify your game session”) is not a ban — it is a system conflict between VAC and another application. Fix: restart Steam as administrator, verify game files, disable overlay applications (Discord, GeForce Experience), and run chkdsk on the game drive.
Steam Error Code Fix Complexity and Cost
The table below summarizes common Steam error codes, their typical cause, and the fix complexity and cost. Most Steam errors are resolved at zero cost — hardware costs apply only when the installation drive is failing.
| Error Code / Issue | Common Cause | DIY Fix Cost (USD) | Hardware / Service Cost (USD) |
|---|---|---|---|
| Error 118 — Cannot connect | Steam server outage or local network issue | $0 (restart Steam / flush DNS) | $0 |
| Error 138 — Connection timeout | Network timeout or firewall blocking Steam | $0 (firewall exception / router restart) | $0 |
| Disk write error (permissions) | Write permission denied — not running as admin | $0 (run Steam as administrator) | $0 |
| Disk write error (drive failing) | Failing storage drive with bad sectors | $0 (move Steam library to healthy drive) | $50 – $150 (replacement SSD) |
| Error 16 — Download corrupt | Network interruption or drive error | $0 (delete and re-download) | $0 |
| Cloud sync error / conflict | Server maintenance or local file conflict | $0 (resolve conflict dialog / re-enable cloud) | $0 |
| VAC authentication error | System conflict with overlay or antivirus | $0 (run as admin / disable overlays / verify files) | $0 |
| Payment failed / purchase error | Card declined, rate limit, or regional restriction | $0 (update payment method / use Steam Wallet) | $0 |
Note: Most Steam error codes are resolved at zero cost through software fixes — running as administrator, clearing the download cache, verifying game files, and adjusting antivirus and firewall settings. The only hardware cost scenario is a failing storage drive causing persistent disk write errors — CrystalDiskInfo identifies this condition before the drive fails completely. Replace a failing drive promptly to avoid data loss.
Conclusion: Steam Error Codes Are Specific — Read Them Carefully
The disk write error that appeared on every game installation for three months was not a Steam problem, not a permissions problem, and not a network problem. It was a failing drive — and CrystalDiskInfo confirmed it in 30 seconds. That outcome illustrates the most important principle for diagnosing Steam error codes: Steam’s error messages are accurate. When Steam says it cannot write to the disk, check the disk. When Steam says it cannot connect to the network, check the network. When Steam says a file is corrupt, verify the files. The error message is the diagnosis — the fix follows directly from understanding what the message means.
Steam error codes divide into clear categories with specific fix paths. Connection errors (118, 138) → check server status, restart Steam, flush DNS, check firewall. Download errors (disk write, error 16) → run as administrator, add to antivirus exclusions, check drive health with CrystalDiskInfo. Cloud sync errors → check server status, resolve conflict dialog carefully, re-enable Steam Cloud. Payment errors → update payment method, use Steam Wallet, wait out rate limits. VAC authentication errors → restart as administrator, verify files, disable overlays. In each category, the fix is specific and documented at help.steampowered.com.
The most effective preventive measures for Steam errors are: run Steam as administrator by default (prevents the majority of disk write and permission errors), add Steam’s installation folder to antivirus exclusions during initial setup (prevents quarantine-related launch failures), check drive health with CrystalDiskInfo annually (catches failing drives before they cause data loss), and keep at least 15% of the installation drive free (prevents disk space-related download failures). These four habits prevent the majority of Steam error codes that users encounter.
Sources
- Valve Steam Support — Steam Error Code Reference and Troubleshooting Guides. Available at: help.steampowered.com
- Steam Store — Current Player Count and Server Status Indicator. Available at: store.steampowered.com/stats
- Valve — Steam Subscriber Agreement and VAC Policy Documentation. Available at: store.steampowered.com/subscriber_agreement
- CrystalMark — CrystalDiskInfo Hard Drive Health Monitoring Tool. Available at: crystalmark.info/en/software/crystaldiskinfo
- Microsoft — Windows Firewall Configuration and Application Exception Management. Available at: support.microsoft.com/en-us/windows/windows-firewall
