That doesn't sound good and is very odd. We're working on changes that will add full-file hashing for all shared files on the network, making this operation much more robust and hopefully eliminating corrupt file messages.

The addition of the corrupt file messages is a good thing in some ways, however, because with the previous implementation the files would have been corrupted without you knowing about it.

Is anyone else seeing this? You are getting the message very consistently?