Hey Kiwi I have observed this phenomenon as well and the way I got through with this is the following. Before I begin, my QOS has been administered from my Linksys Router running Tomato. Now initially I had one rule and it was port based, uTorrent ran with a mind of its' own. Now what I changed to that worked was having two rules both were still port based and now also protocol based, one for UDP and the other for TCP. I gave the TCP transmissions a Higher Priority compared to the UDP. Another way doing this is to have a single TCP and Port based rule set to whatever Priority you like. The reasoning for this is that uTP built into uTorrent is designed to rate limit the UDP part of the connection automatically, it doesn't perform well when outside influence is put in place. What I have observed is that with both TCP and UDP on the same QOS lane, uTP doesn't seem to stay ahead of the QOS curve (a uTP frequency cycle issue?) So again, I have a bad way of explaining things, but what I'm saying is that you should make two lanes for both the UDP and TCP parts of the transmission, preferable with UDP being either lower (hence it can perform better as a way to help TCP by sensing congestions faster) or auto govern itself with no rule put in place for the UDP aspect of the connection on that port. Hey is a next beta coming? This is seemingly more and more becoming like Google Projects as things just won't come out of Beta? Please folks spare me the knee jerk reaction for saying that last sentence an old timer here just can't help but wonder? Edit: On second reading, I seem to have replied in a tangent. But you need to give more details. Simplest thing is to do a step by step approach. First reset all settings back to default, and re change things until you find what is wrong. Change the settings in the Advanced settings page last, as that maybe where the problem is coming from. My hunch is that the problem could be that there may internally (through the Advanced settings) be two IP's uTorrent is trying to bind with ... net.outgoing_ip, and net.bind_ip. I believe the conflict is that there is two IP's trying to use one Port. Or the problem could be that the Advanced setting net.outgoing_port has a port associated to it and you didn't see it. More info would be good in this case, but if you want to give it a crack my settings (which is similar) is the following for those problem settings outline: net.bind_ip is (empty space) [Default] net.outgoing_ip is (empty space) [Default] net.outgoing_port is 0 [Default] [Default] means that it is the default setting, and you can reset it from the Advanced settings page. All other settings are done through the non-Advanced settings page, primarily in your case the Connections settings page is your place to set things right. So then set your port (it encompasses both TCP and UDP), and make sure "Add Windows Firewall exception" setting is checked off. Now remove the Windows Firewall rule you made manually (if you did?), as it could conflict with the Auto rule exception that uTorrent will make on start-up. Hope it helps, and the top part is for the QOS setup later on