mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Make into Windows service #1776
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#1776
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dividium on GitHub (Oct 22, 2014).
it'd be nice to see compatibility as a Windows service. I realize I can accomplish this via creating my own service of the Microsoft anyservice tool but it does really rather depend on all UI elements being accessible via the web UI and built in functionality would be nice.
Also the service could be managed (adding torrent, deleting torrent, etc) via a separate UI process and/or Web UI.
@UgurGumushan commented on GitHub (Jun 29, 2016):
what are the potential benefits?
@PaulBags commented on GitHub (Dec 5, 2016):
"what are the potential benefits?"
Connecting a user mode interface to a service (vs web UI) would give:
Plus: The benefits of running as a service, the main reason I'm looking at it is running at start up with no user logged in. Buuut unless I can get qt running as a service as me at startup, and have the interface ready to go in the tray when I log in, I think it's going to be too annoying.
@TheBestPessimist commented on GitHub (Apr 18, 2017):
+1 for this.
@jimmy-mc commented on GitHub (Jan 4, 2018):
Definitely.
@woookash commented on GitHub (Nov 16, 2019):
+1 - it would allow it to run on a download box when it restarts for example
@talraveh1 commented on GitHub (May 15, 2024):
+1
@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 ❤
reactionsin 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:
DO NOT:
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)
@nchevsky commented on GitHub (May 23, 2025):
@xavier2k6 Please note that #164, where you left an equivalent comment, has discussion locked—which blocks not only comments, but also reactions. Could you please unlock it? 🙏🏻
@PaulBags commented on GitHub (May 23, 2025):
So you thought spamming every single feature request, including ones that
have had no comments for a year, was the way to prevent spam? -_-.
On Sat, 24 May 2025, 08:53 Nick Chevsky, @.***> wrote:
@xavier2k6 commented on GitHub (May 23, 2025):
@nchevsky That ticket was brought up before & i'll review.
@xavier2k6 commented on GitHub (May 23, 2025):
@PaulBags With all the amount of tickets open, we are trying to get a better handle on things & using the reactions as a metric will help us review/determine which may be a priority request over others....all the plus 1 & complaining/abusive comments doesn't help anyone.
there are also the fact that some users open duplicates or are using too old versions where the feature they're requesting has already been implemented.
There are 1,569 feature request open - that even now are still duplicates of others/already implemented.
The notification, will be a once off per feature request.