Qbittorrent's auto-installed plugin tried to hijack Computer proxy and shutdown

Windows specific questions, problems.
Post Reply
Raiden

Qbittorrent's auto-installed plugin tried to hijack Computer proxy and shutdown

Post by Raiden »

What on earth is going on? Never before have I experienced such a terrible thing with Qbittorrent until today. The entire program simply shutdown/exited itself when I turned it on (it had an unfinished torrent that had been up from past days). I had to disable network and find out what was preventing it. Turned out I got a message there is a new "Jackett" plugin that had been installed by default and supposedly displaying a connection error. So I disabled network connection, turned on QBitTorrent and disabled the plugin and then turned on the network. Yet it still got shutdown as soon as I reloaded the torrent even tho this time I had disabled the supposed cause of error ("Jackett" plugin.

Just to make sure I reinstalled the entire qbittorrent program and tried again... to no avail. So it doesn't seem like I solved much of anything.  Never before had any torrent or plugin or setting or anything else been able to trigger an immediate and total shutdown/exit of qbittorrent as soon as a loaded (and not paused) torrent simply connects to the net. And I've been using the application for over 5 years.

Is it possible for something else perhaps an antivirus to shut QB down but only if it connects to the net? (normally I get a message from the antivirus if  it shuts or quaranteens programs. This time there is no message whatsoever from antivirus or firewall, so it seems like Q is shutting itself down.
Last edited by Raiden on Fri Jun 14, 2019 11:43 am, edited 1 time in total.
Raiden

Re: Qbittorrent's auto-installed plugin tried to hijack Computer proxy and shutdown

Post by Raiden »

Tinkering further it even shutsdown/exits without even a torrent being there downloaded.

That happens when I tinker with no torrent being processed but I go to the plugins (press the update plugins button after I opened the plugin dialogue box for example).

So it seems like the fundamental issue is related to plugins so far as I can tell but I can't be sure of that.
Post Reply