starred/qBittorrent

Fork 0

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

official 64 bit windows version needed #2475

New issue

Closed

opened 2026-02-21 16:14:25 -05:00 by deekerman · 30 comments

deekerman commented

2026-02-21 16:14:25 -05:00

Owner

Originally created by @ghost on GitHub (May 14, 2015).

Hi,

best bittorrent client ever .. great work!

... but since 11 years now 32bit is deprecated. even the cheapest notebooks now includes cpus with 64bit extensions. could you please provide a windows 64bit version? or maybe both 32bit and 64bit?

Originally created by @ghost on GitHub (May 14, 2015). Hi, best bittorrent client ever .. great work! ... but since 11 years now 32bit is deprecated. even the cheapest notebooks now includes cpus with 64bit extensions. could you please provide a windows 64bit version? or maybe both 32bit and 64bit?

deekerman closed this issue

2026-02-21 16:14:27 -05:00

deekerman commented

2026-02-21 16:14:29 -05:00

Author

Owner

@ngosang commented on GitHub (May 14, 2015):

👍

@ngosang commented on GitHub (May 14, 2015): :+1:

deekerman commented

2026-02-21 16:14:30 -05:00

Author

Owner

@chrishirst commented on GitHub (May 14, 2015):

32bit is deprecated.

By whom??

And you should read at the support forum occasionally.
There is this 64bit version which has been available since December 2012

@chrishirst commented on GitHub (May 14, 2015): > 32bit is deprecated. By whom?? And you should read at the [support forum](http://forum.qbittorrent.org) occasionally. There is [this 64bit version](https://qbforums.shiki.hu/index.php/topic,1645.0.html) which has been available since December 2012

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@ngosang commented on GitHub (May 14, 2015):

Clearly it's not discouraged but I think it would be good to have an official 64bit vesion. It is not important from the standpoint of performance but if it is as advertising. There are many people who believe it's better even is not.

@ngosang commented on GitHub (May 14, 2015): Clearly it's not discouraged but I think it would be good to have an official 64bit vesion. It is not important from the standpoint of performance but if it is as advertising. There are many people who believe it's better even is not.

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@chrishirst commented on GitHub (May 14, 2015):

The "Unofficial" status is simply because it is not the 'maintainer' of qbittorrent who compiles the 64bit Windows release and builds the installer.

@chrishirst commented on GitHub (May 14, 2015): The "Unofficial" status is simply because it is not the 'maintainer' of qbittorrent who compiles the 64bit Windows release and builds the installer.

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@ghost commented on GitHub (May 14, 2015):

It is deprecated by facts and reality : once again !!! now every cpu has 64bit instructions and if you have dozens of torrents the performance benefits are even measurable greater

@ghost commented on GitHub (May 14, 2015): It is deprecated by facts and reality : once again !!! now every cpu has 64bit instructions and if you have dozens of torrents the performance benefits are even measurable greater

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@birdie-github commented on GitHub (May 14, 2015):

Considering qBittorrent's CPU use there's almost zero gain from running a native 64bit version which will consume MORE RAM.

Please, close this bug report. Volunteers are free to compile their 64bit version of the application.

@birdie-github commented on GitHub (May 14, 2015): Considering qBittorrent's CPU use there's almost zero gain from running a native 64bit version which will consume MORE RAM. Please, close this bug report. Volunteers are free to compile their 64bit version of the application.

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@ngosang commented on GitHub (May 14, 2015):

Considering qBittorrent's CPU use there's almost zero gain from running a native 64bit version which will consume MORE RAM.

I agree, but...

It is not important from the standpoint of performance but if it is as advertising. There are many people who believe it's better even is not.

uTorrent don't have 64 bit version. I think some people will choose qBittorrent because of that.

@ngosang commented on GitHub (May 14, 2015): > Considering qBittorrent's CPU use there's almost zero gain from running a native 64bit version which will consume MORE RAM. I agree, but... > It is not important from the standpoint of performance but if it is as advertising. There are many people who believe it's better even is not. uTorrent don't have 64 bit version. I think some people will choose qBittorrent because of that.

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@Chocobo1 commented on GitHub (May 14, 2015):

If linux can have x64 builds, why not on Windows? Although real improvement is little to none...

@Chocobo1 commented on GitHub (May 14, 2015): If linux can have x64 builds, why not on Windows? Although real improvement is little to none...

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@ghost commented on GitHub (May 15, 2015):

if you use torrent checksum verification it would go a lot faster like ALL! i/o activity with a native 64bit version like all i/o activity and around 5 percent more ram usage is on todays systems only a trivial setback at worst

@ghost commented on GitHub (May 15, 2015): if you use torrent checksum verification it would go a lot faster like ALL! i/o activity with a native 64bit version like all i/o activity and around 5 percent more ram usage is on todays systems only a trivial setback at worst

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@chrishirst commented on GitHub (May 20, 2015):

if you use torrent checksum verification it would go a lot faster

It doesn't, at least, not to any noticeable degree. Maybe if you were rechecking tebibyte payloads with 8 or 16 mebibyte pieces it might be noticeable, but that is far from the norm currently.

@chrishirst commented on GitHub (May 20, 2015): > if you use torrent checksum verification it would go a lot faster It doesn't, at least, not to any noticeable degree. Maybe if you were rechecking tebibyte payloads with 8 or 16 mebibyte pieces it might be noticeable, but that is far from the norm currently.

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@birdie-github commented on GitHub (May 25, 2015):

Checksum calculation cannot be faster because on most modern PCs it's limited by IO throughput.

Of course if you're encoding into H.264/H.265 all day long, you might notice that those tasks perform a millisecond faster with a 64 bit qBittorrent but for 99.99% people out there there will be no difference at all.

@birdie-github commented on GitHub (May 25, 2015): Checksum calculation cannot be faster because on most modern PCs it's limited by IO throughput. Of course if you're encoding into H.264/H.265 all day long, you might notice that those tasks perform a millisecond faster with a 64 bit qBittorrent but for 99.99% people out there there will be no difference at all.

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@chrishirst commented on GitHub (May 26, 2015):

Teeeessss, I was being somewhat hypothetical rather than literal.

@chrishirst commented on GitHub (May 26, 2015): Teeeessss, I was being somewhat hypothetical rather than literal.

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@a178235 commented on GitHub (Jan 14, 2016):

A Windows 64-bit version would be nice. I see at least a 5% performance increase on any 64-bit application compared to its 32-bit version.

@a178235 commented on GitHub (Jan 14, 2016): A Windows 64-bit version would be nice. I see at least a 5% performance increase on any 64-bit application compared to its 32-bit version.

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@ScottRosenberg2 commented on GitHub (Jan 18, 2016):

64bit applications on Windows are held to reasonably strict standards for security by default, as well as having a substantially better ASLR implementation, preventing some risk of exploits.

With 32 bit, included DLL files are not ALSR, while 64 bit DLLs are always ASLR
This means that ASLR is rendered completely ineffective on 32 bit if the attacker knows in advance what DLLs are included in a given application.

As qbittorrent is a networked application, the few KB difference of ram, nor the performance should really be the relevant concern, it should be security.

@ScottRosenberg2 commented on GitHub (Jan 18, 2016): 64bit applications on Windows are held to reasonably strict standards for security by default, as well as having a substantially better ASLR implementation, preventing some risk of exploits. With 32 bit, included DLL files are not ALSR, while 64 bit DLLs are always ASLR This means that ASLR is rendered completely ineffective on 32 bit if the attacker knows in advance what DLLs are included in a given application. As qbittorrent is a networked application, the few KB difference of ram, nor the performance should really be the relevant concern, it should be security.

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@ngosang commented on GitHub (Jan 19, 2016):

We can have two releases.

@ngosang commented on GitHub (Jan 19, 2016): We can have two releases.

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@ScottRosenberg2 commented on GitHub (Jan 19, 2016):

The URL listed for the 64 bit unofficial version here does not work.

@ScottRosenberg2 commented on GitHub (Jan 19, 2016): The URL listed for the 64 bit unofficial version here does not work.

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@theTomaku commented on GitHub (Jan 19, 2016):

@moscato

https://github.com/Gelmir/qBittorrent/releases

@theTomaku commented on GitHub (Jan 19, 2016): @moscato https://github.com/Gelmir/qBittorrent/releases

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@ScottRosenberg2 commented on GitHub (Jan 19, 2016):

Thank you.

On Tue, Jan 19, 2016 at 5:03 PM, theTomaku notifications@github.com wrote:

@moscato https://github.com/moscato

https://github.com/Gelmir/qBittorrent/releases

—
Reply to this email directly or view it on GitHub
https://github.com/qbittorrent/qBittorrent/issues/3001#issuecomment-173016378
.

Scott Rosenberg
TheScottRosenberg@gmail.com

@ScottRosenberg2 commented on GitHub (Jan 19, 2016): Thank you. On Tue, Jan 19, 2016 at 5:03 PM, theTomaku notifications@github.com wrote: > @moscato https://github.com/moscato > > https://github.com/Gelmir/qBittorrent/releases > > — > Reply to this email directly or view it on GitHub > https://github.com/qbittorrent/qBittorrent/issues/3001#issuecomment-173016378 > . ## Scott Rosenberg TheScottRosenberg@gmail.com

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@bloodybunny commented on GitHub (Feb 13, 2016):

👍

@bloodybunny commented on GitHub (Feb 13, 2016): :+1:

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@SL-Gundam commented on GitHub (Feb 26, 2016):

I've been having issues with qbittorrent 32bit where it breaks the interface and crashes because of 2 GB memory usage

Installed 64bit version... hopefully that will clear this issue up

@SL-Gundam commented on GitHub (Feb 26, 2016): I've been having issues with qbittorrent 32bit where it breaks the interface and crashes because of 2 GB memory usage Installed 64bit version... hopefully that will clear this issue up

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@urherenow commented on GitHub (Nov 30, 2016):

Exactly. 64 bit should be DEFAULT. 32bit simply cannot handle the RAM requirements for large torrents, and since 16GB of ram is so common, who cares if a 64bit version would use more RAM? We NEED to be ABLE to use more RAM! My system crashes and restarts the desktop in less than 60 seconds with 3.3.7 because of this :(

@urherenow commented on GitHub (Nov 30, 2016): Exactly. 64 bit should be DEFAULT. 32bit simply cannot handle the RAM requirements for large torrents, and since 16GB of ram is so common, who cares if a 64bit version would use more RAM? We NEED to be ABLE to use more RAM! My system crashes and restarts the desktop in less than 60 seconds with 3.3.7 because of this :(

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@SL-Gundam commented on GitHub (Nov 30, 2016):

@urherenow for the moment you can get an unofficial 64bit version here: https://github.com/Gelmir/qBittorrent/releases

It fixed my issues with the 32bit version

@SL-Gundam commented on GitHub (Nov 30, 2016): @urherenow for the moment you can get an unofficial 64bit version here: https://github.com/Gelmir/qBittorrent/releases It fixed my issues with the 32bit version

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@urherenow commented on GitHub (Nov 30, 2016):

Tried that last night and still having an issue with a large torrent. Some IO issue in the latest release as well.Is there a nightly build anywhere?

@urherenow commented on GitHub (Nov 30, 2016): Tried that last night and still having an issue with a large torrent. Some IO issue in the latest release as well.Is there a nightly build anywhere?

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@lbalbalba commented on GitHub (Dec 1, 2016):

-- edit --
nevermind.

@lbalbalba commented on GitHub (Dec 1, 2016): -- edit -- nevermind.

deekerman commented

2026-02-21 16:14:31 -05:00

Author

Owner

@urherenow commented on GitHub (Dec 1, 2016):

Not of use at all.

@urherenow commented on GitHub (Dec 1, 2016): Not of use at all.

deekerman commented

2026-02-21 16:14:32 -05:00

Author

Owner

@urherenow commented on GitHub (Dec 1, 2016):

Although I figured out my problem. Apparently, qbtorrent can't handle pre-existing files with different hashes. It sees that it's wrong, starts to download the correct one for the .torrent (with the .ut! extension) but doesn't seem to be able to delete the old file and replace it with the new one. I had to delete several .zip files with matching .zip.ut! files, closed qbtorrent, re-opened, forced a recheck, then my torrent was able to complete. Not really related to 32 vs 64 bit at all, in my case.

@urherenow commented on GitHub (Dec 1, 2016): Although I figured out my problem. Apparently, qbtorrent can't handle pre-existing files with different hashes. It sees that it's wrong, starts to download the correct one for the .torrent (with the .ut! extension) but doesn't seem to be able to delete the old file and replace it with the new one. I had to delete several .zip files with matching .zip.ut! files, closed qbtorrent, re-opened, forced a recheck, then my torrent was able to complete. Not really related to 32 vs 64 bit at all, in my case.

deekerman commented

2026-02-21 16:14:32 -05:00

Author

Owner

@urherenow commented on GitHub (Dec 1, 2016):

Go back and re-read what you wrote. It's hard to be a smart ass when you're such a dumb ass. You wrote about the restrictions of 32bit being useful. SMH...

@urherenow commented on GitHub (Dec 1, 2016): Go back and re-read what you wrote. It's hard to be a smart ass when you're such a dumb ass. You wrote about the restrictions of 32bit being useful. SMH...

deekerman commented

2026-02-21 16:14:32 -05:00

Author

Owner

@SL-Gundam commented on GitHub (Dec 1, 2016):

Filesizes have no restriction in 32bit. Memory usage on the other hand do have restrictions in 32bit
~3.5gbyte is max memory on windows some other OSes max out at 4 gbyte

individual 32bit applications are limited to 2 or 3 gbyte of memory. Some 32bit programs on 64bit systems can access 4gbyte

My qbittorrent always broke when at some point its max memory usage hit the 2 gbyte mark. The 64bit version never exceeds 1.7 or 1.8 gbyte... Don't know why the 32bit needs more memory but the 64bit version fixed it

See this if you want to read more: https://en.wikipedia.org/wiki/3_GB_barrier

@SL-Gundam commented on GitHub (Dec 1, 2016): Filesizes have no restriction in 32bit. Memory usage on the other hand do have restrictions in 32bit ~3.5gbyte is max memory on windows some other OSes max out at 4 gbyte individual 32bit applications are limited to 2 or 3 gbyte of memory. Some 32bit programs on 64bit systems can access 4gbyte My qbittorrent always broke when at some point its max memory usage hit the 2 gbyte mark. The 64bit version never exceeds 1.7 or 1.8 gbyte... Don't know why the 32bit needs more memory but the 64bit version fixed it See this if you want to read more: https://en.wikipedia.org/wiki/3_GB_barrier

deekerman commented

2026-02-21 16:14:32 -05:00

Author

Owner

@Pablo-Diablo commented on GitHub (Dec 13, 2016):

I am seeding a lot of large torrents at 100Mbits and I get constant I/O errors on a 32 bit version. My HDD is fine before you ask, and absolutely no settings for cache do the trick. After a couple of these errors qBitTorrent just crashes.
64 bit version on the otrher hand works like a charm. It is like a breath of fresh air after I migrated from uTorrent.

@Gelmir could you please "fix" the new 3.3.8 version?

@Pablo-Diablo commented on GitHub (Dec 13, 2016): I am seeding a lot of large torrents at 100Mbits and I get constant I/O errors on a 32 bit version. My HDD is fine before you ask, and absolutely no settings for cache do the trick. After a couple of these errors qBitTorrent just crashes. 64 bit version on the otrher hand works like a charm. It is like a breath of fresh air after I migrated from uTorrent. @Gelmir could you please "fix" the new 3.3.8 version?

deekerman commented

2026-02-21 16:14:32 -05:00

Author

Owner

@zeule commented on GitHub (Jan 13, 2017):

64-bit installer is available.

@zeule commented on GitHub (Jan 13, 2017): 64-bit installer is available.

deekerman referenced this issue

2026-02-21 16:33:41 -05:00

Option to move deleted items to Recycled Bin #3058

deekerman referenced this issue

2026-02-21 17:05:32 -05:00