/monthly_05_2013/post-54333-0-69706600-1369638288.png" rel=“”>
OS: wondows 7 profeseional 64bit
bitcomet : 1.36
yup that’s about it
and here is the link if anybody wan’t to try it http://download1.msi…_drivers_mb.zip
thanks in advance 
update : I resolved it by disabling ‘search for mirror to speed up your downloads’ in task properties
I’m wondering if the problem was caused by windows adding the “[0]” on the file name. This is done to avoid overwriting existing files. I’ll see if I can download this file without the error.
Ok, I figured it out. This host doesn’t change the file name when a driver version is updated so when bitcomet looks for mirrors from previous downloads, it finds the files previously downloaded from this exact location is different. Most driver are released with the version number as part of the file name, if this was released this way it wouldn’t cause this problem.
I think I’m going to consider this a verified bug, although there may not be anything that can be done about it, but at very least we may be able to change the error message to suggest disabling the search for mirrors option.
moved to bug reports
I’ve conveyed this to the dev team. And they will look into this.
The development team reports they have isolated the bug and it will be corrected in the next version of BitComet.
Thank you very much for reporting this.
queenie, as you can see by his member title, puttachinku is part of our beta testing team that you were asking about.