I'll never update qBittorrent again until you implement a proper updater. #3501

Closed
opened 2026-02-21 16:48:38 -05:00 by deekerman · 18 comments
Owner

Originally created by @ddfssdfkofdsfighdfuigf on GitHub (Dec 9, 2015).

"There is a new version. Do you want to update?"

If you press "yes", it opens your browser, goes to a URL, and forces you to manually download an EXE which you then need to run and go through the entire installation process as if you didn't already have it installed. Every program that spits me in the face like this doesn't deserve to be updated.

You need to implement a proper updater, which does everything on its own and remembers all the settings. This needs to be the #1 priority for every software project that doesn't already implement it. I can't believe you expect people to update it so frequently in this idiotic way.

Originally created by @ddfssdfkofdsfighdfuigf on GitHub (Dec 9, 2015). "There is a new version. Do you want to update?" If you press "yes", it opens your browser, goes to a URL, and forces you to manually download an EXE which you then need to run and go through the entire installation process as if you didn't already have it installed. Every program that spits me in the face like this doesn't deserve to be updated. You need to implement a proper updater, which does everything on its own and remembers all the settings. This needs to be the #1 priority for every software project that doesn't already implement it. I can't believe you expect people to update it so frequently in this idiotic way.
Author
Owner

@ghost commented on GitHub (Dec 9, 2015):

While you are being an ass, I do agree with the general premise of this suggestion.

There should be a part in the installer where it reassures the user that the installer knows that there's already an installation of qBittorrent, and that it will perform an upgrade, and there is nothing to worry about and that no data will be lost.

Because if you think about it, for a new user it's quite confusing. qBittorrent tells them to update, so they say OK and download the installer, but it's the same installer as the regular installer?? They don't know if the installer will wipe their data with a fresh install or not.

@ghost commented on GitHub (Dec 9, 2015): While you are being an ass, I do agree with the general premise of this suggestion. There should be a part in the installer where it reassures the user that the installer knows that there's already an installation of qBittorrent, and that it will perform an upgrade, and there is nothing to worry about and that no data will be lost. Because if you think about it, for a new user it's quite confusing. qBittorrent tells them to update, so they say OK and download the installer, but it's the same installer as the regular installer?? They don't know if the installer will wipe their data with a fresh install or not.
Author
Owner

@yushiyangk commented on GitHub (Dec 9, 2015):

The message prompt definitely should say "download" or simply "get" instead of the current "update" to avoid the confusion.

This is of course moot if an automatic updater is already being implemented.

@yushiyangk commented on GitHub (Dec 9, 2015): The message prompt definitely should say "download" or simply "get" instead of the current "update" to avoid the confusion. This is of course moot if an automatic updater is already being implemented.
Author
Owner

@Askadar commented on GitHub (Dec 9, 2015):

It was really strange and frustrating to see it opens a new page in browser instead of updating itself. Either make proper updater or rename it to "download new update".

@Askadar commented on GitHub (Dec 9, 2015): It was really strange and frustrating to see it opens a new page in browser instead of updating itself. Either make proper updater or rename it to "download new update".
Author
Owner

@ghost commented on GitHub (Dec 9, 2015):

[Wishlist] it and we will see what will happen.

Still I cannot believe how some people can get that bitchy over such a little problem. I know we all are lazy as hell, but is downloading a new .exe for a proper installation (besides, all the torrents and settings in qBittorrent you have will still be there in the next version) really too much? The time you spent for writing the issue and all of the replies would have been worth downloading qB again and again.

And the tone of OP... well, c'mon. You can do better, and then the devs maybe will do something about it.

P.S.: They don't need to implement it because a few people do not like how it is right now.
P.S.S.: Why didn't you complain earlier about the problem and opened an issue?

@ghost commented on GitHub (Dec 9, 2015): [Wishlist] it and we will see what will happen. Still I cannot believe how some people can get that bitchy over such a little problem. I know we all are lazy as hell, but is downloading a new .exe for a proper installation (besides, all the torrents and settings in qBittorrent you have will still be there in the next version) really too much? The time you spent for writing the issue and all of the replies would have been worth downloading qB again and again. And the tone of OP... well, c'mon. You can do better, and then the devs maybe will do something about it. P.S.: They don't _need_ to implement it because a few people do not like how it is right now. P.S.S.: Why didn't you complain earlier about the problem and opened an issue?
Author
Owner

@chrishirst commented on GitHub (Dec 9, 2015):

@ddfssdfkofdsfighdfuigf

Got to ask, ... ... Why should anyone take notice of an apparent 'ultimatum' from someone who's user name is obviously created from random key strokes or is the result of a small kitten falling on to the keyboard?

@chrishirst commented on GitHub (Dec 9, 2015): @ddfssdfkofdsfighdfuigf Got to ask, ... ... Why should anyone take notice of an apparent 'ultimatum' from someone who's user name is obviously created from random key strokes or is the result of a small kitten falling on to the keyboard?
Author
Owner

@ddfssdfkofdsfighdfuigf commented on GitHub (Dec 9, 2015):

chrishirst: Why the hell would my nickname matter in the least for anything whatsoever?

@ddfssdfkofdsfighdfuigf commented on GitHub (Dec 9, 2015): chrishirst: Why the hell would my nickname matter in the least for anything whatsoever?
Author
Owner

@sledgehammer999 commented on GitHub (Dec 9, 2015):

Similar issue that I rejected 8 days ago: #4201
Honestly, I don't like "Chrome like update"/"silent updates"/"self updating" etc. And if you're too lazy to just download and run the installer (for which the program already launches the download URL) then I don't want to cater to your desires. I don't aim the client to be totally noob-friendly. Some geekiness is required.
As for some of the other comments see #4320.

@sledgehammer999 commented on GitHub (Dec 9, 2015): Similar issue that I rejected 8 days ago: #4201 Honestly, I don't like "Chrome like update"/"silent updates"/"self updating" etc. And if you're too lazy to just download and run the installer (for which the program already launches the download URL) then I don't want to cater to your desires. I don't aim the client to be totally noob-friendly. Some geekiness is required. As for some of the other comments see #4320.
Author
Owner

@chrishirst commented on GitHub (Dec 9, 2015):

Why the hell would my nickname matter in the least for anything whatsoever?

Because it suggests that you were not really interested enough to come up with a real user name (albeit an anonymous one) and merely hit a bunch of keys at random.

Most "discussion boards" operators would ban a 'name' like that as being a "Spam Bot" rather than a real person offering useful input.

@chrishirst commented on GitHub (Dec 9, 2015): > Why the hell would my nickname matter in the least for anything whatsoever? Because it suggests that you were not really interested enough to come up with a real user name (albeit an anonymous one) and merely hit a bunch of keys at random. Most "discussion boards" operators would ban a 'name' like that as being a "Spam Bot" rather than a real person offering useful input.
Author
Owner

@chrishirst commented on GitHub (Dec 9, 2015):

In addition to @sledgehammer999 comments, I would think that after the 'sneaky' Windows update 'silent' install of Windows 10 if you had "automatic" updates selected on Windows 7 or Windows 8, regardless of whether you had opted for "Get Windows 10" or not, most people would be against any kind of completely automatic updating.

@chrishirst commented on GitHub (Dec 9, 2015): In addition to @sledgehammer999 comments, I would think that after the 'sneaky' Windows update 'silent' install of Windows 10 if you had "automatic" updates selected on Windows 7 or Windows 8, regardless of whether you had opted for "Get Windows 10" or not, most people would be against any kind of completely automatic updating.
Author
Owner

@ddfssdfkofdsfighdfuigf commented on GitHub (Dec 10, 2015):

chrishirst: Then those people are absolute idiots, since it has nothing whatsoever to do with the discussion.

@ddfssdfkofdsfighdfuigf commented on GitHub (Dec 10, 2015): chrishirst: Then those people are absolute idiots, since it has nothing whatsoever to do with the discussion.
Author
Owner

@ddfssdfkofdsfighdfuigf commented on GitHub (Dec 10, 2015):

sledgehammer999: Thanks for showing how incredibly arrogant you are. I'll look for an alternative to qBittorrent.

@ddfssdfkofdsfighdfuigf commented on GitHub (Dec 10, 2015): sledgehammer999: Thanks for showing how incredibly arrogant you are. I'll look for an alternative to qBittorrent.
Author
Owner

@sledgehammer999 commented on GitHub (Dec 10, 2015):

LOL

@sledgehammer999 commented on GitHub (Dec 10, 2015): LOL
Author
Owner

@ddfssdfkofdsfighdfuigf commented on GitHub (Dec 10, 2015):

That last comment ("LOL") really makes me never want to use your software again.

@ddfssdfkofdsfighdfuigf commented on GitHub (Dec 10, 2015): That last comment ("LOL") _really_ makes me never want to use your software again.
Author
Owner

@ddfssdfkofdsfighdfuigf commented on GitHub (Dec 10, 2015):

chrishirst: 1. That doesn't make the slightest bit of sense. 2. It's not about being "silent" -- just automated.

The author of qBittorrent has clearly proven in this thread that he has absolutely no respect whatsoever for his users, and in fact enjoys wasting our time: "I don't want to cater to your desires."; "Some geekiness is required."

He's a rude, autistic asshole, to put things bluntly.

@ddfssdfkofdsfighdfuigf commented on GitHub (Dec 10, 2015): chrishirst: 1. That doesn't make the slightest bit of sense. 2. It's not about being "silent" -- just automated. The author of qBittorrent has clearly proven in this thread that he has absolutely no respect whatsoever for his users, and in fact enjoys wasting our time: "I don't want to cater to your desires."; "Some geekiness is required." He's a rude, autistic asshole, to put things bluntly.
Author
Owner

@sledgehammer999 commented on GitHub (Dec 10, 2015):

Thank you for providing us with some amusement. You won't be missed.

@sledgehammer999 commented on GitHub (Dec 10, 2015): Thank you for providing us with some amusement. You won't be missed.
Author
Owner

@RobertPaulson90 commented on GitHub (Dec 10, 2017):

I believe they make money off the download page, hence the lack of a built-in updater. Just install with chocolatey and future updates by doing choco upgrade qbittorrent

@RobertPaulson90 commented on GitHub (Dec 10, 2017): I believe they make money off the download page, hence the lack of a built-in updater. Just install with [chocolatey](https://github.com/chocolatey/choco) and future updates by doing `choco upgrade qbittorrent`
Author
Owner

@ctrlsam commented on GitHub (Oct 20, 2018):

Crazy something hasn't been implemented to this day from a thread 3 years old. I understand both views but surely they could've been more civilized and meet in the middle with a solution. For example, why don't they still prompt the user about an update (therefore not having it "silently" install) and then update. Downloading and installing an exe off the site is easy but it takes time and should be automated in my opinion. Maybe in another 3 years time 😄

@ctrlsam commented on GitHub (Oct 20, 2018): Crazy something hasn't been implemented to this day from a thread 3 years old. I understand both views but surely they could've been more civilized and meet in the middle with a solution. For example, why don't they still prompt the user about an update (therefore not having it "silently" install) and then update. Downloading and installing an exe off the site is easy but it takes time and should be automated in my opinion. Maybe in another 3 years time 😄
Author
Owner

@jurchiks commented on GitHub (Dec 24, 2018):

Same, I just received the prompt to update and I am surprised that it's almost 2019 and something like this still exists. Automatic updates for desktop apps has been a must-have for years. Not having this literally makes you lose users because nobody wants to do that manually every time when you could just pick a different software that does it silently in the background like every other app does. You have to get with the times.
I am now going to look for something else that has automatic updates.

@jurchiks commented on GitHub (Dec 24, 2018): Same, I just received the prompt to update and I am surprised that it's almost 2019 and something like this still exists. Automatic updates for desktop apps has been a must-have for years. Not having this literally makes you lose users because nobody wants to do that manually every time when you could just pick a different software that does it silently in the background like every other app does. You have to get with the times. I am now going to look for something else that has automatic updates.
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#3501
No description provided.