starred/qBittorrent

Fork 0

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

Selecting only some files not working #3709

New issue

Closed

opened 2026-02-21 16:55:18 -05:00 by deekerman · 14 comments

deekerman commented

2026-02-21 16:55:18 -05:00

Owner

Originally created by @AndersMalmgren on GitHub (Jan 11, 2016).

If you select only some files in a torrent you will end up with the selected files, but also some parts of other files in the torrent

Originally created by @AndersMalmgren on GitHub (Jan 11, 2016). If you select only some files in a torrent you will end up with the selected files, but also some parts of other files in the torrent

deekerman closed this issue

2026-02-21 16:55:21 -05:00

deekerman commented

2026-02-21 16:55:23 -05:00

Author

Owner

@coolio2013 commented on GitHub (Jan 13, 2016):

There is no way to fix it. This is by design: pieces of a torrent may contain parts of files you don't want, due to selected size of pieces when the torrent was created (they can lay over).

@coolio2013 commented on GitHub (Jan 13, 2016): There is no way to fix it. This is by design: pieces of a torrent may contain parts of files you don't want, due to selected size of pieces when the torrent was created (they can lay over).

deekerman commented

2026-02-21 16:55:23 -05:00

Author

Owner

@AndersMalmgren commented on GitHub (Jan 14, 2016):

That is strange, I never noticed this behaviour with utorrent, do they delete the unwanted content?

@AndersMalmgren commented on GitHub (Jan 14, 2016): That is strange, I never noticed this behaviour with utorrent, do they delete the unwanted content?

deekerman commented

2026-02-21 16:55:23 -05:00

Author

Owner

@Deadpool-XBL commented on GitHub (Jan 14, 2016):

I am having this issue too. I am not sure why you are saying that there is no way to fix this as it use to work before in qBittorrent. I am actually going to try and install an older version today hoping to get back what I lost somewhere along the way.

@Deadpool-XBL commented on GitHub (Jan 14, 2016): I am having this issue too. I am not sure why you are saying that there is no way to fix this as it use to work before in qBittorrent. I am actually going to try and install an older version today hoping to get back what I lost somewhere along the way.

deekerman commented

2026-02-21 16:55:23 -05:00

Author

Owner

@Deadpool-XBL commented on GitHub (Jan 14, 2016):

I just reverted to 3.2.5 and its working fine.

@Deadpool-XBL commented on GitHub (Jan 14, 2016): I just reverted to 3.2.5 and its working fine.

deekerman commented

2026-02-21 16:55:23 -05:00

Author

Owner

@AndersMalmgren commented on GitHub (Jan 14, 2016):

Thanks for confirming it, thought it was strange

@AndersMalmgren commented on GitHub (Jan 14, 2016): Thanks for confirming it, thought it was strange

deekerman commented

2026-02-21 16:55:23 -05:00

Author

Owner

@chrishirst commented on GitHub (Jan 15, 2016):

I never noticed this behaviour with utorrent, do they delete the unwanted content?

Nope, uTorrent puts 'unwanted' pieces in a hidden dat file (uTorrent[random-chars].dat)

@chrishirst commented on GitHub (Jan 15, 2016): > I never noticed this behaviour with utorrent, do they delete the unwanted content? Nope, uTorrent puts 'unwanted' pieces in a hidden dat file (uTorrent[random-chars].dat)

deekerman commented

2026-02-21 16:55:23 -05:00

Author

Owner

@coolio2013 commented on GitHub (Jan 15, 2016):

@AndersMalmgren: You're right. In v3.3.1 I now also have 3 files in folder '.unwanted', smaller than piece-size of the torrent; also the progress-bar in 'General' does not show these unwanted files as white areas. Not sure if this is an issue of qbt, though.
However, your report is kind of thin ;-)

@coolio2013 commented on GitHub (Jan 15, 2016): @AndersMalmgren: You're right. In v3.3.1 I now also have 3 files in folder '.unwanted', smaller than piece-size of the torrent; also the progress-bar in 'General' does not show these unwanted files as white areas. Not sure if this is an issue of qbt, though. However, your report is kind of thin ;-)

deekerman commented

2026-02-21 16:55:23 -05:00

Author

Owner

@chrishirst commented on GitHub (Jan 15, 2016):

smaller than piece-size of the torrent;

They are only the size of the bytes that cross two files.

does not show these unwanted files as white areas

It won't, they are not required so will not be requested, therefore are not going to be marked as 'missing' or 'don't have'.

@chrishirst commented on GitHub (Jan 15, 2016): > smaller than piece-size of the torrent; They are only the size of the bytes that cross two files. > does not show these unwanted files as white areas It won't, they are not required so will not be requested, therefore are not going to be marked as 'missing' or 'don't have'.

deekerman commented

2026-02-21 16:55:24 -05:00

Author

Owner

@coolio2013 commented on GitHub (Jan 15, 2016):

@chrishirst: No, those files are complete (JPGs). Torrent was finished today 14:15 (and automatically rechecked upon completion), two unwanted have file-date 14:08:56 (same second!), and one has file-date of yesterday. Folder .unwanted was created 5 days ago, when I unselected those 3 files. Creator was utorrent/1610.
Initially I also thought the reported issue was impossible, by chance I noticed the same. But something seems fishy (I can't remember anything related in changelogs). Not a big problem-there are much bigger issues currently.

@coolio2013 commented on GitHub (Jan 15, 2016): @chrishirst: No, those files are complete (JPGs). Torrent was finished today 14:15 (and automatically rechecked upon completion), two unwanted have file-date 14:08:56 (same second!), and one has file-date of yesterday. Folder .unwanted was created 5 days ago, when I unselected those 3 files. Creator was utorrent/1610. Initially I also thought the reported issue was impossible, by chance I noticed the same. But something seems fishy (I can't remember anything related in changelogs). Not a big problem-there are much bigger issues currently.

deekerman commented

2026-02-21 16:55:24 -05:00

Author

Owner

@chrishirst commented on GitHub (Jan 15, 2016):

No, those files are complete (JPGs). Torrent was finished today 14:15 (and automatically rechecked upon completion), two unwanted have file-date 14:08:56 (same second!), and one has file-date of yesterday. Folder .unwanted was created 5 days ago,

it all depends on where the cross file boundaries where placed in the torrent structure.

@chrishirst commented on GitHub (Jan 15, 2016): > No, those files are complete (JPGs). Torrent was finished today 14:15 (and automatically rechecked upon completion), two unwanted have file-date 14:08:56 (same second!), and one has file-date of yesterday. Folder .unwanted was created 5 days ago, it all depends on where the cross file boundaries where placed in the torrent structure.

deekerman commented

2026-02-21 16:55:24 -05:00

Author

Owner

@vit5421 commented on GitHub (Jan 18, 2016):

I have some parts of other files in the torrent on the version 3.3.1 and 3.3.2. This is not by design. The 3.2.5 works absolutely perfect with no problem on the same torrent.

@vit5421 commented on GitHub (Jan 18, 2016): I have some parts of other files in the torrent on the version 3.3.1 and 3.3.2. This is not by design. The 3.2.5 works absolutely perfect with no problem on the same torrent.

deekerman commented

2026-02-21 16:55:24 -05:00

Author

Owner

@thalieht commented on GitHub (Jan 19, 2016):

The .unwanted folder functionality was removed in 3.3 https://github.com/qbittorrent/qBittorrent/pull/3687#issuecomment-137259448

If users want to differentiate they can always use .!qB.

This doesn't seem elegant but:

libtorrent 1.1.x will support "partfiles" or whatever they're called. It is a single file per torrent where pieces from deselected files are written to and then used to verify the hashes.

So i guess patience is a virtue.

@thalieht commented on GitHub (Jan 19, 2016): The .unwanted folder functionality was removed in 3.3 https://github.com/qbittorrent/qBittorrent/pull/3687#issuecomment-137259448 > If users want to differentiate they can always use .!qB. This doesn't seem elegant but: > libtorrent 1.1.x will support "partfiles" or whatever they're called. It is a single file per torrent where pieces from deselected files are written to and then used to verify the hashes. So i guess patience is a virtue.

deekerman commented

2026-02-21 16:55:24 -05:00

Author

Owner

@vit5421 commented on GitHub (Jan 19, 2016):

I just trying to download one file and qB is downloading extra files and its very confusing.

I am back to 3.2.5 and feel much more comfortable with no partfiles and clear watch folder.

It will be very nice option also to do not delete the loaded files in any circumstances during multiple files torrent as Mtorrent client do.

@vit5421 commented on GitHub (Jan 19, 2016): I just trying to download one file and qB is downloading extra files and its very confusing. ![partfiles](https://cloud.githubusercontent.com/assets/16120768/12426713/b6c02892-bea0-11e5-9cd9-2d354ac33d2a.jpg) I am back to 3.2.5 and feel much more comfortable with no partfiles and clear watch folder. It will be very nice option also to do not delete the loaded files in any circumstances during multiple files torrent as Mtorrent client do.

deekerman commented

2026-02-21 16:55:24 -05:00

Author

Owner

@thalieht commented on GitHub (Dec 23, 2017):

Duplicate of #2659

Version 4.0.x is released. It uses libtorrent 1.1.x which puts the unwanted part files in the hidden file
".<torrent_hash>.parts" which is put in the same folder as the root folder(if any) of the torrent.
For the moment it's not possible to put that file somewhere else.

@thalieht commented on GitHub (Dec 23, 2017): Duplicate of #2659 Version 4.0.x is released. It uses libtorrent 1.1.x which puts the unwanted part files in the hidden file ".<torrent_hash>.parts" which is put in the same folder as the root folder(if any) of the torrent. For the moment it's not possible to put that file somewhere else.