Hi Peter,
We are still trying to collate how many users have the same problem before we can forward this to the Office Team.
Regards.
Count me in - I have exactly this problem described in the thread.
Microsoft Excel 2016 MSO (16.0.7571.7095) 32-bit
99.9% of Excel users will either a) not recognize this issue, or b) recognize this issue and not try to solve it, or c) try to solve it and not find this thread, or d) find this thread and not bother posting.
My guess, based on the characteristics of the bug, is that it affects EVERYONE with Excel.
Besides, even if it's only us, why would that mean Microsoft shouldn't fix a bug that they created?
Disappointed, but not surprised, that this bug has been known to Microsoft for so long without an acknowledgement that it will be fixed...