Make into Windows service #1776

Closed
opened 2026-02-21 15:50:50 -05:00 by deekerman · 11 comments
Owner

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.

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.
Author
Owner

@UgurGumushan commented on GitHub (Jun 29, 2016):

what are the potential benefits?

@UgurGumushan commented on GitHub (Jun 29, 2016): what are the potential benefits?
Author
Owner

@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:

  • notifications
  • the add torrent dialog box
  • the easiest way to get magnet links started
  • you could completely disable the webUI if you want
  • less resource usage than a web browser
  • depending on how interface is connected to service it could be connected to from native apps on mobile devices across the network (which would most likely be easier to use than the web interface - not that it's bad)
  • the web UI has other cavets, for example it's harder to use if I don't allow websites to disable context menu. Edit: also web UI doesn't show trackers in side bar.

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.

@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: * notifications * the add torrent dialog box * the easiest way to get magnet links started * you could completely disable the webUI if you want * less resource usage than a web browser * depending on how interface is connected to service it could be connected to from native apps on mobile devices across the network (which would most likely be easier to use than the web interface - not that it's bad) * the web UI has other cavets, for example it's harder to use if I don't allow websites to disable context menu. Edit: also web UI doesn't show trackers in side bar. 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.
Author
Owner

@TheBestPessimist commented on GitHub (Apr 18, 2017):

+1 for this.

@TheBestPessimist commented on GitHub (Apr 18, 2017): +1 for this.
Author
Owner

@jimmy-mc commented on GitHub (Jan 4, 2018):

Definitely.

@jimmy-mc commented on GitHub (Jan 4, 2018): Definitely.
Author
Owner

@woookash commented on GitHub (Nov 16, 2019):

+1 - it would allow it to run on a download box when it restarts for example

@woookash commented on GitHub (Nov 16, 2019): +1 - it would allow it to run on a download box when it restarts for example
Author
Owner

@talraveh1 commented on GitHub (May 15, 2024):

+1

@talraveh1 commented on GitHub (May 15, 2024): +1
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:

  1. Please select/click the 👍 &/orreactions 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.)
@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.)**
Author
Owner

@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? 🙏🏻

@nchevsky commented on GitHub (May 23, 2025): @xavier2k6 Please note that #164, where you left an [equivalent comment](https://github.com/qbittorrent/qBittorrent/issues/164#issuecomment-2905453525), has discussion locked—which blocks not only comments, but also reactions. Could you please unlock it? 🙏🏻
Author
Owner

@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:

nchevsky left a comment (qbittorrent/qBittorrent#2070)
https://github.com/qbittorrent/qBittorrent/issues/2070#issuecomment-2905786803

@xavier2k6 https://github.com/xavier2k6 Please note that #164
https://github.com/qbittorrent/qBittorrent/issues/164, where you left
an equivalent comment
https://github.com/qbittorrent/qBittorrent/issues/164#issuecomment-2905453525,
has discussion locked—which blocks not only comments, but also reactions.
Could you please unlock it? 🙏🏻


Reply to this email directly, view it on GitHub
https://github.com/qbittorrent/qBittorrent/issues/2070#issuecomment-2905786803,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEVNBXAY5OE6C4GNPIJZEWD276DE3AVCNFSM6AAAAAB5ZN4IB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMBVG44DMOBQGM
.
You are receiving this because you commented.Message ID:
@.***>

@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: > *nchevsky* left a comment (qbittorrent/qBittorrent#2070) > <https://github.com/qbittorrent/qBittorrent/issues/2070#issuecomment-2905786803> > > @xavier2k6 <https://github.com/xavier2k6> Please note that #164 > <https://github.com/qbittorrent/qBittorrent/issues/164>, where you left > an equivalent comment > <https://github.com/qbittorrent/qBittorrent/issues/164#issuecomment-2905453525>, > has discussion locked—which blocks not only comments, but also reactions. > Could you please unlock it? 🙏🏻 > > — > Reply to this email directly, view it on GitHub > <https://github.com/qbittorrent/qBittorrent/issues/2070#issuecomment-2905786803>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AEVNBXAY5OE6C4GNPIJZEWD276DE3AVCNFSM6AAAAAB5ZN4IB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMBVG44DMOBQGM> > . > You are receiving this because you commented.Message ID: > ***@***.***> >
Author
Owner

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

@nchevsky That ticket was brought up before & i'll review.

@xavier2k6 commented on GitHub (May 23, 2025): @nchevsky That ticket was brought up before & i'll review.
Author
Owner

@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.

@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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/qBittorrent#1776
No description provided.