Magnet REG_SZ CitrioDOC.FVBLGPJK6BS5NI3EMFOUZGPMJIĢ. Note: as an example, this was the result for me: HKEY_CURRENT_USER\Software\Clients\StartMenuInternet\Citrio.FVBLGPJK6BS5NI3EMFOUZGPMJI\Capabilities\URLAssociations Okay, so here's how you should proceed:ġ.Open the command prompt, type the following: reg query HKCU\Software\Clients /v magnet /s tough luck.Īfter some testing, I came up with an easy way to test if you have this issue, I say this because the symptom that I complain about in this post can have multiple reasons, but unfortunately all discussion I found online had different reasons and solutions behind them, yet none worked for me. Typically this association would be carried out at the level of HKEY_CLASSES_ROOT, but in this case the associations were added in HKEY_CURRENT_USER\Software\Clients\StartMenuInternet the approach is indeed very similar but the issue is that this one overrides whatever is in HKCR, meaning that if you do not know to search for it. The thing is that not many apps use (yet) this URL association approach, but among those which use they seem to be implemented sloppily enough to leave a broken key behind that fucks you over once you uninstall it.Ĭase in point, last year I installed a web browser called Citrio, this web browser will not only claim association to various web filetypes (url, htm, html, etc.), but also URL protocols (mailto, magnet, etc.). Some software, namely web browsers like Torch or Citrio, use a (redundant, but prioritized) form of URL association new to Windows 10 (maybe 8.1 too?). NOTE: Comments on how to install Linux are unwarranted, take your arrogance elsewhere (someone did already, actually).Īfter some digging, it was quite simple to solve but a pain to track down. My guess is that at some point in time I installed some dodgy app that created the new magnet handler entry and when uninstalled left Windows "in charge" of what can or cannot handle the magnet protocol.ĮDIT: After a few terabytes moved around and a backup restored to a VM, I have finally pinpointed what creates this issue: The above example shows an entry for MAGNET protocol, which in the case of most people who have stuff working properly shouldn't be in that list because it's a new Windows functionality which connects with their Store's AppX handler support. Not to mention that the support in browsers for the URI has also been eroded and doesn't work in some either. ![]() I'm using uTorrent v2.2, but I've read about people having this issue with current builds of Transmission and qBitorrent.Īnyway, the bigger issue is that I cannot find information on how to work around this restriction that Microsoft created and cannot associate magnets with my client any longer. ![]() Windows seems to refuse the association of any software with MAGNET URIs, instead suggesting that you download one from their store. ![]() Windows 10 has deprecated default associations from HKEY_CLASSES_ROOT, especially for protocols like MAGNET.
0 Comments
Leave a Reply. |