New: Gopherus (Feb 14, 2023), Platform 24.1 (Feb 13, 2023)
450+ real apps (49GB), 1 billion downloads, Please donate.
Hi, I'm having some trouble with qBittorrent.
If I start the program using the launcher "qBittorrentPortable.exe" and later try to open a torrent file with it, it starts a new process instead of opening it in the existing one.
However if try to launch "qBittorrentPortable.exe" by opening torrent file it seems to work fine.
I found this topic and I can see that the fix is already applied but it doesn't seem to work for me.
Is there any way to fix or circumvent this problem?
It's working here with qBittorrent Portable 3.1.12 Rev 2 if I do File - Open and select a torrent file or if I drag a torrent file onto the UI and drop it. How are you trying to open it, what OS, what's the full path, how did you launch qBittorrent Portable?
I'm sorry I should have stated that in my main post.
I'm using Windows 8.1 x64, latest version of qBittorent downloaded with the launcher.
I launch it by double-clicking "qBittorrentPortable.exe".
I'm opening the torrent file it by downloading it with firefox and selecting "Open with". I added qBittorrent by browsing and selecting "qBittorrentPortable.exe".
The full path is "G:\Loading\qBittorrentPortable\qBittorrentPortable.exe"
Is this not supported/possible with qBittorrent? This has always worked fine for me with uTorrentPortable.
qBittorrent's method of determining a running instance is entirely based on the TEMP directory (which is probably the most absurd method I've seen thusfar). Firefox Portable, like many of our apps, uses a contained TEMP directory, so it would have a different TEMP and the instance of qBittorrent being spawned would think it was a new instance.
Basically, it's an issue with qBittorrent itself as this would also affect the local version being launched from another app with its own TEMP defined. For right now, you can save your torrent files and open them by dragging them to the launcher manually, dragging them to the running app, or using File - Open. I have an idea for a possible workaround in an upcoming release, but I'll need to figure out if it works right first.
Ohh I see.
I've tried to migrate to qBittorent a couple of times now and I've always hit this problem, at least now I know why.
Thank you very much for your answers and you quick replies.
Visit the Community page
Join our forums