When a download stops at 99 percent

A download that sits at 99 percent is usually not downloading at all. The transfer finished; what the progress bar is now hiding is the work that comes afterwards — unpacking, verifying and writing the files into place — and that work fails in ways the percentage never explains.

The last percent is a different job

Game clients download compressed packages and then rebuild the installation from them. During that stage the disk is busy, the network is idle, and the counter stays where it was. On a large title and a mechanical drive it can take many minutes, so the first useful step is simply to watch the drive activity: if it is working, the client is too.

The same stage runs a verification pass. If a single package fails its checksum, some clients quietly fetch it again and stall the display while they do, and on a slow connection that repeat can take longer than the original download.

Space, permissions and the things that block writing

Unpacking needs room for both the compressed copy and the finished files, which in practice means free space of roughly twice the size of the download. A drive that looked adequate when the download started is the single most common cause of a permanent stall at the end.

After space, look at whatever else can block a write. Real-time antivirus scanning each file as it is unpacked will slow the stage to a crawl and sometimes quarantine a file mid-way; adding the install folder as an exception fixes it. On phones, battery optimisation suspends the store app in the background, and a wrong system clock breaks the certificate checks the client makes before it commits anything.

In order, from safe to drastic

Pause and resume the download, then restart the client entirely — that alone clears a surprising number of stuck finalisation passes. Next, clear the client's download cache, which discards the queue without touching installed games. On a phone, clear the cache of the store app and the download service in the system settings rather than reinstalling anything.

If it survives all that, change the path the data takes: switch the download region or server in the client, or move from Wi-Fi to a cable. Only then use the repair or verify function, which keeps the files already on disk and re-fetches the rest. Deleting the whole installation is the last step, not the first, and on a large game it is the most expensive way to solve a problem that is usually about free space.