Qbittorrent 4.4; file transfer problem when defult torrent file change #12825

New issue

Closed

opened 2026-02-21 23:13:07 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-21 23:13:07 -05:00

Owner

Originally created by @marko090591 on GitHub (Jan 14, 2022).

qBittorrent & operating system versions

Qbittorrent 4.4 final
Windows 10 (10.0.1xxxx)

What is the problem?

Hello

When changing the defult path from g:/ to f:/ in options, some torrents which have automatic menagment turned on are also transfered to new location. This option (switch to manual mode when defult torrent save path change) is turned on in the settings of the programe qbittorrent.
In previous version, when the option of switch to manual mode, when torrent path changed torrents whih had atomatic menagment turned on, files were not transfered to new location.

Steps to reproduce

See video bellow:

https://drive.google.com/file/d/1-AwCN2BvIE5AW_Yz8LepbzBwD35y6Ofn/view?usp=drivesdk

Additional context

No response

Log(s) & preferences file(s)

No response

Originally created by @marko090591 on GitHub (Jan 14, 2022). ### qBittorrent & operating system versions Qbittorrent 4.4 final Windows 10 (10.0.1xxxx) ### What is the problem? Hello When changing the defult path from g:/ to f:/ in options, some torrents which have automatic menagment turned on are also transfered to new location. This option (switch to manual mode when defult torrent save path change) is turned on in the settings of the programe qbittorrent. In previous version, when the option of switch to manual mode, when torrent path changed torrents whih had atomatic menagment turned on, files were not transfered to new location. ### Steps to reproduce See video bellow: https://drive.google.com/file/d/1-AwCN2BvIE5AW_Yz8LepbzBwD35y6Ofn/view?usp=drivesdk ### Additional context _No response_ ### Log(s) & preferences file(s) _No response_

deekerman closed this issue

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

deekerman commented

2026-02-21 23:13:14 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Mar 13, 2025):

This ticket has been closed due to being "out-of-date", and thus either most likely resolved in recent versions or no longer applicable.
If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.
A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.
Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.
Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.
Thank you for your contribution(s).

@xavier2k6 commented on GitHub (Mar 13, 2025): * This ticket has been closed due to being "out-of-date", and thus either most likely resolved in recent versions or no longer applicable. * If you experience the reported problem or similar in the **latest** version, please open a new issue report with the requested information in the issue template. * A new issue report with relevant updated data gathered from the **latest** version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression. Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar. Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression. * Thank you for your contribution(s).