Stopping Steam from updating in the background isn't as simple as flipping a single switch in the main settings menu. Valve designs the platform to stay current by default, meaning client patches and game updates often download uninvited, eating up bandwidth and occasionally breaking mods. If you want total control over your system resources and game versions, you need to use a mix of built-in scheduling tricks, file property locks, and command-line flags.
This guide breaks down how to halt automatic downloads for both individual games and the core Steam client, giving you back command over your own hardware.
Why Steam Forces Updates and Why You Want to Stop Them
Valve pushes background updates to maintain multiplayer server compatibility, patch security vulnerabilities, and roll out new interface features. However, these updates carry drawbacks for power users.
Background downloads can saturate your internet connection right when you need bandwidth for other tasks. More critically, automatic game patches frequently break heavily modded single-player titles like Skyrim, Fallout, or Cities: Skylines. When an update drops unexpectedly, your favorite mods stop working overnight until modders spend weeks updating their tools.
Preventing these updates keeps your setup stable, predictable, and entirely under your supervision.
Method 1: Restricting Automatic Game Updates Globally
If you want to stop games from downloading updates while you're trying to game or work, you can't turn off all auto-updates entirely, but you can restrict the window during which they are allowed to happen.
Open your Steam client, click on Steam in the top-left corner, and select Settings, then navigate to the Downloads tab. Look for the section labeled Download Restrictions.
Here, check the box that says Only auto-options games between and set a very narrow one-hour window—such as 4:00 AM to 5:00 AM. Unless your computer is actively powered on and running Steam during that exact hour, automatic background downloads will effectively freeze.
Additionally, uncheck any options allowing downloads while you are streaming or playing games so that background processes never steal your CPU cycles or network packets mid-match.
Method 2: Stopping Updates for Specific Games
For individual titles, Valve provides a built-in switch that halts background downloads, though it handles them by deferring the download until you click play.
- Open your Steam Library.
- Right-click the game you want to protect and select Properties.
- Click on the Updates tab on the left menu.
- Under the Automatic updates dropdown, change the setting from Always keep this game updated to Only update this game when I launch it.
This stops Steam from grabbing gigabytes of patch data in the background. The game remains untouched until the exact moment you boot it up.
(Note: If the game requires an online connection to launch, Steam may refuse to start it without downloading the patch first. For total offline protection, combine this with offline mode or the manifest lock detailed below.)
Method 3: The Manifest Read-Only Trick for Hard Blocks
If you want to completely freeze a game in its current version and prevent Steam from forcing an update even when you click play, you must manipulate the game manifest files. Steam tracks game builds using manifest files named after unique App IDs. By making these files unmodifiable, you block Steam from writing update instructions to them.
First, close Steam completely from your system tray to ensure no files are locked by the running client. Navigate to your main Steam installation directory, usually found at C:\Program Files (x86)\Steam\steamapps\.
Find the file starting with appmanifest_ followed by your target game's unique ID number and ending with .acf (for instance, appmanifest_489830.acf for Skyrim Special Edition). Right-click the file, select Properties, and check the Read-only box at the bottom of the General tab. Click Apply.
When Steam tries to queue an update, it will fail to update the manifest file, resulting in a disk write error that halts the update entirely. To play the game safely, you can launch the game executable directly from its installation folder rather than through the Steam UI.
Method 4: Preventing the Steam Client Itself from Updating
Stopping individual games is useful, but stopping the core desktop application from forcing updates requires a different approach. Valve tightly couples the client bootstrapper with their online servers, making complete client immobilization difficult, but you can block automatic bootstrap patches using shortcut arguments or configuration flags.
Using Command-Line Shortcuts
You can instruct the Steam desktop launcher to ignore bootstrap updates by appending specific flags to your shortcut target.
- Right-click your desktop Steam shortcut and select Properties.
- In the Shortcut tab, locate the Target field, which points to
C:\Program Files (x86)\Steam\steam.exe. - Add a space after the closing quotation mark and paste the following parameters:
-noverifyfiles -nobootstrapupdate -skipinitialbootstrap. - Click Apply and save your changes.
When you launch Steam using this modified shortcut, it bypasses several verification checks and startup update routines.
Creating a Steam.cfg File
For a deeper configuration block, you can create a localized control file inside your core Steam directory.
- Open Notepad or any plain text editor.
- Type or paste the following line:
BootStrapperInhibitAll=Enable - Save the file as
Steam.cfgand place it directly inside your main Steam installation folder (next tosteam.exe).
This configuration flag tells the bootstrapper to inhibit automatic updates where possible. Keep in mind that Valve frequently updates their client architecture, and major platform overhauls can occasionally deprecate legacy configuration files. Always back up your files before altering core directories.
Handling Offline Mode and Network Isolation
The most foolproof method to stop Steam from updating anything—client or games—is to cut its internet access entirely once your desired environment is stable.
Open Steam, click Steam in the top menu, and select Go Offline. Steam will restart in offline mode, cutting off background data transfers. For absolute security against forced background checks, you can also add a rule in your operating system's firewall (such as Windows Defender Firewall) to block outbound connections for steam.exe.
When you want to browse the store or chat with friends, simply toggle the firewall rule back on or reconnect. For more details on managing client preferences, review the official Steam Support Documentation.
Common Mistakes to Avoid
When attempting to lock down your Steam installation, avoid these frequent pitfalls:
- Leaving Steam running in the system tray while trying to edit manifest files or configuration text. Always exit the application completely first.
- Forgetting to remove the read-only attribute from manifest files when you do eventually want to update a game. Leaving them locked permanently will cause recurring error loops if an essential patch is later required.
- Relying solely on third-party software launchers that promise instant bypasses; these often violate the Valve Anti-Cheat (VAC) Policy and can risk your entire account standing. Stick to native configuration tweaks and file permission changes.
Frequently Asked Questions
Will setting my game manifest to read-only get me banned?
No. Modifying local file permissions or setting configuration flags on your own computer does not violate Valve's terms of service, as it does not inject code into memory or alter multiplayer game code to gain an unfair competitive advantage.
Why does Steam force client updates even after I added shortcut flags?
Valve occasionally updates its core login protocols and security certificates. When a mandatory security threshold is crossed, the client will ignore older bootstrap flags and force a connection update to maintain network integrity.
Can I revert to an old game version after an update has already installed?
Yes, though it requires advanced tools like Depot Downloader via the Steam console to pull older manifest manifests directly from Valve's content servers. It is always easier to prevent the update beforehand using the manifest lock method.
Does blocking updates save bandwidth if I have a metered connection?
Yes. Stopping automatic background downloads prevents hundreds of gigabytes of patches and shader cache downloads from hitting your network unexpectedly, preserving your data cap for gameplay and direct downloads you initiate manually.
