µTorrent 1.8, page 1

just wonder anyone have problems with µTorrent 1.8 build 11813?
1.77 got updated itself and since than it cant down/up anything [on the office pc where i dont seed much]. but if it'd do this here i'll getting seriously angry as im seedin 850 torrents at home. any ideas?

it forked  fine with me. i think is better to restart your pc first before updating. what i did yeah i restarted it than when i started the utorrent a pop up message showed up saying about the new version and i installed it and it went normal very good...

It works good for me as well. Restarting utorrent or rebooting might help, otherwise you might try the usual connectibility things and if that doesn't work, maybe something in the settings that got reset while updating, that's all i can think of.

I have problems,
at least one. I haven investigated all the cases when something has happend, so I cannot say how many bugs there are. But there is at least one - for sure.
The result is uTorrent cannot connect to the tracker and put it in status "offline" (timeouted). And of caurse the tracker cannot see it and the seeding peer disapears.

Either I am back to 1.7 or I will use Azureus 3.1.

yes, 1.8 is awfull, didnt thought they can do something so ugly. anyway, i'm tyred of investigation and will leave it as it is. lets hope they fix it

well, finaly im seeding from 1.8. after a 3 years with connectable status im 100% not conectable right now. 1.8 is the worst thing im running on my pc ever. again,

Thanks for the info Bidona and Spas.

Reading the shoutbox over the past two weeks there seems to have been some issues. I have installed 1.8 on my second PC, there seems to be no issues there. But i didn't not want to risk the 200 or so on the other pc to a not connectable status.

Sit and wait for the problems to get ironed out by the sounds of it.

its all because of nod32. just cant understand is it nods fault or utorrents. wich one should i keep and which should go? any ideas?

Can't answer that one for you Bidona.

Just to confuse you even more. My first PC runs 1.7 with AVG and the second i have just set up 1.8 with nod 32. The main share is on the first pc. I have been able to get the second pc connectable though!

I had a similar problem with utorrent 1.8 and nod 32. It's working fine now, I fixed nod's IMON settings - unticked "enable HTTP checking" and all was back to normal. I'm a big fan of utorrent and I don't like nod32 at all, so if you ask me remove the nod32..    Better try to adjust IMON settings, though.

was big fan of µtorrent as well but i've used nod ages before it. when i was with 1.4/1.5/1.6/1.7x everything was ok with both µtorrent and nod. in sudden all went crazy when 1.8 came out. so, the problem have to be 1.8 and not nod32, right? now im not a fan of either of them

Bidona it's not the nod32 I use AVG and got the same problem as you "not connectable"  or the status is "timed out"

I use AVG 8.0 allong with utorrent 1.8 and everything works perfect, haven't had a moment of being not connectable, so the problem won't be caused only by either of them.

To me it is a program bug.
When the test for port forwarding fails, only uTorrent not Azureus 3.1 for example, I make a simulating change of the uTorrent port. Then the test passes.

In order to help developers to improve the program they need information about its behavior.
But they accept such information for their Betas. So, I use uTorrent 1.8.1 Beta.
My impression about it is it seems better - so, less unexpected events and more important the developers release Betas relatively often. I think they constantly improve something.
In other words, if you want the latest version of the program use Beta version.
But ... I still have unexplained behavior. This time I think it is related to the latest Window upgrade. So, I cannot say exactly the reason.