Innovabase › Updates

Downloads and updates that stall, fail or never finish

An update that stops at the same percentage every time is telling you something specific, and it is rarely what people assume. The cause is almost never the speed of the connection. It is usually free space, a permission the installer does not have, or a write that something else is interrupting.

What the stall point tells you

Free space, and how much is actually needed

Updates are not applied in place. A typical patch downloads a compressed package, extracts it somewhere, writes the new files, and only then removes the old ones. During that window, the drive holds the download, the extracted contents and the existing installation simultaneously. A two-gigabyte patch can therefore need considerably more than two gigabytes of headroom, and the requirement is not usually stated anywhere you can see it.

Solid-state drives add a second consideration: they slow down markedly when nearly full, because the controller has less room to move data around internally. A drive at ninety-five per cent capacity can write at a fraction of its rated speed, which turns a ten-minute patch into an hour and makes it look like a network fault.

A practical target is to keep at least ten per cent of the drive free as a standing habit, and to clear more than the patch size before a large update. Where the game sits on a drive that is chronically short of space, moving it to another drive is a better use of an evening than repeatedly clearing a few hundred megabytes.

Permissions and locked files

An installer that cannot write where it needs to fails in ways that rarely mention permissions. On Windows, a game installed outside the usual program directories — on a second drive, or in a folder created by a different user account — can end up with permissions that block the launcher from updating it. Running the launcher as an administrator once is a reasonable diagnostic; if that works, the underlying permissions on the folder are what should be corrected, rather than running as administrator from then on.

On macOS, the security model asks for explicit permission before an application writes to certain locations, and a prompt dismissed weeks ago can quietly block an update today. The privacy and security settings show what has been granted and what has not.

Files held open are the related problem. If any part of the game is still running — a launcher in the system tray, an overlay, an anti-cheat service — the updater cannot replace the files it needs to replace. Closing everything related, or restarting the machine, removes that whole category in one step.

Interrupted writes and damaged patches

A download that completes but fails its integrity check will often restart from the beginning, which is maddening and is the system working correctly — it has determined that what arrived does not match what should have arrived, and would rather fetch it again than install something damaged.

Repeated failures of that kind point at something corrupting the data on the way in or on the way to disk. Candidates, in the order they are worth testing: security software inspecting the download, a flaky connection losing and re-requesting fragments, a failing drive, and — occasionally — memory faults on older machines. Clearing the launcher's download cache before the next attempt prevents a partially bad file from being reused.

Where a launcher offers verify, validate or repair, use it before considering a reinstall. It compares the installed files against a manifest and re-downloads only the differences, which is faster and preserves local settings.

Network causes worth checking

A download that stalls at varying points is more likely a connection problem than a disk one. Three checks cover most cases. First, whether anything else on the network is saturating the link — another device streaming, or a system update running quietly. Second, whether Wi-Fi is the weak point, which a cable settles in one test. Third, whether the connection drops entirely at intervals, which the page on lag and dropouts goes through in more detail.

Metered connections deserve their own mention. A phone hotspot or a plan with a data allowance can throttle or stop a multi-gigabyte download without any error that identifies the reason. Operating systems also treat metered connections differently and may defer downloads on them by design, which looks identical to a stalled update.

App store updates on phones and tablets

Store-managed updates fail differently, because the store rather than the game controls the process. The recurring causes are storage, account state and cached store data.

• Storage on mobile devices fills faster than people expect, and stores need working room beyond the size of the app.
• Updates are often deferred until the device is on Wi-Fi and charging, which is a setting rather than a fault.
• A store account signed out, or a payment method that has expired, can block updates to apps that were previously installed.
• Clearing the store application's cache resolves a well-known class of stalled downloads on Android devices.
• An operating system version below what the current app build requires will stop the update with a message that is easy to misread.

Star Stable Online is listed by the network that supplies our product information as available on Android, iOS and Windows phones and tablets in addition to Windows, macOS and Linux desktops. Where a device is at the edge of what a current build supports, the vendor's own site is the place to check requirements, since they change between releases and this site does not track them.

A working sequence

1. Note where and how it fails. Same percentage or different, during download or during install, with a code or without. Everything below depends on that.
2. Free real space. Aim well above the size of the update. Empty the recycle bin or trash afterwards, since files there still occupy the drive.
3. Close everything related and restart. This releases held files and clears whatever state the failed attempt left.
4. Test on a wired connection. If the stall point moves or disappears, the problem was the link rather than the files.
5. Clear the launcher or store cache. Prevents a damaged partial download from being used again.
6. Exclude the game folder in security software, briefly. Test once, then remove the exclusion if it changed nothing.
7. Run verify or repair. Faster than a reinstall and keeps your settings.
8. Reinstall only if the rest failed. Note your settings first; some are stored outside the game folder and survive, but not all.

Reading an error before you search for it

Error codes are the most searchable thing on the screen and the first thing people dismiss. Copy the text exactly, including any hexadecimal string, before closing the dialogue. Search it together with the game's name on the vendor's own support site rather than in a general search engine, where results for common codes are dominated by pages selling repair tools.

If the code is generic — and many are — the useful information is elsewhere: the launcher's log file, which most launchers keep in the user's application data directory, records what it was doing when it stopped. You do not need to understand the whole file. The last few lines before the failure, quoted in a support ticket, are often enough for someone who does.