starred/qBittorrent

Fork 0

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

'Run on torrent finished' option in Windows not executing concatenated commands #17156

New issue

Open

opened 2026-02-22 03:42:11 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-22 03:42:11 -05:00

Owner

Originally created by @jay-ramani on GitHub (Sep 5, 2025).

qBittorrent & operating system versions

qBittorrent: 5.1.0 (64-bit)
Operating system: Windows 11 Pro (24H2) 26100.4946
Qt: 6.9.0
Libtorrent: 2.0.11.0

What is the problem?

Under Options -> Downloads -> Ron on torrent finished, only the first of concatenated DOS commands is executed.

Steps to reproduce

For example, if

"command 1" "%F" & "command 2" "%F" & "command 3"

(execute the second and subsequent commands regardless of the previous command's exit status)

are passed to this field, only command 1 is executed.

My current workaround is to gather these commands in a batch file, but shouldn't executing multiple commands be allowed?

Thanks in advance for the attention. Cheers.

Additional context

No response

Log(s) & preferences file(s)

qBittorrent.ini.txt

Originally created by @jay-ramani on GitHub (Sep 5, 2025). ### qBittorrent & operating system versions qBittorrent: 5.1.0 (64-bit) Operating system: Windows 11 Pro (24H2) 26100.4946 Qt: 6.9.0 Libtorrent: 2.0.11.0 ### What is the problem? Under Options -> Downloads -> Ron on torrent finished, only the first of concatenated DOS commands is executed. ### Steps to reproduce For example, if `"command 1" "%F" & "command 2" "%F" & "command 3"` (execute the second and subsequent commands regardless of the previous command's exit status) are passed to this field, only `command 1` is executed. My current workaround is to gather these commands in a batch file, but shouldn't executing multiple commands be allowed? Thanks in advance for the attention. Cheers. ### Additional context _No response_ ### Log(s) & preferences file(s) [qBittorrent.ini.txt](https://github.com/user-attachments/files/22177704/qBittorrent.ini.txt)

deekerman added the

Triggers

label

2026-02-22 03:42:11 -05:00

deekerman commented

2026-02-22 03:42:14 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Sep 5, 2025):

Please update to qBittorrent 5.1.2 & verify issue is still present.

https://sourceforge.net/projects/qbittorrent/files/qbittorrent-win32/qbittorrent-5.1.2/

@xavier2k6 commented on GitHub (Sep 5, 2025): Please update to qBittorrent 5.1.2 & verify issue is still present. https://sourceforge.net/projects/qbittorrent/files/qbittorrent-win32/qbittorrent-5.1.2/

deekerman commented

2026-02-22 03:42:15 -05:00

Author

Owner

@jay-ramani commented on GitHub (Sep 5, 2025):

Please update to qBittorrent 5.1.2 & verify issue is still present.

https://sourceforge.net/projects/qbittorrent/files/qbittorrent-win32/qbittorrent-5.1.2/

Didn't know 5.1.2 was released. Thanks for letting me know. When I check with Help -> Check for updates on v5.1.0, it says no updates available! Another bug?

Anyway, installed 5.1.2 from your Sourceforge link, and the issue still persists.

@jay-ramani commented on GitHub (Sep 5, 2025): > Please update to qBittorrent 5.1.2 & verify issue is still present. > > https://sourceforge.net/projects/qbittorrent/files/qbittorrent-win32/qbittorrent-5.1.2/ Didn't know 5.1.2 was released. Thanks for letting me know. When I check with Help -> Check for updates on v5.1.0, it says no updates available! Another bug? Anyway, installed 5.1.2 from your Sourceforge link, and the issue still persists.

deekerman commented

2026-02-22 03:42:15 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Sep 6, 2025):

Didn't know 5.1.2 was released. Thanks for letting me know. When I check with Help -> Check for updates on v5.1.0, it says no updates available! Another bug?

Not a bug per-se, issues with original web host.
An alternative fix was provided but only came in newer builds.

Anyway, installed 5.1.2 from your Sourceforge link, and the issue still persists.

Thanks for feedback.

@xavier2k6 commented on GitHub (Sep 6, 2025): >Didn't know 5.1.2 was released. Thanks for letting me know. When I check with Help -> Check for updates on v5.1.0, it says no updates available! Another bug? Not a bug per-se, issues with original web host. An alternative fix was provided but only came in newer builds. >Anyway, installed 5.1.2 from your Sourceforge link, and the issue still persists. Thanks for feedback.

deekerman commented

2026-02-22 03:42:15 -05:00

Author

Owner

@HanabishiRecca commented on GitHub (Sep 6, 2025):

Not a bug, that's simply not supported. Such operators are resolved by command line interpreter, qBittorrent obviously would not reimplement command line scripting capabilities.

So you need to pass your line into cmd /c or run a batch file.

@HanabishiRecca commented on GitHub (Sep 6, 2025): Not a bug, that's simply not supported. Such operators are resolved by command line interpreter, qBittorrent obviously would not reimplement command line scripting capabilities. So you need to pass your line into `cmd /c` or run a batch file.

deekerman commented

2026-02-22 03:42:15 -05:00

Author

Owner

@jay-ramani commented on GitHub (Sep 11, 2025):

Not a bug, that's simply not supported. Such operators are resolved by command line interpreter, qBittorrent obviously would not reimplement command line scripting capabilities.

So you need to pass your line into cmd /c or run a batch file.

Yup, as already mentioned in the original ticket description, I am running the commands in a batch file.

@jay-ramani commented on GitHub (Sep 11, 2025): > Not a bug, that's simply not supported. Such operators are resolved by command line interpreter, qBittorrent obviously would not reimplement command line scripting capabilities. > > So you need to pass your line into `cmd /c` or run a batch file. Yup, as already mentioned in the original ticket description, I am running the commands in a batch file.

deekerman commented

2026-02-22 03:42:15 -05:00

Author

Owner

@HanabishiRecca commented on GitHub (Sep 11, 2025):

Sure, but this issue should be closed as not a bug.

@HanabishiRecca commented on GitHub (Sep 11, 2025): Sure, but this issue should be closed as not a bug.