October 15, 2008 by sharky
One good thing about µTorrent is its upgradability to a newer (hopefully improved) version, and that this is set to "ON" by default (with user confirmation) in the client. The bad thing about uTorrent …well, ironically it’s the same thing. After a much-anticipated release of version 1.8.0 stable, everything started to go wrong: from ongoing ZoneAlarm firewall and NOD32 antivirus conflicts, Vista problems, connectability issues and a bounty of other mishaps in the last month or so. µTorrent developers have repeatedly scrambled to put out quick betas/builds until finally settling on the latest stable v1.8.1 - a version even the dev team couldn’t have contemplated having to come up with in such short notice. All this for a tiny 263 KB application.
WinAll Problems:
After testing uTorrent v1.8.x on both WinXP and Vista, torrents seem to take an increased amount of time to load the initial seed/peer list, which translates to slower download start times. At first we thought the (private) tracker was rejecting the client; but after waiting (up to 2 minutes or more on some private trackers), the tracker finally did connect and commence downloading the torrent. This was never an issue with v1.7.7 where torrents started instantly.
Avoid The ‘v1.8.0′
The semi-new version uTorrent 1.8.0 is finding itself banned on more than just a handful of trackers, including BMTV. Using v1.8.0, torrent connection stopped entirely as shown by these tracker stats:
Further investigation proves that v1.8.0 is indeed a banned client at BMTV:
Avoid The ‘Betas’
There’s been 15, yep count ‘em 15 “beta/build” versions of µTorrent 1.8.1 before the current "final" (as of today) release #12639. While everyone can appreciate the µTorrent team for coming up with quick fixes to improve the client, a big problem is since these "betas" are automatically (and repeatedly) being offered to users to upgrade an already known stable release or to a future beta (to another one). By default, you either have to click "No" and take your chances with a stable (or beta), or turn off these settings in the client.
So what? you say? Here’s what — Most private trackers ban any use of an unstable or beta BT client - and this goes for µTorrent. Private tracker owners/sysops cannot possibly keep up with these betas - many will allow some of the unstables, some will not. The only sure way it to check with your private tracker’s allowable BT client list to be sure. Or use a public tracker where they could care less.
Apparently this issue has been resolved in the latest version, which does not prompt users to upgrade to a beta (as there is no current beta build being offered by the µTorrent dev team). It’s unclear if the next beta v1.8.2 will ask users to update to a build version that is not classified as a final.
uTorrent 1.8.1 Banned?
Not yet, but it likely will be, once a v1.8.2 becomes a "final" build. Be sure to keep current with your private tracker’s rules on allowable BT clients. And take caution when updating µTorrent to any beta release version.
Downgrading Back to µTorrent 1.7.7
While µTorrent v1.8.x has included a small cornucopia of changes and improvements, there’s always the option to go back to v1.7.7 if you’re finding any issues. As stable as 1.7.7 is, it’s still an allowable client on any tracker. Downgrading is simple - firstly, quit µTorrent if you have it running, download the old version, and overwrite the utorrent.exe file in your installed directory. For XP users, the default path is C:/Program Files/uTorrent/utorrent.exe
Many users have complained that v1.8.x shows them as ‘unconnectable’ even when no other modifications to the system have occurred, and v1.7.7 worked just fine. In all likelihood the problem is a firewall issue whereby it’s blocking the new version - a ‘quick fix’ is to remove µTorrent from your firewall ‘exception’ rules, reboot your PC and re-allow it back in your firewall software.
Got any other issues with the new µTorrent? Gripe about it on their forums, which have never been busier.