Windows 10 home - updating qbt from 4.1.5 to 4.1.6
Posted: Fri Jul 05, 2019 7:54 am
qBittorrent version and Operating System
ver 4.1.5 (x64) attempting to update to 4.1.6 (x64)
Windows 10 home. 64bit
What is the problem:
each time when I open bt; it detects that it is an older version and promts for an update. I download, and it installs, and even disassociates itself and re associates iteself with magnet links / being the default client for torrent files - so I know it's installed etc.. but the version still stays @ 1.5 and never actually updates to 1.6 - so each time I open BT again; it just keeps cycling over the same process..
What is the expected behavior:
to overinstall from the previous version; same as all other version skins.
Steps to reproduce:
update using the check for updates link; follow all prompts and attempt to install.
Extra info(if any)
there also seems to be an issue that chrome now opens and additional tab to open a magnet link before qbittorrent picks it up - as before it just used to open directly into QBT. Is this a chrome behaviour that can be prevented or is it also something to do with QBT?
Thanks
ver 4.1.5 (x64) attempting to update to 4.1.6 (x64)
Windows 10 home. 64bit
What is the problem:
each time when I open bt; it detects that it is an older version and promts for an update. I download, and it installs, and even disassociates itself and re associates iteself with magnet links / being the default client for torrent files - so I know it's installed etc.. but the version still stays @ 1.5 and never actually updates to 1.6 - so each time I open BT again; it just keeps cycling over the same process..
What is the expected behavior:
to overinstall from the previous version; same as all other version skins.
Steps to reproduce:
update using the check for updates link; follow all prompts and attempt to install.
Extra info(if any)
there also seems to be an issue that chrome now opens and additional tab to open a magnet link before qbittorrent picks it up - as before it just used to open directly into QBT. Is this a chrome behaviour that can be prevented or is it also something to do with QBT?
Thanks