Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Not able to re-associate with magnet links on windows 10 latest version. #11524
Please provide the following information
qBittorrent version and Operating System
v126.96.36.199 / Windows 10
If on linux, libtorrent-rasterbar and Qt version
What is the problem
Not able to re-associate with magnet links after trying to use instant.io for a web torrent, checking the associate with magnet links box and applying doesn't change and windows doesn't seem to think qbit is capable of handling magnet urls (thanks windows)
What is the expected behavior
Being able to associate qbit with magnet links
Steps to reproduce
Have qbit as default for magnet links, try to use instant.io for web torrenting then try to switch back to using qbit for magnet links.
Extra info(if any)
Seems new way is preferably so you can't redefine default applications using the old one.
I twice opened PRs implementing its support, but they died of old age, never being properly reviewed and approved. So if you still decide to evolve qBittorrent a bit, I can share my experience with anyone who wants to finish it.
The registry modifications aren't that bad. We already do something really close to that.
@glassez Am I reading this correct?
@pullup If I understand correctly you used instant.io via a web browser. And the web browser prompted you about making instant.io the default handler for magnets (which I assume you accepted). Try to search in your browser's preferences for Applications associations per filetype. And see what it allows for magnet uris. For example, in Firefox this is Found in the
In my previous work I changed it to be compatible with both old and new methods. Really if you register handlers according to Default Programs specifications you can use them with old method.
Yes. Moreover, it doesn't show this dialog in Windows 8+ but just message about where you can change default handlers.
Additionally Windows 10 shows you an appropriate dialog when you open some file for which handlers have been changed (e.g. the new one is added).
The common thing in all this is that we need to register correct handlers (according to Default Programs specifications).
Any workaround until this gets fixed?