I was able to reproduce this issue in 4.10.4 and added more information to a bug that was generated for this issue, which is currently unresolved. We are working to track down this issue (UE-11109) and get a fix in place, and we appreciate your patience while we do so.
Once the issue has been resolved either myself or another staff member will return with the updated information. Let me know if you have further questions or need additional assistance.
Thank you,