starred/qBittorrent

Fork 0

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

Upgrade Problem #5936

New issue

Closed

opened 2026-02-21 18:08:07 -05:00 by deekerman · 14 comments

deekerman commented

2026-02-21 18:08:07 -05:00

Owner

Originally created by @Isengard97 on GitHub (Aug 17, 2017).

Please provide the following information

qBittorrent version and Operating System: 3.3.14-3.3.15, Windows 10

What is the problem: Upgrade problem

What is the expected behavior:

Hello everyone, I have a problem with qBittorrent.
I had v 3.3.14 and when v 3.3.15 came out I upgraded but after few days when I open the program (I usually open when Windows starts), appears the v 3.3.14 again instead of v 3.3.15. I have try to reinstall 2 times but it doesn't work, what can I do?

Originally created by @Isengard97 on GitHub (Aug 17, 2017). **Please provide the following information** ### qBittorrent version and Operating System: 3.3.14-3.3.15, Windows 10 ### What is the problem: Upgrade problem ### What is the expected behavior: Hello everyone, I have a problem with qBittorrent. I had v 3.3.14 and when v 3.3.15 came out I upgraded but after few days when I open the program (I usually open when Windows starts), appears the v 3.3.14 again instead of v 3.3.15. I have try to reinstall 2 times but it doesn't work, what can I do?

deekerman closed this issue

2026-02-21 18:08:09 -05:00

deekerman commented

2026-02-21 18:08:13 -05:00

Author

Owner

@thalieht commented on GitHub (Aug 17, 2017):

Try uninstalling first.

@thalieht commented on GitHub (Aug 17, 2017): Try uninstalling first.

deekerman commented

2026-02-21 18:08:13 -05:00

Author

Owner

@Isengard97 commented on GitHub (Aug 18, 2017):

Yep. I will try again.
(Fo me "reinstalling" means uninstall first then install again)

@Isengard97 commented on GitHub (Aug 18, 2017): Yep. I will try again. (Fo me "reinstalling" means uninstall first then install again)

deekerman commented

2026-02-21 18:08:13 -05:00

Author

Owner

@Isengard97 commented on GitHub (Aug 21, 2017):

Hi. I have tried but this problem appears again. On 08/18/2017 I have uninstalled v 3.3.14 and installed v.3.3.15 but from yesterday when I open program it says v.3.3.14

@Isengard97 commented on GitHub (Aug 21, 2017): Hi. I have tried but this problem appears again. On 08/18/2017 I have uninstalled v 3.3.14 and installed v.3.3.15 but from yesterday when I open program it says v.3.3.14

deekerman commented

2026-02-21 18:08:13 -05:00

Author

Owner

@pjc123 commented on GitHub (Aug 29, 2017):

Same problem on 3 separate computers, different hardware but same OS.

qBittorrent version: 3.3.14 (64bit)
Operating System: Windows 10 Pro 64 Bit, Version 1703, OS Build 15063.540, Current OS + Current Drivers
What is the problem: Qbittorrent will not upgrade, or program displays wrong version number and thinks it needs to be upgraded, or I don't know

What is the expected behavior:
Trying to upgrade from 3.3.14 to 3.3.15.

Error message during upgrade process:

First a message comes up that a previous version was detected and it will be uninstalled without deleting user settings. So select OK, Next to continue, Accept the License, Next, Choose components, next, Choose install location, Install
A message then comes up
error opening file for writing:
c:\programfiles(x86)\qbittorrent\qbittorrent.exe
click abort to stop installation, retry to try again, ignore to skip... etc.
I have tried "retry". Same error.
I have tried "skip". The program completes, but the old version is still there.
I have tried "abort". Interesting.....It removed the program completely! Gone from the Control panel.
Tried to install 3.3.15. Same error again and I am back at 3.3.14 according to the help menu and main program screen, but version 3.3.15 in the Control Panel.
So I click on Help > Check for updates. A new version is available. Do you want to download 3.3.15.
I give up.

@pjc123 commented on GitHub (Aug 29, 2017): Same problem on 3 separate computers, different hardware but same OS. qBittorrent version: 3.3.14 (64bit) Operating System: Windows 10 Pro 64 Bit, Version 1703, OS Build 15063.540, Current OS + Current Drivers What is the problem: Qbittorrent will not upgrade, or program displays wrong version number and thinks it needs to be upgraded, or I don't know What is the expected behavior: Trying to upgrade from 3.3.14 to 3.3.15. Error message during upgrade process: 1) First a message comes up that a previous version was detected and it will be uninstalled without deleting user settings. So select OK, Next to continue, Accept the License, Next, Choose components, next, Choose install location, Install 2) A message then comes up error opening file for writing: c:\programfiles(x86)\qbittorrent\qbittorrent.exe click abort to stop installation, retry to try again, ignore to skip... etc. 1) I have tried "retry". Same error. 2) I have tried "skip". The program completes, but the old version is still there. 3) I have tried "abort". Interesting.....It removed the program completely! Gone from the Control panel. 4) Tried to install 3.3.15. Same error again and I am back at 3.3.14 according to the help menu and main program screen, but version 3.3.15 in the Control Panel. 5) So I click on Help > Check for updates. A new version is available. Do you want to download 3.3.15. 6) I give up.

deekerman commented

2026-02-21 18:08:13 -05:00

Author

Owner

@Isengard97 commented on GitHub (Aug 30, 2017):

Oh. It seems that I'm not the only one, lol. I'm giving up to. I have reinstalled 3.3.15 for six times!

I'm just waiting v 3.3.16 or later

@Isengard97 commented on GitHub (Aug 30, 2017): Oh. It seems that I'm not the only one, lol. I'm giving up to. I have reinstalled 3.3.15 for six times! I'm just waiting v 3.3.16 or later

deekerman commented

2026-02-21 18:08:14 -05:00

Author

Owner

@thalieht commented on GitHub (Aug 30, 2017):

A message then comes up
error opening file for writing:
c:\programfiles(x86)\qbittorrent\qbittorrent.exe
click abort to stop installation, retry to try again, ignore to skip... etc.

qbittorrent process was probably still running (known to happen in certain situations with libtorrent 1.0.x)

But then again this has been an issue for too long and personally, i only recently started seeing such strange reports when x64 build appeared and people started switching to it from x86.

@thalieht commented on GitHub (Aug 30, 2017): >A message then comes up error opening file for writing: c:\programfiles(x86)\qbittorrent\qbittorrent.exe click abort to stop installation, retry to try again, ignore to skip... etc. qbittorrent process was probably still running (known to happen in certain situations with libtorrent 1.0.x) But then again this has been an issue for too long and personally, i only recently started seeing such strange reports when x64 build appeared and people started switching to it from x86.

deekerman commented

2026-02-21 18:08:14 -05:00

Author

Owner

@pjc123 commented on GitHub (Aug 30, 2017):

qbittorrent process was probably still running

What is the name of the process? I can try stopping it in task manager and retry.

@pjc123 commented on GitHub (Aug 30, 2017): qbittorrent process was probably still running What is the name of the process? I can try stopping it in task manager and retry.

deekerman commented

2026-02-21 18:08:14 -05:00

Author

Owner

@Isengard97 commented on GitHub (Aug 30, 2017):

Hm but during upgrading, the program ask us to close the client or not?

@Isengard97 commented on GitHub (Aug 30, 2017): Hm but during upgrading, the program ask us to close the client or not?

deekerman commented

2026-02-21 18:08:14 -05:00

Author

Owner

@thalieht commented on GitHub (Aug 30, 2017):

What is the name of the process?

qbittorrent.exe

Hm but during upgrading, the program ask us to close the client or not?

As i said, i might be wrong about the process thing because i only recently started seeing such reports.

@thalieht commented on GitHub (Aug 30, 2017): >What is the name of the process? qbittorrent.exe >Hm but during upgrading, the program ask us to close the client or not? As i said, i might be wrong about the process thing because i only recently started seeing such reports.

deekerman commented

2026-02-21 18:08:14 -05:00

Author

Owner

@pjc123 commented on GitHub (Aug 30, 2017):

I am thinking I could kill the process before I hit retry, or even before I do the update.

@pjc123 commented on GitHub (Aug 30, 2017): I am thinking I could kill the process before I hit retry, or even before I do the update.

deekerman commented

2026-02-21 18:08:14 -05:00

Author

Owner

@pjc123 commented on GitHub (Aug 30, 2017):

I will see after I am done with something else.

@pjc123 commented on GitHub (Aug 30, 2017): I will see after I am done with something else.

deekerman commented

2026-02-21 18:08:14 -05:00

Author

Owner

@pjc123 commented on GitHub (Aug 30, 2017):

I couldn't find qbittorrent running anywhere. However on all my PCs I uninstalled and reinstalled (running as administrator) one more time and no error this time and both the program and control panel match as 3.3.15. Why, haven't got a clue...maybe all the installs, reinstalls, reboots, etc the other day.

@pjc123 commented on GitHub (Aug 30, 2017): I couldn't find qbittorrent running anywhere. However on all my PCs I uninstalled and reinstalled (running as administrator) one more time and no error this time and both the program and control panel match as 3.3.15. Why, haven't got a clue...maybe all the installs, reinstalls, reboots, etc the other day.

deekerman commented

2026-02-21 18:08:14 -05:00

Author

Owner

@Isengard97 commented on GitHub (Sep 12, 2017):

Hello again guys. I have the same problem with new upgrade. I take a Screenshot:

Idk what can I do anymore

@Isengard97 commented on GitHub (Sep 12, 2017): Hello again guys. I have the same problem with new upgrade. I take a Screenshot: ![image](https://user-images.githubusercontent.com/31104857/30333861-42174318-97de-11e7-8dc1-b92023e8701b.png) Idk what can I do anymore

deekerman commented

2026-02-21 18:08:14 -05:00

Author

Owner

@thalieht commented on GitHub (Sep 25, 2018):

Should be fixed by now.

@thalieht commented on GitHub (Sep 25, 2018): Should be fixed by now.