KaoDome Posted October 19, 2018 Report Share Posted October 19, 2018 So, this has been the same for quite some years now and given there's no change I decided to report it. Basically, if you disable telemetry reporting you don't get any update. It's nothing new, it's been happening for ever but I find it uncceptable to be honest. It's not that there are no updates, as soon as you enable the option to send detailed info when checking for updates you are told there is actually an update (or there have been several already if you had it disabled for a while). It not only affects the μTorrent client but the mainstream BitTorrent one as well. Link to comment Share on other sites More sharing options...
rafi Posted October 19, 2018 Report Share Posted October 19, 2018 with 3.5.3 ? At least check (for betas) with a newer version, see if that happens... BTW, for me it does not update to Betas even with this enabled... Link to comment Share on other sites More sharing options...
mike20021969 Posted October 19, 2018 Report Share Posted October 19, 2018 23 minutes ago, rafi said: for me it does not update to Betas even with this enabled... Update doesn't work for me full stop and always pops up the "...no new version..." window. It did work a long time ago in the olden days when people used to walk faster and everything was in black & white. Link to comment Share on other sites More sharing options...
rafi Posted October 19, 2018 Report Share Posted October 19, 2018 Ok, confirmed with 3.5.4 b44520 (stable) and b44504 (beta). I guess it will be fixed ASAP.... Good catch! Link to comment Share on other sites More sharing options...
mike20021969 Posted October 19, 2018 Report Share Posted October 19, 2018 1 hour ago, rafi said: I guess it will be fixed ASAP.... Even going back to 2.2.1 won't see any update (not for me anyway). So wherever the check "looked" for updates has maybe been disabled (server side). Link to comment Share on other sites More sharing options...
rafi Posted October 19, 2018 Report Share Posted October 19, 2018 1 hour ago, rafi said: Ok, confirmed with 3.5.4 b44520 (stable) and b44504 (beta). I guess it will be fixed ASAP.... ^ works for me with that "send info" enabled, so server side is OK (unless you've blocked it in your firewall/hosts). Also, best remove all exe files after the above from .\update\*.exe Link to comment Share on other sites More sharing options...
mike20021969 Posted October 19, 2018 Report Share Posted October 19, 2018 9 minutes ago, rafi said: ^ works for me with that "send info" enabled, so server side is OK Yes, that works. 3.5.4.44632 sees beta update, but only 3.5.4.44640. Link to comment Share on other sites More sharing options...
rafi Posted October 19, 2018 Report Share Posted October 19, 2018 Well, I guess this is what is available on their end/server ATM. Ask them why... Link to comment Share on other sites More sharing options...
mike20021969 Posted October 19, 2018 Report Share Posted October 19, 2018 5 minutes ago, rafi said: Ask them why... I'm not really concerned about the version. But having to delete/remove any .exe in the update folder & check send detailed info box beforehand are the problem areas. Link to comment Share on other sites More sharing options...
rafi Posted October 19, 2018 Report Share Posted October 19, 2018 No, only what is reported here. Old exes should not be a problem in real life... Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.