How Game Patches Work

Game patches are easier to understand when you separate the download from the installation. A launcher finds the changed data, downloads it, rebuilds the affected files, checks the result, then marks the new version ready to play.

That is why a 2 GB download can need far more free space and keep working after the network activity stops. Once you know what the launcher is doing, most patch problems become much easier to diagnose.

What happens between Download and Play

1. The launcher checks your version. It compares the installed build with the newest build available for your platform.
2. It downloads the changed data. Modern systems try to send only new or modified pieces instead of the entire game.
3. It rebuilds affected files. A small change inside one large data archive can require the launcher to create a new copy of that whole archive.
4. It checks the finished build. The launcher confirms that the files match the developer’s current version.
5. It replaces the old build. Temporary files are removed and the updated version becomes active.

Valve’s SteamPipe technical documentation describes this process in detail. Steam divides content into chunks and reuses unchanged data, but it may still need to rebuild large files on your drive.

A patch changes the installed build

A game patch is a set of changes to the version already on your device. It can replace an executable, repair a quest script, rebalance weapon data, add textures, change configuration defaults, or install entirely new content.

The word patch can be misleading. Early PC patches were often small collections of replacement files. A modern update may rebuild several large archives and change most of the game.

The result is not the old game with a fix taped on. It is a new build that must stay compatible with your saves, settings, platform, and any mods you installed.

Why the download and installation sizes differ

Download size measures what arrives through your internet connection. Installation work measures what must be read, copied, unpacked, rebuilt, checked, and deleted on the drive.

Valve explains that Steam can build a new version of a large packed file beside the old one before switching them. This protects the installed build if the process fails, but it also explains three common surprises:

• A small download may need much more temporary free space.
• Disk usage can remain high after the download reaches 100%.
• A hard drive can take much longer than an SSD to finish the same update.

Do not force-close the launcher while it is writing or checking files. If it appears stuck, check whether disk activity is continuing before interrupting it.

The four update types that matter

• Server-side hotfix: the developer changes online systems without downloading anything to your device. Balance values, drop rates, and server rules can change this way.
• Client hotfix: a small download that usually targets crashes, quest blockers, or urgent bugs.
• Content update: a larger release with features, assets, balance changes, or new areas. These updates are more likely to affect mods and hardware requirements.
• Version upgrade: a major rebuild or separate edition, such as GTA V Enhanced. Treat it like a new version of the game, not a routine fix.

The name alone does not tell you the size. A developer may call a large release a patch, update, hotfix, or title update. The patch notes and download details matter more than the label.

Why updates break games and mods

Three causes explain most failures:

1. A mod expects the old executable. Script extenders and hook frameworks attach to a specific game version. When the executable changes, the framework and everything depending on it may stop, so follow the diagnosis in Mods Broke After an Update.
2. The installation did not finish cleanly. Power loss, a full drive, antivirus interference, or closing the launcher can leave old and new files mixed together. Verifying the files checks the installed build and downloads damaged or missing pieces again.
3. The new build has a bug. Verification cannot repair a problem that is part of the official release. Check the developer’s patch notes and known issues before changing your computer.

Back up your saves first

Make a fresh copy of your saves before any patch, rollback, or fix. Games keep them in a few predictable places, so check these in order:

1. Documents\My Games\<game name> is the classic spot for Bethesda games and many others.
2. %LOCALAPPDATA% and %APPDATA%: paste either into the File Explorer address bar and look for the game or publisher name.
3. The game’s install folder holds saves for some older games.
4. Steam\userdata\<your ID>\<app ID> holds saves for many games that use Steam Cloud.

Copy the save folder to another drive or a cloud folder, and put the date in its name. Our Save Backup Toolkit finds the folders for you and writes a script that backs them all up in one run.

Grab the game’s .ini settings files from the same places, since hours of tweaking live in them. Steam Cloud is not a backup: it can sync a broken save over a good one, so keep your own copy.

Control when important updates happen

For an unmodded game, automatic updates are usually convenient. For a heavily modded game, they can break the setup before its tools are ready.

Steam lets you choose Only update this game when I launch it under Library, Properties, then Updates. You can also schedule automatic update hours. Steam lists the current controls in its download and update guide.

Before accepting a major update, back up your saves, check the required free space, read the patch notes, and confirm that important mods support the new version. Those few minutes are much faster than repairing a half-updated installation.

Verify game files

Verification makes the launcher compare every installed file with the official build and download anything damaged or missing. It fixes a large share of post-patch problems, so try it before anything drastic:

• Steam: right-click the game, then Properties, Installed Files, Verify integrity of game files
• GOG Galaxy: select the game, then the settings icon, then Manage installation, Verify / Repair
• Epic Games Launcher: library, then “…” on the game, then Manage, Verify Files
• Battle.net: select the game, then the gear icon, then Scan and Repair
• EA app: game tile, then “…”, then Repair
• Rockstar Games Launcher: Settings, select the game, then Verify integrity

Verification leaves your saves alone, but it can remove or overwrite mod files inside the game folder. If you mod the game, read Mods Broke After an Update first.

Some games fail one file on every check because they rewrite it at launch, and that is normal. If verification keeps finding damage, look below the game: a failing drive, antivirus quarantining files, or an unstable overclock.

When a patch won’t install

Updates usually fail for boring reasons. Work through this list in order, and most people never reach the end:

1. Free up space on both drives. A patch needs room to download and room to rebuild files, on the game’s drive and on the launcher’s download drive. A 20 GB patch can briefly want 40 GB or more.
2. Restart the launcher, then the PC. Exit fully from the system tray, not just the window. A reboot also clears “content file locked” errors left by a crashed game.
3. Clear the download cache. In Steam, open Settings, then Downloads, then Clear Download Cache. For Battle.net, exit it and delete the Battle.net folder in %ProgramData%.
4. Verify the game files as shown above. A half-finished update can leave files the patcher can’t match.
5. Rule out antivirus and VPNs. Add the game and launcher folders to your antivirus exclusions, then try one update without a VPN or DNS ad blocker.
6. On patch day for an online game, wait. Launch-hour failures are often the servers buckling, not your PC. Check the game’s status page before deleting anything.
7. Reinstall last. Back up your saves, uninstall through the launcher, reboot, then reinstall to the same drive.