starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Torrents stuck at 100%, does not move to folder for complete files #12804

New issue

Open

opened 2026-02-21 23:11:45 -05:00 by deekerman · 12 comments

deekerman commented

2026-02-21 23:11:45 -05:00

Owner

Originally created by @GasMusK on GitHub (Jan 12, 2022).

qBittorrent & operating system versions

qBittorrent: 4.4.0 x64
Operating system: Windows 10 PRO 21H1 x64 10.0.19043

What is the problem?

When file download is complete (100%), file goes to Stalled and is not moved the the selected folder for completed files.
This has happened to multiple files now.
Force Resume changes status to [F]downloading.
If Force recheck is used the files status changes to checking but progress seems to not update, 394 Mb file has 0% done after 4 hours.
Issue still occurs after restart of program.

Steps to reproduce

download file.
´wait until download is 100%
file will become Stalled and is not moved.

Additional context

No response

Log(s) & preferences file(s)

No response

Originally created by @GasMusK on GitHub (Jan 12, 2022). ### qBittorrent & operating system versions qBittorrent: 4.4.0 x64 Operating system: Windows 10 PRO 21H1 x64 10.0.19043 ### What is the problem? When file download is complete (100%), file goes to Stalled and is not moved the the selected folder for completed files. This has happened to multiple files now. Force Resume changes status to [F]downloading. If Force recheck is used the files status changes to checking but progress seems to not update, 394 Mb file has 0% done after 4 hours. Issue still occurs after restart of program. ### Steps to reproduce 1. download file. 2. ´wait until download is 100% 3. file will become Stalled and is not moved. ### Additional context _No response_ ### Log(s) & preferences file(s) _No response_

deekerman added the

Temp folder

label

2026-02-21 23:11:45 -05:00

deekerman commented

2026-02-21 23:11:52 -05:00

Author

Owner

@RustleBranch commented on GitHub (Jan 12, 2022):

I’m having the same issue with version 4.4.0 on Windows 10.

In addition, when I close the app the process remains running and using a lot of memory, even though I paused all (~100) torrents before exiting.

@RustleBranch commented on GitHub (Jan 12, 2022): I’m having the same issue with version 4.4.0 on Windows 10. In addition, when I close the app the process remains running and using a lot of memory, even though I paused all (~100) torrents before exiting.

deekerman commented

2026-02-21 23:11:52 -05:00

Author

Owner

@GasMusK commented on GitHub (Jan 13, 2022):

This morning it seems like all files have finally moved to completed folder which is on the same HDD as uncompleted folder.
This would previously take seconds not multiple hours.

@GasMusK commented on GitHub (Jan 13, 2022): This morning it seems like all files have finally moved to completed folder which is on the same HDD as uncompleted folder. This would previously take seconds not multiple hours.

deekerman commented

2026-02-21 23:11:52 -05:00

Author

Owner

@RustleBranch commented on GitHub (Jan 13, 2022):

I waited several hours and a handful (less than 10) have move to "Seeding", but the ones I attempted to recheck are still stuck at 0% and a couple dozen more have gotten to the 100%, "Stalled" state. I'll just let it keep running and update here if anything changes.

Reinstalling version 4.4.0 did not make a difference.

@RustleBranch commented on GitHub (Jan 13, 2022): I waited several hours and a handful (less than 10) have move to "Seeding", but the ones I attempted to recheck are still stuck at 0% and a couple dozen more have gotten to the 100%, "Stalled" state. I'll just let it keep running and update here if anything changes. Reinstalling version 4.4.0 did not make a difference.

deekerman commented

2026-02-21 23:11:52 -05:00

Author

Owner

@DarkVoyage commented on GitHub (Jan 17, 2022):

Some new downloads show such behavior. But I saw them turning into Seeding. I saw this just 2-3 times. Also some of them, where not complete on recheck, i.e. 99.9%. And where redownloaded successfully after this. Might be some storage problem. Automatic recheck might help.

@DarkVoyage commented on GitHub (Jan 17, 2022): Some new downloads show such behavior. But I saw them turning into Seeding. I saw this just 2-3 times. Also some of them, where not complete on recheck, i.e. 99.9%. And where redownloaded successfully after this. Might be some storage problem. Automatic recheck might help.

deekerman commented

2026-02-21 23:11:53 -05:00

Author

Owner

@ghost commented on GitHub (Feb 21, 2022):

@glassez I was able to reproduce this problem. What happens here is the download finishes but pieces are still being validated. qBt shows the status as stalled at 100%.
I think it's better that the torrent should change to another state like validating pieces instead of stalled. Because this gives user a wrong idea and they may end up doing pause/resume/force recheck/restart qBt etc which will make it even worse.

@ghost commented on GitHub (Feb 21, 2022): @glassez I was able to reproduce this problem. What happens here is the download finishes but pieces are still being validated. qBt shows the status as stalled at 100%. I think it's better that the torrent should change to another state like validating pieces instead of stalled. Because this gives user a wrong idea and they may end up doing pause/resume/force recheck/restart qBt etc which will make it even worse.

deekerman commented

2026-02-21 23:11:53 -05:00

Author

Owner

@GasMusK commented on GitHub (Feb 21, 2022):

@an0n666 thanks for the info, that is good to know .

@GasMusK commented on GitHub (Feb 21, 2022): @an0n666 thanks for the info, that is good to know .

deekerman commented

2026-02-21 23:11:53 -05:00

Author

Owner

@glassez commented on GitHub (Feb 21, 2022):

I was able to reproduce this problem. What happens here is the download finishes but pieces are still being validated. qBt shows the status as stalled at 100%.

@arvidn, are the pieces really counted in progress before they are validated?

@glassez commented on GitHub (Feb 21, 2022): > I was able to reproduce this problem. What happens here is the download finishes but pieces are still being validated. qBt shows the status as stalled at 100%. @arvidn, are the pieces really counted in progress before they are validated?

deekerman commented

2026-02-21 23:11:53 -05:00

Author

Owner

@ghost commented on GitHub (Feb 21, 2022):

@glassez I’m not sure if they’re being validated or being flushed to disk. But the progress shows 100% and pieces count gradually increases. In the piece bar it shows partial pieces till everything completes.

@ghost commented on GitHub (Feb 21, 2022): @glassez I’m not sure if they’re being validated or being flushed to disk. But the progress shows 100% and pieces count gradually increases. In the piece bar it shows partial pieces till everything completes.

deekerman commented

2026-02-21 23:11:53 -05:00

Author

Owner

@glassez commented on GitHub (Feb 21, 2022):

But the progress shows 100% and pieces count gradually increases. In the piece bar it shows partial pieces till everything completes.

Can you provide a screenshot to illustrate this?

@glassez commented on GitHub (Feb 21, 2022): > But the progress shows 100% and pieces count gradually increases. In the piece bar it shows partial pieces till everything completes. Can you provide a screenshot to illustrate this?

deekerman commented

2026-02-21 23:11:53 -05:00

Author

Owner

@ghost commented on GitHub (Feb 21, 2022):

In the general tab if you scroll down to info section, you can see total piece count is shown there along with the number of pieces that we have in brackets. When the torrent stalls at 100% this have x pieces count is lower than the total piece count and it gradually increases. Once they become same the torrent status changes to seeding.

@ghost commented on GitHub (Feb 21, 2022): In the general tab if you scroll down to info section, you can see total piece count is shown there along with the number of pieces that we have in brackets. When the torrent stalls at 100% this `have x` pieces count is lower than the total piece count and it gradually increases. Once they become same the torrent status changes to seeding. ![image](https://user-images.githubusercontent.com/79678786/154949404-c78649a0-ee91-4e49-b55f-60c208b77c56.png)

deekerman commented

2026-02-21 23:11:53 -05:00

Author

Owner

@ghost commented on GitHub (Feb 21, 2022):

It's also possible that torrent is at close to 100% with 1 or 2 missing pieces but qBt is showing rounded figures. Because I wasn't able to reproduce it everytime.

@ghost commented on GitHub (Feb 21, 2022): It's also possible that torrent is at close to 100% with 1 or 2 missing pieces but qBt is showing rounded figures. Because I wasn't able to reproduce it everytime.

deekerman commented

2026-02-21 23:11:53 -05:00

Author

Owner

@ghost commented on GitHub (Feb 22, 2022):

Seems like there’s a 5 year old thread https://github.com/qbittorrent/qBittorrent/issues/7893#issuecomment-568348830 with the same issue that hundreds of users are facing since many old versions.

qBt rounds up the progress. So if it’s 99.999 it’ll show as 100%.
Also when pieces are being validated some pieces may fail hash check. These pieces are downloaded after all pieces in the queue finish checking. So this can stall a torrent at 100% if you’re downloading 5-6 torrents at the same time and have a lot of disk activity going on.

@ghost commented on GitHub (Feb 22, 2022): Seems like there’s a 5 year old thread https://github.com/qbittorrent/qBittorrent/issues/7893#issuecomment-568348830 with the same issue that hundreds of users are facing since many old versions. qBt rounds up the progress. So if it’s 99.999 it’ll show as 100%. Also when pieces are being validated some pieces may fail hash check. These pieces are downloaded after all pieces in the queue finish checking. So this can stall a torrent at 100% if you’re downloading 5-6 torrents at the same time and have a lot of disk activity going on.