qBittorrent official forums

I just switched to a new computer (Intel 12th gen i5, 32gb ddr5, nvme ssd etc) running Windows 11 Pro, I followed instructions to migrate torrents from my old computer to the new one and installed QBittorrent V4.45 x64. Everything is working as it normally would with the exception that if I exit QBittorent the program window closes but if I attempt to then shut the computer down it gets stuck saying that "QBittorrent is stopping" but it never properly exists (and it shows in taskmgr that it's still seems to be running) and when I left the computer in that state for several hours it never shut down as QBittorent never exited. I finally had to pull out the network cable which finally caused QBittorent to exit allowing the computer to shut down.

Doing a Google search I found a number of people complaining about this but they were a number of years old and mostly seemed to be using Windows 7 or 8 / 8.1 and even a couple using Windows 10. So what can I do to keep QBittorrent from getting stuck in this state?

Interesting, I am also on Win11 Pro running 4.4.5 at the moment and have no such issues at all.
Do you see anything in Event Viewer? Are you running a lot of torrents?

I'm pretty sure that the version on my old computer was 4.4.5 but probably x32 but it was Windows 10 Pro and I didn't have this problem. I'm looking at both the system and application logs (this is a brand new build and brand new Windows 11 install) and I do see some assorted errors but being new to Windows 11 I'm not sure if these are errors that like Windows 10 frequently show up but mean nothing. If you want to look at my system and application logs, I can upload them to my Google drive and post links just let me know. At the time it was seeding some few torrents probably 5 or less as well as downloading maybe 2-3 others max.

Right now I tried exiting QBittorent and this time it did in fact stop when the program window closed and did not get stuck in the state that I'd described. So I'm not sure why that happened or why it's now not doing that since nothing has changed on the computer since that incident.