Hi, I upgraded to Microsoft Remote Desktop Client for Mac: 10.8.2 but a connection I use just errors on trying to connect. I restored 10.8.1 from backup and it's working fine again, so thinking it is the new version causing the problem. It is quite an old server it's connecting to for this connection. Other, more modern servers are working fine with the newer version of RDP client.   Running on Ventura, 13.3.1.   ... View more

  Connections from Mac computers running Microsoft Remote Desktop to connect to remote servers start throwing up "Error Code: 0x4" when attempting to connect to servers today. Servers are confirmed working and functional, connections are fine from Windows clients and iOS clients. Only macOS clients seem to be impacted.   I went back through the Beta Builds and tried every version.    Build 2048 was the last version of Remote Desktop for macOS that worked correctly.   Every single build since, and including, 2057 fails to connect with error 0x4.   Thanks, Scott   ... View more

Hello! After update Microsoft Remote Desktop 10.8.2 (Mac OS 13.3.1) can't connect to Windows Server 2003. 10.8.1 connect without any problem. ... View more

Hello! I am unsure of the exact cause of this bug, but when flipping between the Microsoft RDP app on macOS and macOS apps, often trying to copy and paste from macOS -> Windows will fail (as in, nothing will paste, as if the clipboard is empty). Instead, to get it to work, I need to copy something on Windows first, which then means I can return to macOS to copy and then paste without issue. ... View more

After updating to version 10.8.2 I can no longer connect to servers running versions 2008 (not r2) and earlier - app throws error 0x4. Client version 10.8.1 works fine with those servers. Are those servers no longer supported? ... View more

It's not possible to update from Outlook Win32 to Monarch on Azure Virtual Desktop. For the intended purposes using the OWA client doesn't resolve.   Once you toggle the pop up displays it's downloading, but stays there forever. ... View more

after todays update i have been getting 0x4 error when trying to connect on the same system which had no issues just before the update. ... View more

Microsoft Remote Desktop client for Mac has a long and ghastly history. (Yes ghastly is the right word and this is not a typo where 'glorious' should have been used.)   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. The most infamous examples of this where that the Mac " (speech marks) key would generate an @ (at symbol) in Windows and vice versa although a number of other incorrect key mappings also apply.   Version 2.x did finally fix this 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. Regardless as this was new/different code it REINTRODUCED THE SAME BUG!!!   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.   Literally thousands and thousands of Mac users throughout the world except the USA have been complaining about this ever since.   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. The reason being it was not written by American programmers who are wilfully ignorant regarding international keyboard layouts.   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.   I have however been able to prove that the RDC client for Mac available here - www.jumpdesktop.com DOES connect to the same Microsoft RDC server and DOES NOT have this keyboard mapping bug. However the JumpDesktop client is a chargeable product.   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. Why therefore is this bug which affects potentially BILLIONS of people around the world i.e. anyone who does not have a Mac with an American keyboard still not been fixed?   PLEASE FIX IT AT LONG LAST!   How to reproduce. 1. Connect a non-US keyboard to a Mac, this could be a USB or Bluetooth keyboard, it does not have to be an Apple brand keyboard but genuine Apple keyboards would be the most common use. 2. The Mac should be configured to use the relevant keyboard layout - in my case this is UK but I know that it affects all other non-US layouts e.g. French, German, etc. 3. Connect to a Windows RDC session 4. On the Windows desktop open an app like Wordpad 5. On the Mac type in to the Wordpad document abcdefghijklmnopqrstuvwxyz these all map correctly. Now on the Mac type the @ (at) symbol, in Window you will instead see the " (speech marks) symbol, now on the Mac type the " (speech marks) symbol, in Windows an @ (at) symbol will appear. As mentioned other keys like the \ (back slash) are also incorrectly mapped. 6. Download the trial version of the JumpDesktop client 7. Use JumpDesktop to connect to the SAME Windows RDC server 8. Repeat the same typing test in to Wordpad, this time all the keys are correctly mapped with no settings having to be altered either on the Mac or in Windows.   Conclusion, Microsoft programmers are at fault. ... View more

Hi,    I am using Microsoft Remote Desktop Mac client ( https://apps.apple.com/fr/app/microsoft-remote-desktop/id1295203466?mt=12 ) everyday to connect to remote app hosted on Windows servers. I upgraded to 10.8.0 this morning and the app does not connect anymore. It throws error code 0x3000064   It fails both when using imported RDP file, and when using Workspace connection.   OS: MacOS Catalina 10.15.7   Regards, Aurélien ... View more

I have happily used Microsoft Remote Desktop Client for number of years now. I'm on macOS 10.14.6, RD Client 10.8.2 (2088). After recent update, I lost access to the client's legacy Server 2003. It was working nicely before. I'm sad today. Below is the log.   E|2023-04-28 16:38:31.8610 +03:00|FileLoggingWindowController.swift:243 Logging to file started!! E|2023-04-28 16:38:37.1110 +03:00|:0 {e491749b-f096-4b05-9b0d-b8a30c300000} <0x700002fa1000> RDP_WAN(ERR): TcpTrans::TcpTransportOnClosed - last exception: The operation couldn’t be completed. Operation now in progress: Operation now in progress /Users/runner/work/1/s/source/stack/libtermsrv/rdp/LegacyXPlat/Transport/ClientCore/Implementation/TsTcpDctTransport.cpp(1240): TcpTransportOnClosed() E|2023-04-28 16:38:40.2720 +03:00|FileLoggingWindowController.swift:194 Logging to file finished!! ... View more

Every time you close and open the laptop lid, a reconnect message appears. You have to press it again and again every time. Please add an option to connect automatically, as if the connection was broken. ... View more

When I update the version 10.8.2(2057), the desktop show below.   It worked well before I update it.     ... View more

Current version of the Remote Desktop for Mac (Version 10.7.3 (1966) is not supporting multiple workspaces to subscribe to. The windows version of the client do support it. When will this feature be available n the Mac client as well.   Currently you have unsubscribe and subscribe again to switch between Azure Virtual Desktop Workspaces. This is not practical when you need to switch often between two workspaces. ... View more

As of Version 10.8.1 (2048) it appears that Microsoft Remote Desktop client for Mac does not support UDP. This makes it significantly worse than the windows client. Is there any plans for adding UDP support to the client? ... View more

RDP for Mac version 10.7.7 has broken multiple monitor support ... View more

The Windows version of Remote Desktop allow registering multiple Azure workspaces with different usernames and passwords.  In the Mac app, it would be very helpful to be able to do the same.  Currently, when trying to add the second workspace, it says, "You are already subscribed to this workspace:" and displays the workspace url as "https://rdweb.wvd.microsoft.com".  Is it possible to add multiple Azure workspaces in the future? Thanks for your consideration. Norman ... View more

Hello, I did a clean install of Windows 11 and logged in with an account that has Sign-In notification set. I confirm each new login using the Microsoft Authenticator mobile app. I am also using macOS and would like to connect to Windows 11 using remote desktop. So I used a Microsoft product - specifically Misrosoft Remote Desktop, v 10.8.1. Unfortunately, due to 2FA, I cannot connect with this program. Can you advise me how to connect? However, I would not like to disable multiple authorization. ... View more

MacOS - Monterey ver 12.6.2 Microsoft Remote Desktop ver 10.8.0 (2032)   Before the update the Remote Desktop work perfectly.  After the update the Remote Desktop don't recognised my username and password.   ... View more

After upgrading to MacOS Ventura, using Mac Shortcuts is no longer working when connecting to remote Windows machines.   ... View more