EagleGet Stuck at 99%: Why Downloads Stall While Merging

A download that reaches 99% and then seems to freeze is usually not stuck downloading at all. With multi-part downloads, the last few percent are often the merge step: EagleGet is joining the downloaded parts into the finished file. Merging is disk work, not network work, so the progress bar barely moves while the disk is busy — especially for large files on a slow drive. Before you cancel anything, give it time and check the disk-related causes below.

Wait first, then diagnose

For a large file, merging can take minutes. Watch the drive activity: if the disk is busy, EagleGet is probably still working. Cancelling during a merge throws away that work and forces a re-download or a resume cycle. Only start diagnosing if the task has been at 99% far longer than the file size justifies, or if the disk is idle and nothing is happening.

Cause 1: Not enough free space

Merging needs room for the finished file in addition to the parts it is joining. If the destination drive is nearly full, the merge cannot complete. Free up space — at least the full size of the file, ideally more — and then resume the task. This is the single most common cause, and it is also the easiest to rule out.

Cause 2: Permissions on the destination folder

If EagleGet cannot write to the destination or temporary folder, the merge fails. Check that the destination folder is writable by your user account, that no security software is locking the partial files, and that the folder is not on a drive that has gone offline (for example, an external drive that disconnected). Moving the destination to a simple folder on a local drive with free space is a reasonable test.

Cause 3: Antivirus scanning the partial files

Security software sometimes locks a newly written file while scanning it, which can stall a merge. Do not disable your antivirus to test this. Instead, wait for the scan to finish, or check the antivirus log for a hold on the file. If your antivirus flags the file itself, see antivirus-flagging-eagleget — a flagged download is a different problem from a stalled merge.

Cause 4: A part that never actually finished

Occasionally one part of a multi-part download is incomplete even though the total looks like 99%. In that case resuming the task — not restarting it — lets EagleGet fetch the missing piece. Restarting from scratch wastes the 99% you already have; resuming is almost always the better first move. If resume repeatedly returns to 99% and stalls again, the server-side file may have changed, and a fresh link is the next step.

What not to do

Do not delete the partial files to “clean up,” do not rename them mid-task, and do not run the installer or program as administrator as a first resort. Administrator rights can mask a permissions problem rather than fixing it, and they give a legacy program more access than it needs. Fix the folder, the space, or the link first.

FAQ

Is 99% a bug in EagleGet?

Not necessarily. The 99% stage is where parts are joined, verified, and written as the finished file. A pause there is normal for large files; only a very long, disk-idle stall indicates a problem.

How long should merging take?

It depends on file size and disk speed. A multi-gigabyte file on a mechanical drive can take several minutes. A small file that stalls for a long time is more suspicious than a large file that takes a while.

Will pausing and resuming help?

Often, yes — resume re-checks the parts and continues from the missing piece. It is the safest intervention, ahead of cancelling or restarting.

Should I download to a different drive?

If the destination drive is full, slow, or external and unreliable, yes. A local drive with ample free space is the best destination for large multi-part downloads.

Download EagleGet from the EagleGet download hub.