Thanks for your bug report. I have not been able to reproduce this issue here so far. Just to confirm: this is happening when the size of the file being downloaded is exactly one block/cluster size larger than the available disk space?