We seem to be experiencing this issue since we upgraded to 17.6.3 and subsequently since we've updated to 17.6.4. It doesn't happen on all interfaces, but when it does happen the only way we can get around it is by migrating the affected user to a di...