Fix Steam Error 130: Update Stuck or Fails

Quick answer

Clear your Steam download cache, then restart Steam and try again. If that fails, add Steam to your firewall's allowed apps.

Why you're seeing this error

Steam Error 130 usually shows up when you're trying to download a game or update and the message says something like "Content servers unreachable" or "Connection timed out." It's not a corrupted file problem. That's the first thing people assume, and it's wrong. The real issue is that your Steam client can't talk to the download servers properly. This can happen when your network connection hiccups mid-download, when your firewall or antivirus is blocking Steam's traffic, or when a stale cache file gets in the way. I've seen it most often after a Windows update resets your network settings or when you switch from Wi-Fi to a wired connection while a download is running. The good news? You don't need to reinstall Steam or your game. You just need to clear out the junk and let Steam reconnect.

Fix Step-by-Step

Work through these in order. Start with the first one—it works for most people.

Step 1: Clear your download cache

Open Steam and click Steam in the top-left corner.
Select Settings (or Preferences on a Mac).
Click Downloads in the left sidebar.
Click the Clear Download Cache button.
Click OK on the confirmation popup. Steam will restart and ask you to log in again—that's normal.
After logging back in, try your download again.

What you should expect: After clearing the cache, Steam signs you out. That's not a glitch. Once you log back in, the download should start fresh. If it throws Error 130 again, move to Step 2.

Step 2: Restart your router and PC

This sounds too simple, but I've seen it fix Error 130 more times than I can count. Your router might have a temporary glitch that's blocking Steam's servers.

Turn off your PC.
Unplug your router and modem (if you have both).
Wait 30 seconds.
Plug the modem back in, wait for it to fully boot (check the lights), then plug the router back in.
Wait another 30 seconds, then turn on your PC.
Launch Steam and retry the download.

What you should expect: If the router was the culprit, the error won't appear again right away. Give the download a minute to actually start before you judge it.

Step 3: Update your network drivers

Outdated network drivers can cause exactly this kind of connection timeout. Windows often installs generic drivers that work, but they're not always reliable for long downloads.

Press Windows + X and click Device Manager.
Expand Network adapters.
Right-click your Wi-Fi or Ethernet adapter (the one you're actually using) and select Update driver.
Choose Search automatically for drivers.
If Windows says you're up to date, go to your laptop or motherboard manufacturer's website and grab the latest driver from there. This matters more than Windows Update.
Reboot your PC after updating.

What you should expect: After reboot, the driver will be active. Try Steam again. If the error persists, you've got a software conflict on your hands.

Step 4: Add Steam to your firewall exceptions

Windows Defender Firewall (or any third-party firewall like Norton or McAfee) can block Steam's background services without telling you. This usually happens after a Windows update resets your firewall rules.

Type "Allow an app through Windows Defender Firewall" in the Start menu and open it.
Click Change settings (you'll need admin rights).
Scroll down and find Steam in the list. If it's not there, click Allow another app and browse to C:\Program Files (x86)\Steam\steam.exe.
Make sure both Private and Public checkboxes are ticked for Steam.
Click OK, then completely close Steam and reopen it.

What you should expect: If the firewall was blocking Steam, the download will start within a few seconds. If you're using a third-party firewall, look for its own rules list and add an exception for Steam the same way.

Step 5: Switch your download region

Sometimes the content server you're hitting is having issues, but other regions work fine. This is a temporary workaround, not a permanent fix, but it gets you downloading now.

Go to Steam > Settings > Downloads.
In the Download Region dropdown, pick a nearby city that isn't your default (e.g., if you're in New York, try Chicago).
Click OK and let Steam restart.
Try the download again.

What you should expect: The download should start. You can switch back to your original region later, but honestly, if the new one is stable, just leave it.

Alternative fixes if the main ones fail

If you've gone through all five steps and Error 130 still shows up, try these less common fixes.

Check your proxy or VPN

If you're using a proxy or VPN, Steam might be failing to reach its servers through that tunnel. Turn off the VPN or proxy, then retry. I've had to tell people to disable their VPN more than once after they insisted it couldn't be the problem. It was.

Rename the Steam client registry entry

This one's a bit more technical, but it's safe if you follow it exactly.

Close Steam completely.
Press Windows + R, type regedit, and press Enter.
Go to HKEY_CURRENT_USER\Software\Valve\Steam.
Right-click the Steam key and select Rename. Add .old to the end (so it becomes Steam.old).
Close Regedit and relaunch Steam. It'll rebuild the registry entry fresh.

What you should expect: Steam will act like a new install—it'll ask you to log in and agree to the terms again. Your games are still there, don't worry. You'll just have to re-enter your settings (like download region and library folders).

Uninstall and reinstall Steam (without losing your games)

This is the nuclear option. But do it right so you don't lose your game files.

Back up your steamapps folder. By default, it's at C:\Program Files (x86)\Steam\steamapps. Copy it to your desktop.
Uninstall Steam through Control Panel > Programs and Features.
Download and install Steam from the official site.
After installation, close Steam. Delete the new steamapps folder in the installation directory, then move your backup over.
Launch Steam and log in. Your games will show up, and Steam will verify the files instead of downloading them again.

What you should expect: This wipes any corrupted configuration or cache that survived the earlier steps. It takes about 20 minutes, but it's almost guaranteed to kill Error 130.

Prevention tip

The easiest way to avoid Error 130 in the future is to keep your network drivers current and don't switch between Wi-Fi and Ethernet mid-download. If you have to switch, pause the download first, then switch, then resume. Also, check your firewall rules after every major Windows update. That's the trigger I see most: a Windows feature update resets firewall exceptions, and Steam gets blocked silently until a download fails.