Add an (advanced) option to disable file hooks. #3816

New issue

Open

opened 2026-02-21 16:58:47 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-21 16:58:47 -05:00

Owner

Originally created by @Misiek304 on GitHub (Jan 23, 2016).

In previous version (worked for me in 3.2.5) I was able to delete files of the torrent that was currently actively seeding or in seeding status. This way I was able to delete files without disable seeding for them in qBittorrent first. Now I can't. On Windows I get a message that "the file is in use by another program". This is very annoying because I use a network drive and I don't have "real" access to the files.

What I'm looking for is the option to disable file hooks for torrent files that are seeding or actively seeding so I could delete them without an issue. The expected behavior would be to change torrent status from seeding to "finished" or "paused" like it was done in previous versions of qBittorrent.

The idea behind this is because I download lots of different torrents for example TV Shows that are quickly "dying" and I delete those files right after I watch them. With this "file in use" problem I have to search for every torrent I want to delete and disable seeding. I understand this may be not liked by everyone so I'm suggesting implementing this as "advanced feature".

The alternative solution for this problem would be to stop seeding right after I download the torrent and I don't want to do that because sometimes I keep those files for months or years.

Originally created by @Misiek304 on GitHub (Jan 23, 2016). In previous version (worked for me in 3.2.5) I was able to delete files of the torrent that was currently actively seeding or in seeding status. This way I was able to delete files without disable seeding for them in qBittorrent first. Now I can't. On Windows I get a message that "the file is in use by another program". This is very annoying because I use a network drive and I don't have "real" access to the files. What I'm looking for is the option to disable file hooks for torrent files that are seeding or actively seeding so I could delete them without an issue. The expected behavior would be to change torrent status from seeding to "finished" or "paused" like it was done in previous versions of qBittorrent. The idea behind this is because I download lots of different torrents for example TV Shows that are quickly "dying" and I delete those files right after I watch them. With this "file in use" problem I have to search for every torrent I want to delete and disable seeding. I understand this may be not liked by everyone so I'm suggesting implementing this as "advanced feature". The alternative solution for this problem would be to stop seeding right after I download the torrent and I don't want to do that because sometimes I keep those files for months or years.

deekerman added the

Feature request

label

2026-02-21 16:58:47 -05:00

deekerman commented

2026-02-21 16:58:49 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 23, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 23, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**

deekerman referenced this issue

2026-02-21 17:01:42 -05:00

Download in sequential order misses first part #3905

deekerman referenced this issue

2026-02-21 17:09:41 -05:00

New download more pieces in "Download first and last pieces first" feature broke "Download in sequential order" #4145