@Robert Cowan wrote:
Was told this was a known issue, but two updates have not addressed the problem.
It is, indeed, a known issue in the sense that it has occurred in several instances, but the developers need to track it down because they, on their own, have not been able to reproduce the issue (I have tried a number of test transfers and have yet to experience this anomaly).
