-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[4.1.1] Stalled at 99.9% #9047
Comments
you can also complete the torrents by "force rechecking" them, without having to restart. |
As I said in the original post, here's what I did:
|
Just tried that, it didn't help. They all got going at ~25KB/s, and rapidly dropped back to stalled. |
right click and try to "force recheck" |
Sounds like it's not qBittorrent, and instead your ISP is throttling you. You may need to invest in a seedbox. |
seeing that there are at most only 1 or 2 seeds there, you are probably downloading poisoned torrents. |
Closing old issues related to "Stalled"/"Stalled at 99%" and similar. If you can reproduce the problem in the newest version:
If the above does not help, please post a new issue with:
Thank you for your contributions. |
Please provide the following information
qBittorrent version and Operating System
qBittorrent v4.1.1
Windows 10 1803 17134.81
If on linux, libtorrent and Qt version
n/a
What is the problem
I had 2 torrents that stalled at 99.9%. These are large torrents (22.5GB and 29.0GB) that took several days. Nothing I did was able to get them to complete until I saw an old problem (from 2012) that was the same as this. That problem indicated pausing all torrents, quitting qBittorrent, and restarting qBittorrent and restarting all torrents let the torrents complete. So I did this, and the torrents did eventually complete.
What is the expected behavior
Obviously, the torrents should have completed on their own.
Steps to reproduce
Unknown. This is the first time I've seen qBittorrent do this, and I've been using it for a few years now.
Extra info(if any)
n/a
The text was updated successfully, but these errors were encountered: