qBittorrent won't shut down

[Brodieman]

Please provide the following information

qBittorrent version and Operating System

Version 4.0.3 - Windows 7

What is the problem

qBittorrent won't shut down. GUI closes but stays running and listed in task manager. Need to manually end the process to start qBittorrent again

What is the expected behavior

Not running in task manager

[Ornlu]

This issue has been around for a couple years now.

It seems the only way for this behavior to not occur is to manually pause all your torrents before exiting qbittorrent/shutting down windows

[eurobank]

Qbit torrent takes a while to completely shut down (removed from task manager). But finally it does stop.

[Brodieman]

I have let it sit for hours (as the torrent finished over night) It never shuts down. Been using qBittorrent for years and it just started doing this

[eurobank]

Oh, not hours, i was talking about a minute or so.

[Brodieman]

I cannot find another torrent client I like either, I have looked

[DragonQ]

I also have this problem, with both qBittorrent and Deluge. Seems to be an issue with libtorrent. It's even worse in my case because not only will the application never shut down willingly, but I can't end the task or process in Task Manager either (whilst logged in as Administrator). I have to reboot whenever qBittorrent crashes or wants to update! :(

[nunomcm]

I have the same issue and also on Windows 7 (x64). Not sure if it helps but if I try to shutdown windows, it says that qBittorrent is blocking the shutdown and shows the message "Saving torrent progress...".

[Zentriert]

I have the same issue as @DragonQ - many times when I close qBittorent it stays running and even when I try to force end the process using Task Manager - it does not quit.

qBittorrent has just gotten buggier and buggier and I can barely use it now. It refuses to write data to my 8TB external HDD and then qBittorrent freezes up and requires me to restart to make it quit.

Why won't it write to my HDD? This is EXTREMELY FRUSTRATING.

[Hvalfisk]

I have the same issue, also Windows 7 (x64), version 4.0.3. After shutdown qBittorrent remains listed in task manager, with a single thread which uses up 100% of a single core, unable to be forced terminated. It prevents upgrading to a newer version, but it does not prevent running a new instance of qBittorrent. Only option is Windows restart.

[joder666]

I've been having the same problem with 4.x.x releases but in opensuse tumbleweed. Every time i close qbittorrent the process stays in the background without ending unless you kill it.

Here is a back-trace, not sure if it is helpful l though. I ran it through gdb close it and had to "ctrl+c" to end the process. won't-close.txt

[Tri125]

Present in 4.0.4 win7 64bit. Didn't occurred until I updated to the version that introduced the new GUI.

I have set my client to shutdown automatically when done downloading. When it's done, the GUI shutdown but the background process is still running. It will never close by itself and I won't be able to restart qBittorrent until I kill it.

If I kill it, restart the app, then manually stop the torrent, then shutting down the app will also kill the process.

[XaQute]

Yeah, same here. On a Win7 machine. So I asked myself the question: might it be that if any torrent is still alive, either for download or seeding (even if there's seeding is not actually taking place), that qbittorrent (qbt) is waiting until the download and upload has finished, since pausing the torrents seemed to do the trick too?

So, I experimented. I had set qbt to shut down my computer after completion of a torrent and after downloading the interface shut down. But not the computer did not and qbt was still running and visible in the tray. Though could not get it to open the interface by double clicking on the tray icon or from the Start menu.

After waiting for an hour, killed the process with task manager. Then started qbt. The interface opened and the seeding restarted. And after a few minutes I manually exited qbt. This seemed to go fine, since also qbt disappeared after 30 seconds from the tray. But qbt was still lurking in the background as a process, as the task manager revealed, and would not end. So, killed it again.

And restarted it. The set time limit on seeding of 2 minutes for one of the torrents that was active. Another seeding torrent was not actually seeding (upload speed is 0), but still had the status that it could. And the same result.

Then also set the upload limit on the other torrent. And... And yes, this does the trick. So, it seems the not-ending of qbt is related to either downloading or status of seeding of the torrent. Once the downloading or seeding status ends, qbt will exit.

[AsphyxNYC]

Well whatever the reason, QBT should shut down any traffic and stop properly. It seems each time I shut down or restart the computer I'm stuck waiting for it to check integrity a slew of torrents (including those that are completed and just seeding) when it really should only bother to check those still downloading.

[Immow]

I'm having shutdown problems as well, they started a while back. Using Windows 10 64 bit with qBittorent v4.04 on a SSD. It say's something along the lines of saving torrent progress.

[Carighan]

Curiously enough, these issues with preventing system shutdown happen even if there's no torrent in the program at all.

Win64, qbt 4.0.4

[AsphyxNYC]

For those having issues try using the 32 bit version not the 64 bit version. It seems to avoid this issue.

[Immow]

I know it's against the spirit of torrenting but I found a solution, in options at BitTorrent enable at Share and Ratio Limiting -> Seed torrents until their ratio reaches -> 0.01

Then as soon as torrent finishes it pauses the torrent and for me this solved system shutdown problem.

[sonnysavage]

I'm running the 64 bit v4.1.1 on Windows 10. Using the "Pause All" before "Exit" does not prevent the process from hanging.

[mb64h]

It amazes me why this problem is still around and apparently only getting worse! I have Windows 7 Professional. running qBittorrent v, 4.1.1 (64 bit) Any time I quit the program it leaves behind one or more qBittorrent processes . I cannot kill them in Task Manager. I cannot kill them using pskill from SysInternals. Even if I shut down the port they are using I still cannot kill them. I have to reboot my laptop and it takes a while to shut it down. It's a shame, I really like qB, but I will have to stop using it.

[Tri125]

Indeed. The problem is being completely ignored. I even posted on the subreddit to get help about it. They said that the problem doesn't exists on their machine and they banned me. I don't feel like this was handled professionally.

[zeule]

Closing as duplicate of #5097. Will be reopened if you manage to obtain a stacktrace showing a different problem. Until that I assume it to be a libtorrent (or boost) bug.

[KingZee]

This is still an active issue

[Cyer6]

It is still an issue and that's scary if you're not running a Socks5 connection to your VPN. qBitt 4.15 was still running in Task Manager after deleting the torrent and closing qBitt in Win10 for upwards of 15 minutes.

[Carighan]

Same here, I frequently (I would say ~20% o the time) get my Windows shutdown stopped because there's qbittorrent still open and it cannot be closed. It actually happens even if I close it manually beforehand.

[realtebo]

Same problem here, dev team, please, accept that is a knwown bug !!!!!!!!!

[jef]

Is this not actually a bug? It seems the common fix is the pause all the torrents then shut down. What's the current behavior or quitting qBittorent (macOS 10.14+)

[Carighan]

@hijxf : Thing is, this can happen even if there's no torrent in qbittorrent at all. If it was removed... 30 minutes earlier.

[jef]

@Carighan, that's interesting. I haven't had that behavior. I don't know what it would be then. Maybe some process exit code that isn't working as expected or some states that aren't getting determined for OK to close.

[eddieboy1953]

For what it's worth, I had the same problem with a zombie QB 4.2.5 process after exiting. By changing the compatibility settings in Windows 10 and running QB as a Windows 8 app the problem disappeared.

[Palladiawa]

I have the same issue in Debian Buster. Not the os's problem. It's apparently a bug of qb.