I have this problem on the latest official firmware, tinker 19.03.1, tinker 16.01, and I just discovered it happens with mainline marlin 2.1.1 (all tried on the same UM2)
So it's either a hardware issue, or it's a bug in LCD code shared between all four of those.