Yes, it is latest alpha. I have utorrent caching disabled completely and only windows caching "enabled". Actually the more I think of this, I start to see the problem here. How does utorrent "cache" work? Is it accumulating the writes in order to write them all at once, acting as second "coalesce write" setting? And how you think windows caching works? The problem may be in that when utorrent internal caching is disabled, "coalesce writes" settings kicks in and what you do is explicitly flush to disk every file write of "coalesce buffer" size, bypassing windows cache completely. This would explain the rape that I see utorrent commences upon the disk when high-speed download is started with "enabled" windows cache and small default 4 kb "coalesce write" size. If I'm correct, then what you need to do is don't flush anything if "windows cache" is enabled and let windows write writes at its own pace, flushing completed files by closing file handle on file. Plus then I am correct in coming up with workaround for rape described above by ballooning "coalesce write" size and introducing the actual utorrent cache as supposed to be.