[4.0.1] Re-downloading old finished torrents without consent #6387

Closed
opened 2026-02-21 18:23:15 -05:00 by deekerman · 32 comments
Owner

Originally created by @reyaz006 on GitHub (Nov 23, 2017).

qBittorrent version and Operating System

qBittorrent 4.0.1
Windows 8.1 x64

If on linux, libtorrent and Qt version

(type here)

What is the problem

Upgraded from 3.3.13 to 4.0.1. Noticed slow loading and unresponsive behavior. Noticed that qBittorrent tries to re-check and re-download many of old torrents which were FINISHED or PAUSED or at ERROR state before. Most of those downloaded files I've already moved somewhere else after MAKING SURE THAT TORRENTS ARE STILL ON LIST AND PAUSED OR OTHERWISE SHOULD NOT BE RUNNING.
My download drive got filled and now I have to sort it out all by hand.

What is the expected behavior

Should not have started old downloads without my consent.

Steps to reproduce

Install new version. Run. Get mad.

Extra info(if any)

More than 16000 torrents on my list.

Originally created by @reyaz006 on GitHub (Nov 23, 2017). ### qBittorrent version and Operating System qBittorrent 4.0.1 Windows 8.1 x64 ### If on linux, libtorrent and Qt version (type here) ### What is the problem Upgraded from 3.3.13 to 4.0.1. Noticed slow loading and unresponsive behavior. Noticed that qBittorrent tries to re-check and re-download many of old torrents which were FINISHED or PAUSED or at ERROR state before. Most of those downloaded files I've already moved somewhere else after MAKING SURE THAT TORRENTS ARE STILL ON LIST AND PAUSED OR OTHERWISE SHOULD NOT BE RUNNING. My download drive got filled and now I have to sort it out all by hand. ### What is the expected behavior Should not have started old downloads without my consent. ### Steps to reproduce Install new version. Run. Get mad. ### Extra info(if any) More than 16000 torrents on my list.
Author
Owner

@Hilvern commented on GitHub (Nov 23, 2017):

Same issue :(

After having seeded up to a certain ratio my downloaded torrents, I usually move the files to an external storage but do keep the torrents in qBittorrent in case I decide to re-seed some time after, and also for my torrent history (to avoid downloading twice the same thing). These torrents already downloaded but showing a 0.0% progress (as files were moved) are usually categorized in the ERROR section (Files missing)

With the 4.0.1 update, almost all these torrents are put back to an "active" status and qBittorrent attempts to re-download them. It is quite annoying, and I had to select them all then "pause" them in order to "solve" the situation.

I was pretty sure something like this was gonna happen with this v4 update... fortunately I don't have a lot of torrents in my list, a 100 times less than reyaz006. Also I must say the logo appears to be of very poor quality on the windows taskbar.

Anyway, congrats to the dev team for their great work to this major update which seems to work quite well apart from these minor issues. Thanks for providing us with an ad-free quality tool.

@Hilvern commented on GitHub (Nov 23, 2017): Same issue :( After having seeded up to a certain ratio my downloaded torrents, I usually move the files to an external storage but do keep the torrents in qBittorrent in case I decide to re-seed some time after, and also for my torrent history (to avoid downloading twice the same thing). These torrents already downloaded but showing a 0.0% progress (as files were moved) are usually categorized in the ERROR section (Files missing) With the 4.0.1 update, almost all these torrents are put back to an "active" status and qBittorrent attempts to re-download them. It is quite annoying, and I had to select them all then "pause" them in order to "solve" the situation. I was pretty sure something like this was gonna happen with this v4 update... fortunately I don't have a lot of torrents in my list, a 100 times less than reyaz006. Also I must say the logo appears to be of very poor quality on the windows taskbar. Anyway, congrats to the dev team for their great work to this major update which seems to work quite well apart from these minor issues. Thanks for providing us with an ad-free quality tool.
Author
Owner

@bakedmotato commented on GitHub (Nov 23, 2017):

I had this problem. Try turning off the "Keep incomplete torrents in" feature in the download options.

@bakedmotato commented on GitHub (Nov 23, 2017): I had this problem. Try turning off the "Keep incomplete torrents in" feature in the download options.
Author
Owner

@reyaz006 commented on GitHub (Nov 24, 2017):

Try turning off the "Keep incomplete torrents in" feature in the download options.

It wasn't enabled for me.

@reyaz006 commented on GitHub (Nov 24, 2017): > Try turning off the "Keep incomplete torrents in" feature in the download options. It wasn't enabled for me.
Author
Owner

@reyaz006 commented on GitHub (Nov 27, 2017):

I can't even understand how can I describe this issue. Just by keeping a torrent on my list in a PAUSED state, I'm risking that qBittorrent is going to create or overwrite or re-allocate or break the file. I've lost few updated files due to that. I've edited the files after they have been downloaded (and paused) and kept them under the same name, then at some point qBittorrent broke them. Can't it just leave the torrent there and don't do a thing to it if it's paused?

@reyaz006 commented on GitHub (Nov 27, 2017): I can't even understand how can I describe this issue. Just by keeping a torrent on my list in a PAUSED state, I'm risking that qBittorrent is going to create or overwrite or re-allocate or break the file. I've lost few updated files due to that. I've edited the files after they have been downloaded (and paused) and kept them under the same name, then at some point qBittorrent broke them. Can't it just leave the torrent there and don't do a thing to it if it's paused?
Author
Owner

@lite104me commented on GitHub (Nov 29, 2017):

Had same issue after upgrading to 4.0.1 x64. Now all my torrents stay in completed and will not seed for longer than 5 seconds.

@lite104me commented on GitHub (Nov 29, 2017): Had same issue after upgrading to 4.0.1 x64. Now all my torrents stay in completed and will not seed for longer than 5 seconds.
Author
Owner

@thalieht commented on GitHub (Nov 30, 2017):

@lite104me not the same issue. For your issue select all torrents (ctrl+a) or desired ones and right click -> limit share ratio: no share limit.

@thalieht commented on GitHub (Nov 30, 2017): @lite104me not the same issue. For your issue select all torrents (ctrl+a) or desired ones and right click -> limit share ratio: no share limit.
Author
Owner

@mustafaismail22 commented on GitHub (Dec 11, 2017):

I have the same issue.

qBittorrent version and Operating System
qBittorrent 4.0.2
Windows 10 x64

@mustafaismail22 commented on GitHub (Dec 11, 2017): I have the same issue. **qBittorrent version and Operating System** qBittorrent 4.0.2 Windows 10 x64
Author
Owner

@reyaz006 commented on GitHub (Jan 4, 2018):

Dear god. It happened again. qbt crashed, and then I restarted it. Only few hours later I noticed that it has downloaded 3 whole torrents which were previously downloaded and stopped. This time, I noticed this:

  • qbt does not update the "Completed On" data for such torrents, even though it re-downloads and completes them.
  • qbt resets tags for such torrents. Previously I had ~300 untagged, now I have ~1200 untagged.

PLEASE. I like the "PAUSE" button. But it doesn't work right. PLEASE add the "STOP AND NEVER TOUCH IT AGAIN" button. Maybe that'll work.

@reyaz006 commented on GitHub (Jan 4, 2018): Dear god. It happened again. qbt crashed, and then I restarted it. Only few hours later I noticed that it has downloaded 3 whole torrents which were previously downloaded and stopped. This time, I noticed this: - qbt does not update the "Completed On" data for such torrents, even though it re-downloads and completes them. - qbt resets tags for such torrents. Previously I had ~300 untagged, now I have ~1200 untagged. PLEASE. I like the "PAUSE" button. But it doesn't work right. PLEASE add the "STOP AND NEVER TOUCH IT AGAIN" button. Maybe that'll work.
Author
Owner

@Nischi85 commented on GitHub (Jan 10, 2018):

I think my issue might be similiar, but maybe not exactly same. My torrents finish, and ends up in the "stalled" status which is fine because it's waiting to seed, but every now and then it re-downloads the whole torrent again!(I've not had the program turned off, it's on all the time) even while the files are still accessible and at the same location! I've redownloaded loads of stuff like this accidentally, and some of the files are quite big as well meaning it's eating up my bandwidth and ratio.

@Nischi85 commented on GitHub (Jan 10, 2018): I think my issue might be similiar, but maybe not exactly same. My torrents finish, and ends up in the "stalled" status which is fine because it's waiting to seed, but every now and then it re-downloads the whole torrent again!(I've not had the program turned off, it's on all the time) even while the files are still accessible and at the same location! I've redownloaded loads of stuff like this accidentally, and some of the files are quite big as well meaning it's eating up my bandwidth and ratio.
Author
Owner

@plazadelmar commented on GitHub (Feb 15, 2018):

Same problem here.

PC with torrent version 4.0.3 64-bits.

@plazadelmar commented on GitHub (Feb 15, 2018): Same problem here. PC with torrent version 4.0.3 64-bits.
Author
Owner

@JoanneMullen commented on GitHub (Feb 23, 2018):

For the love of God, add an option where you can choose to have a 'file error' rather than automatically downloading a deleted file again. It makes QBit a pain to use. uTorrent does this properly, and so anyone coming to QBit from uTorrent after the latest security scare is going to get a nasty surprise or two.

@JoanneMullen commented on GitHub (Feb 23, 2018): For the love of God, add an option where you can choose to have a 'file error' rather than automatically downloading a deleted file again. It makes QBit a pain to use. uTorrent does this properly, and so anyone coming to QBit from uTorrent after the latest security scare is going to get a nasty surprise or two.
Author
Owner

@fatjing commented on GitHub (Feb 26, 2018):

qBittorrent 4.0.4
Windows 10 x64

Still not fixed. This is so frustrating.

@fatjing commented on GitHub (Feb 26, 2018): qBittorrent 4.0.4 Windows 10 x64 Still not fixed. This is so frustrating.
Author
Owner

@ihendriks commented on GitHub (Mar 9, 2018):

Same issue.

qBittorrent 4.0.4 (x64)
Windows 10 (x64)

@ihendriks commented on GitHub (Mar 9, 2018): Same issue. qBittorrent 4.0.4 (x64) Windows 10 (x64)
Author
Owner

@IgnacioFDM commented on GitHub (Mar 11, 2018):

Same problem here on 4.04 and Windows 7 x64

@IgnacioFDM commented on GitHub (Mar 11, 2018): Same problem here on 4.04 and Windows 7 x64
Author
Owner

@plazadelmar commented on GitHub (Mar 11, 2018):

Is someone working on this problem?

On 11 Mar 2018, at 18:13, IgnacioFDM notifications@github.com wrote:

Same problem here on 4.04 and Windows 7 x64


You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/qbittorrent/qBittorrent/issues/7846#issuecomment-372131698, or mute the thread https://github.com/notifications/unsubscribe-auth/Ai0PCDcemjfPlU0BFFe9fPC1UI63wbRzks5tdVtBgaJpZM4Qow6w.

@plazadelmar commented on GitHub (Mar 11, 2018): Is someone working on this problem? > On 11 Mar 2018, at 18:13, IgnacioFDM <notifications@github.com> wrote: > > Same problem here on 4.04 and Windows 7 x64 > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub <https://github.com/qbittorrent/qBittorrent/issues/7846#issuecomment-372131698>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ai0PCDcemjfPlU0BFFe9fPC1UI63wbRzks5tdVtBgaJpZM4Qow6w>. >
Author
Owner

@bobsage123 commented on GitHub (Mar 12, 2018):

For all the crap uTorrent gets, it's insanely less buggy than Qbittorent. This is number #5 major bug thats affecting me so far.

@bobsage123 commented on GitHub (Mar 12, 2018): For all the crap uTorrent gets, it's insanely less buggy than Qbittorent. This is number #5 major bug thats affecting me so far.
Author
Owner

@ihendriks commented on GitHub (Mar 13, 2018):

I've changed back to 3.3.16 and haven't seen the issue since. Don't know if that's an option for everyone though.

@ihendriks commented on GitHub (Mar 13, 2018): I've changed back to 3.3.16 and haven't seen the issue since. Don't know if that's an option for everyone though.
Author
Owner

@plazadelmar commented on GitHub (Apr 12, 2018):

This issue has been posted for version 4.0.1, I'm on version 4.0.4 and the problem still persists. I think they only way to solve it is to go back to my previous torrent software that worked fine.

@plazadelmar commented on GitHub (Apr 12, 2018): This issue has been posted for version 4.0.1, I'm on version 4.0.4 and the problem still persists. I think they only way to solve it is to go back to my previous torrent software that worked fine.
Author
Owner

@tehmasterer commented on GitHub (Apr 17, 2018):

Same problem here. I updated from version 3.3.1.6 to 4.0.4 because qbittorrent was hanging in task manager. Updating solved the problem but a new one arose. ALL my paused torrents started to download again. Multiple files have been overwritten. Super pissed!

@tehmasterer commented on GitHub (Apr 17, 2018): Same problem here. I updated from version 3.3.1.6 to 4.0.4 because qbittorrent was hanging in task manager. Updating solved the problem but a new one arose. ALL my paused torrents started to download again. Multiple files have been overwritten. Super pissed!
Author
Owner

@Kyguy0 commented on GitHub (Apr 30, 2018):

Same problem, super disappointing. 4.0.4 on OSX.

@Kyguy0 commented on GitHub (Apr 30, 2018): Same problem, super disappointing. 4.0.4 on OSX.
Author
Owner

@kristofferR commented on GitHub (May 9, 2018):

Same issue here.

4.1.0, macOS

@kristofferR commented on GitHub (May 9, 2018): Same issue here. 4.1.0, macOS
Author
Owner

@KMFR commented on GitHub (May 9, 2018):

Same issues here too, been going on for six months or so already... Paused torrents whose content has already been deleted always start re-downloading after a restart. Are there any better alternatives? I guess utorrent is out of the question, and Deluge seems pretty bad too...

@KMFR commented on GitHub (May 9, 2018): Same issues here too, been going on for six months or so already... Paused torrents whose content has already been deleted always start re-downloading after a restart. Are there any better alternatives? I guess utorrent is out of the question, and Deluge seems pretty bad too...
Author
Owner

@ihendriks commented on GitHub (May 9, 2018):

@KMFR I just went back to pre-4.0, which works fine. Haven't really tried anything else because I can't be bothered.

@ihendriks commented on GitHub (May 9, 2018): @KMFR I just went back to pre-4.0, which works fine. Haven't really tried anything else because I can't be bothered.
Author
Owner

@bobsage123 commented on GitHub (May 9, 2018):

I'm really not sure why they can't just code something that says if file in completed torrent is renamed > throw error.

And NOT redownload the file. I have thousands of torrents running and sometimes accidently rename one of the files in them. Then the file is redownloaded and I have two of the same copy on my HD, eating up space, plus it's killing my ratio on the private tracker. Never had this issue in utorrent.

@bobsage123 commented on GitHub (May 9, 2018): I'm really not sure why they can't just code something that says if file in completed torrent is renamed > throw error. And NOT redownload the file. I have thousands of torrents running and sometimes accidently rename one of the files in them. Then the file is redownloaded and I have two of the same copy on my HD, eating up space, plus it's killing my ratio on the private tracker. Never had this issue in utorrent.
Author
Owner

@KMFR commented on GitHub (May 12, 2018):

@ihendriks thanks I'll do the same until I find a better alternative, don't know why I didn't think of that earlier

@KMFR commented on GitHub (May 12, 2018): @ihendriks thanks I'll do the same until I find a better alternative, don't know why I didn't think of that earlier
Author
Owner

@marianolc commented on GitHub (May 18, 2018):

Same problem. In windows. Installed last updated and suddenly old downloads started again(all those were finished already)

@marianolc commented on GitHub (May 18, 2018): Same problem. In windows. Installed last updated and suddenly old downloads started again(all those were finished already)
Author
Owner

@ghost commented on GitHub (May 19, 2018):

I'm having the same problem. I moved the files (and set the file locations) to an external hard drive and later when I rebooted my computer (with external hard drive connected) the files commenced downloading again.

@ghost commented on GitHub (May 19, 2018): I'm having the same problem. I moved the files (and set the file locations) to an external hard drive and later when I rebooted my computer (with external hard drive connected) the files commenced downloading again.
Author
Owner

@sledgehammer999 commented on GitHub (May 23, 2018):

Libtorrent bug: https://github.com/arvidn/libtorrent/issues/3045

@sledgehammer999 commented on GitHub (May 23, 2018): Libtorrent bug: https://github.com/arvidn/libtorrent/issues/3045
Author
Owner

@delykj commented on GitHub (May 29, 2018):

When will be this bug resolved? Downloaded latest 4.1.1 version and the bug still exists. This bug opened more than six months ago.
If this will be not resolved, then this software is not usable and need to switch back to uTorrent.

@delykj commented on GitHub (May 29, 2018): When will be this bug resolved? Downloaded latest 4.1.1 version and the bug still exists. This bug opened more than six months ago. If this will be not resolved, then this software is not usable and need to switch back to uTorrent.
Author
Owner

@sledgehammer999 commented on GitHub (May 29, 2018):

@delykj learn to read and have patience. https://github.com/arvidn/libtorrent/issues/3045#issuecomment-392368607

@sledgehammer999 commented on GitHub (May 29, 2018): @delykj learn to read and have patience. https://github.com/arvidn/libtorrent/issues/3045#issuecomment-392368607
Author
Owner

@delykj commented on GitHub (May 29, 2018):

Yes, I have read that thread.
"learn to read"
Don't be rude.

@delykj commented on GitHub (May 29, 2018): Yes, I have read that thread. "learn to read" Don't be rude.
Author
Owner

@sledgehammer999 commented on GitHub (May 29, 2018):

PR fixing this: #9007

@sledgehammer999 commented on GitHub (May 29, 2018): PR fixing this: #9007
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/qBittorrent#6387
No description provided.