anyone who does not have a Mac with an American keyboard still not been fixed?ġ. Why therefore is this bug which affects potentially BILLIONS of people around the world i.e.

Microsoft over the decades has in a number of cases committed grave offences against Mac-kind but in more recent times has been comparatively friendly to the Mac using community. However the JumpDesktop client is a chargeable product. I have however been able to prove that the RDC client for Mac available here - connect to the same Microsoft RDC server and DOES NOT have this keyboard mapping bug. Unfortunately I now once more have to use an RDC client and I am finding that the Parallels client whilst still available is not connecting to the Microsoft RDC server whereas the Microsoft client does successfully connect even if it then inflicts cruel and unusual punishment in the form of this now ancient keyboard mapping error. The reason being it was not written by American programmers who are wilfully ignorant regarding international keyboard layouts. When I last was personally victimised by Microsoft with this issue many years ago I also reported this but I found that the Parallels Remote Desktop Client for Mac did not have this bug. Literally thousands and thousands of Mac users throughout the world except the USA have been complaining about this ever since. Note: I have just reproduced this with Microsoft Remote Desktop 10.8.1 (2048) running under macOS Ventura 13.2.1 with as mentioned a UK Mac keyboard. Regardless as this was new/different code it REINTRODUCED THE SAME BUG!!!

Microsoft then bought a 3rd party RDC client and this became the next Microsoft official client and I cannot remember if this was released as version 5.x or 7.x. The most infamous examples of this where that the Mac ' (speech marks) key would generate (at symbol) in Windows and vice versa although a number of other incorrect key mappings also apply. Version 1.x had a bug whereby anybody using a Mac with a non-US keyboard was tortured by the software failure to map keys correctly to the Windows session.

(Yes ghastly is the right word and this is not a typo where 'glorious' should have been used.) Microsoft Remote Desktop client for Mac has a long and ghastly history.

Microsoft exchange mac mail