A transfer at 99.9% still needs its remaining data and successful completion checks. The percentage alone does not tell you whether you are waiting for a rare part, a remote upload slot, verification or a local file operation.
Read the file-level bar first
| Colour | Meaning at file level |
|---|---|
| Black | Parts already obtained |
| Red | No known source currently offers that part |
| Blue shades | Parts available from known sources; darker indicates more sources |
| Yellow | A part currently being downloaded |
| Green progress indicator | Overall progress; a completed file has a green bar |
Make sure you are looking at a file's bar. The bars beside individual peers use a different legend. For example, a source's silver area can indicate parts that source also lacks, rather than data your computer has already received.
Check the last missing parts, not just source totals
Expand the source list and compare which parts those clients offer. Many peers with the same gap cannot collectively provide the missing data. A large total source count is therefore not proof that the file is currently completable.
Review Last seen complete if your client shows it. It is useful historical information about availability, not a reservation of a source that must still be online. Note what changes over a reasonable connected session before deciding the transfer is permanently unavailable.
If a useful source exists but you are queued
Read that source's state and queue rank. A peer may have the part you need while allocating its upload capacity to somebody else. Setting your local priority to High does not force that peer to create an extra slot.
Keep the unfinished transfer intact and use the queue explanation. Repeated cancellations can discard progress without changing which sources have the final part.
If the client is checking or repairing data
Look at the state and log rather than interpreting every pause as a network failure. eMule checks data integrity and can request damaged data again. Repeated corruption messages are a different clue from a red area with no known source.
A matching file hash concerns data integrity, not whether the content is safe or honestly named. Continue to use the file-safety checks before opening an obtained file.
If it is completing, erroneous or unable to write
Check the destination path and free space on both Temporary and Incoming volumes. A download can have the needed network data yet fail during a local file operation, particularly when the final destination is on another drive.
Use the disk-error guide for that case. Renaming an almost-complete .part file to its expected extension does not finish or validate it.
Preserve the useful evidence
Record the exact state, missing-part pattern, useful sources, last-complete observation and log message. Those details identify the next check. There is no setting that manufactures data nobody offers; leaving the transfer intact preserves the possibility of resuming if an appropriate source returns.
Sources and further reading
- Official help: progress-bar colours
- Official FAQ: incomplete files and sources
- Official help: corruption handling
- Official troubleshooting: file-operation errors
Some project help includes historical interface examples. Match the instructions to your installed build.