uTorrent 1.7 Stable Finally Released

Written by Ernesto on July 13, 2007 

After months of hard work and nearly half a year after the release of their previous stable release uTorrent 1.7 finally sees the light. uTorrent 1.7 comes with several new features and some essential changes and big fixes.

utorrentuTorrent 1.7 is fully Vista compatible and the 65,536 piece limit for torrents is removed which might improve the download speed of larger torrents.

Other noticeable changes are:

  • Feature: option to auto update to betas
  • Feature: automatic upload speed limiting
  • Feature: Web seed support for single-file torrents
  • Feature: Local Peer Discovery
  • Change: Prioritize seed queue based off seed/peer ratio
  • Change: Improved half-open connection management
  • Fix: download rate limiting bug
  • Fix: UPnP mapping when local IP changes

A complete list of changes, features and fixes can be found at the uTorrent forums. In the meantime the uTorrent team is working hard on their next milestone, the release of a Mac version.

Until those ported versions are ready Mac users might want to try running it under emulation to get uTorrent working on OSX.

Time to update! uTorrent 1.7 (Windows)can be downloaded over here.

Previously: Media Defender Buys P2P.net: Preparing for their Next Scam?

Next: Media Defender Endorses TorrentFreak’s Great Work

29 Responses

1 Jul 13, 2007 at 07:20 by Anton

Finally! I been beta testing it for months now.

2 Jul 13, 2007 at 07:54 by chrisn

very nice, just switched from azureus to uTorrent 1.7

3 Jul 13, 2007 at 09:42 by Hamster

Usual question:

Is it (still) safe?

4 Jul 13, 2007 at 10:32 by Jdizzle

Anyone know of any tests done to see if it phones home or does anything suspicious?

I won’t be using it until there is some proof it’s safe.

5 Jul 13, 2007 at 12:03 by hoz

and now this version is banned on some trackers because of inaccuarate data sent back

6 Jul 13, 2007 at 14:33 by børge

From this article:
“In the meantime the uTorrent team is working hard on their next milestone, the release of a Mac and a Linux version.”

From uTorrent FAQ:
“Is there a Linux or Mac version?

The OSX port is in progress. A Linux port is currently not planned for the future. ”

:(

7 Jul 13, 2007 at 15:11 by Ernesto

You’re right Børge, my bad…

8 Jul 13, 2007 at 15:27 by Ben Jones

Jdizzle – with all the people testing, and all the people in the µtorrent irc channel that check this, if it happened, you’d soon find out. Especially as I am one of the regulars there, and had switched within 15 minutes of release. If it phoned home, I would know.

Hoz – there are always going to be some people running trackers, who are out of their depth. It is also not that strange for people to just follow what some other tracker admin tells them, regardless of how true it is. Just look back and see how many trackers banned all versions of bitcomet, for the bug that affected one release (yet don’t ban az, which can be made to do that easily enough, or every other windows client which can effectively be manipulated to do the same thing).

9 Jul 13, 2007 at 18:39 by Hamster

“I won’t be using it until there is some proof it’s safe.”

So you aren’t using Windows either? ;)

10 Jul 14, 2007 at 04:23 by quakebuzz

it phones home

11 Jul 15, 2007 at 07:39 by jo

“Every version > 1.6.1 is Bittorrent Inc., which is directly in partnership with the movie studios. Viacom Inc.’s Paramount Pictures, News Corp.’s 20th Century Fox, Lionsgate, Palm Pictures and Kadokawa Pictures USA etc etc .

In fact versions > 1.7 don’t even have the same developer doing it. It’s all handled now by Bittorrent Inc’s development. The original author (up to 1.6.1) is no longer even part of the project. ”

Saw that somewhere don’t know if its true.

12 Jul 15, 2007 at 15:27 by Hamster

It is true. So stay clear of 1.7+

13 Jul 16, 2007 at 04:56 by Whopperboy

i took a look at the newest version 1.7 and it looks the exact same as 1.6.1 and i left it up to watch it for a bit to see if it uploaded anything but it didn’t look like it was to me and as for ludde he is still part of the development team but only as a consultant so i don’t believe that it is totally safe but just stick with either 1.6.1 or Halite until they make it open source and use peergaurdian2 to be extra safe

14 Jul 17, 2007 at 07:08 by kopss

Alot of private sites have banned 1.7 now and require 1.6.1 or lower. 1.7 is not to be trusted…trust me

15 Jul 17, 2007 at 15:53 by Licking my China Bitch Ass

My bitch and I won’t “upgrade” to version 1.7 as it got fucked up as spyware! You can think who is behind that gang! Version 1.6.1 is already very stable and clean coded so don’t use 1.7!

16 Jul 18, 2007 at 20:59 by FreQ

OK to all those people saying it phones home , Where are you getting your info from ? do you have prof, I mean not hear say shit but real concrete prof ? if not please stop talking shit !!

17 Jul 20, 2007 at 05:52 by Mike

“OK to all those people saying it phones home , Where are you getting your info from ? do you have prof, I mean not hear say shit but real concrete prof ? if not please stop talking shit !!”

My firewall has caught it on severl occasions trying to “send e-mail”

No Idea what was in the message or where it was going but it was suspicious as hell. Thats why I’m going back to 1.6

18 Jul 29, 2007 at 10:11 by piki

Believe it or not it phones home … i will investigate deeper but this is from PG2 logs after starting up uTorrent 1.7+: BitTorrentInc 72.20.34.145:6881 UDP Blocked … gonna sniff it.

19 Aug 03, 2007 at 04:39 by Papa Midnight

…And banned from most private trackers right along with BitComet, BitLord, etc. In addition, tack up 1.7.1 to the banned list as well.

20 Oct 08, 2007 at 00:18 by Rita

It makes a one packet UDP request to 72.20.34.145 (IP providor is Staminus Communications and the IP is also the one utorrent.com is on) on port 6881 but only if you enable DHT. The data in the packet is “d1:ad2:id20:.

21 Oct 08, 2007 at 00:24 by Rita

Woops, the stuff I was quoting broke my message. A screenshot of the data packet is at http://img266.imageshack.us/img266/6940/78302557is7.gif. The data is similar to the stuff in other DHT packets (that follow immediately afterwards to a variety of other IP’s). I don’t think it’s anything dodgy – just DHT

22 Oct 15, 2007 at 21:52 by No Dot

That URL should be http://img266.imageshack.us/img266/6940/78302557is7.gif

(no dot)

23 Nov 18, 2007 at 23:52 by Matt

I’m running uTorrent 1.6 (build 474) and on starting up PG2 blocks a connection to 72.20.34.145:6881

Is this the same thing as 1.7+ is doing, and if so, how is 1.6 any better? (alternatively, how is 1.7 any worse?)

24 Feb 22, 2008 at 19:52 by rick

Hi, any “Hack the max half-open TCP connection” patch for the Vista version? i m trying out using wireless & is hardly moving. some advise pls?

25 Mar 11, 2008 at 23:29 by tina

i use version utorrent 1.6 and lately i can open it but it wont connect to any of the seeders/leechers its showing.Bear in mind my peerguardian is running whenever i use the program (i wouldn’t run it without it) I can’t even connect with utorrent’s homepage to check what the problem is…..its seriously starting to piss me off what is going on here?

26 Apr 28, 2008 at 07:08 by Jack

TO ALL DOWNLOADERS….!!!!
I am a debut artist who’s just recorded one of the most expensive debut albums in recent history.

We have just released my debut album as a FREE HQ Mp3 download.

It was a tough decision for us to make because of the vast amounts spent on the album. We had two of the biggest record producers in the world work on it…. at Peter Gabriel’s Realworld studio and at Abbey Road studio in london.

Despite all that, we recognise the massive potential the internet and free albums in particular offers. We launched last friday and have already had 1000’s of DL’s all over the world.

Come over and download for FREE.. it takes 2 minutes to DL because we have a dedicated server.

http://www.jackrubinacci.com
Thanks
Jack

27 May 11, 2008 at 14:05 by Boizy

Not only the later versions of uTorrent a problem, so too is BitComet BC).

BC was found to be tranferring up to 5GBytes/night to IP addresses located in P.R. China when its DHT was switched on.

None of this traffic was torrent related and did not appear in BC’s own stats.

Reports to the BC forum about this, after initial silence, led to, character assassination by a BC supporters club (aka “the management” under cover) and was finally followed by deletion of the thread when the actual chinese ip addresses (so people could block them) and traffic details were posted to the thread. This traffic was shown to be encrypted. BC management did nothing to remove this offending code by a year later. It was realized that others had reported this before but their reports were ignored/cleverly deflected.

After 7 days of hostile responses from BC supporters and posting of the chinese IP’s, the poster had his pc attacked for some 12hours from over 400+ (probably a bot DOS attack) ip addresses with billions of packets. With numerous attempts to hack various ports. The next day the posters ISP offically changed the (fixed) IP address of the poster and then blocked all traffic to it at their external firewall! The same day the thread was deleted. Attempts to post about the dos attack on the BC forum were blocked.

I use utorrent1.6.1, Azureus2.5.0.4 and don’t use BC at all.

28 Jul 12, 2008 at 18:13 by niraj

my lan ip is 72.20.34.145
and i m using utorrent 1.7, but from two days i m not getting to connect with the trackers it always say firewall/router is blocking the incoming connection

i forwarded the port for the router and even turn of the antivirus and firewall but even affter that i m not getting the connection which results me download speed <10kbps but my upload is fine and is 25kbps

tell me how can i resolve the problem or how do i know which port is open for the incoming connection

29 Aug 08, 2008 at 10:18 by dave

I noticed a previous commenter remarking “My firewall has caught it on severl occasions trying to “send e-mail”".

Regardless of whether or not µTorrent is to be trusted, this is not indicative. When an e-mail program needs to send a message, it connects to a typical port on the mail server (25). As the BitTorrent protocol can operate on any random port, sometimes you connect to someone via their port 25, and your firewall misinterprets this.

This should be avoided by enabling “bt.no_connect_to_services” in the advanced options, so long as 25 is listed as one of the ports.

Responses are closed

All remaining responses will continue to be archived. Use the TorrentFreak forums if you want to discuss something.