I added the following text to another thread on the same issue, I've tried to be more specific here as to the circumstances rather than just saying it doesn't work, the guys need more detail to be able to help or tweak BT to fix the bug I suspect.I'm having this problem too, however I have discovered that it only seems to occur when downloading more than one torrent at a time, basically I'll queue a few up and the first one past the post so to speak starts (and continues) downloading, but the other torrents just sit there saying 'Checked 0.0%' and don't start. I've tried various solutions including restarting BT, using Stop and Start and Force Start, but I usually find the only way to get anything going is to wait until one has finished, close BT and then open it again.
Then we enter the same pattern described above, the first to start downloads, whilst the rest sit at Checked 0.0%. The question to the guys above is are you downloading via a proxy? If so try not downloading by Proxy, I have a suspicion it might be something to do with that feature ability, it used to be fine as a feature a couple of versions ago but now seems to stumble.
I also noted that with version 7.8 my max download speeds are off by about 400kb, and whilst we all know that download speeds can vary wildly due to numerous factors, I've been running things down at a reliable 1.5-1.6Mbps for so long that when the speed dropped it was something I noticed. It might be completely unrelated of course but is nevertheless an observation. My 'Maximum number of Active Torrents (upload and download)' is set to 400 (which I'd never even get close to I should add, and 'Max Active Downloads' is set to 400 as well.
In the Number of Connections section on Bandwidth (reading top to bottom) I use, 400, 400 and 4. These settings to date have always served me well and the rest are pretty much left at default. As a side note when you uninstall BT, it's worth scooting round your hard drive and checking for any rogue files folders that haven't gone, you may need to set View Hidden Files and folders to do this.
That's what I had to do when I had a problem with my previous BT version and then I installed V7.8 which resolved the issue I was having with whatever that previous version build was. My 7.8 is build 29421 (32-bit). I thought about this early on tablet43, however I found the complete opposite, if I turn off downloading via proxy it appears to be OK. I have tested several proxy servers all over the world and everyone behaves the same.
The list of file extensions associated with BitLord - The Ultimate Torrent Downloader - A bittorrent client for BitTorrent peer-2-peer file-sharing protocol. Bitlord free download. Get the latest version now. Find anything without visiting bad websites. Ten million torrents indexed.
But turn off DL by proxy (specifically https proxies) and it sees to be OK. So quite strange we should find opposite results. As yet I haven't investigated alternate clients since I prefer the lightness of BT, but it would be interesting to have a tinker with the likes of Azureus perhaps. When you guys first upated to 7.8 I too was having this problem. About a week or so ago bittorrent offered a stable update and my problem was solved. I get home tonight to find another stable update availiable. I dled it and now I'm having the same problem again.
I cannot dl more than one torrent at a time(the others stay at checked 0.0%). Tried to close and restart the program, but it will not close the program unless I restart my cpu or use task menu- even though the confirm program close box is checked.
It does not confirm. Very frustrating! If you could tell me how to go back to previous update; or fix this one I would greatly appreciate it. I'm having the exact same problem and it just started tonight, within the past few hours. I received notice of a new stable bitTorrent update and the moment I agreed to the update I was stuck at 'Checked 0.0' for everything.
The closing and reopening of the torrent browser trick described here worked for me to get the existing torrents going, so thanks to the those who suggested that. However that's not a permanent or practical solution.
Hopefully whatever glitch this update seems to have caused can be fixed quickly.