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

In the current Remote Desktop Client and also in the preview of the Azure Virtual Desktop App, it is unfortunately not saved in which state, and at which position the user has closed the desktop session.   Example: The session starts by default in Fullscreen, the user now switches to window mode and moves the window to the right of the screen. If the user ends the session or disconnects it and starts it again the session is back in fullscreen mode.   With the RDP properties you can influence the window behaviour a little bit, but not in the way that the Remote Desktop Client simply "notices" how the session was ended. Every other Windows program remembers the way (maximized/fullscreen) and position where it was closed.   Please change the behaviour to remember the position in window mode and whether the session ran in fullscreen or window.   ... 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

The RDP Client currently does not support true full screen with IPAD OS, leading to a lot of the display for externally connected monitors to not be used well. Teams and Outlook seem to support the extended displays better, so it would much appreciated on RDP Client as well ... View more

I want to suggest the implementation for resizable stage manager, so we can use the full resolution of the external display. ... 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

After upgrade my remote desktop screen is full of vertical lines. The attached screenshot shows an example that's not too bad but this happens in all applications, and on the desktop/taskbar. Lots of lines on the login screen. The app is used daily in the same configuration and was fine until latest update. Client and host reboot did not help.   Is it possible to revert to a previous version? This is Remote Desktop Beta 10.8.2 (2057) running on macOS Monterey 12.6.3. Client is Win 10 Pro, Version 10.0.19045 Build 19045     ... View more

Activating the "try the new client (preview)" option in AVD creates an issue with copy and pasting spreadsheet lines to Excel.   It's copied from a legacy application hosted in AVD that contains spreadsheets. As you can see using the old client it works like expected; it pastes all the lines appropriately into multiple rows. In the new client however the lines get copied into only one row instead. The application is hosted on the same server in both examples, the only difference is the client feature. ... View more

It would be great if you could pick a specific audio device to pass through from your local machine to the VDI machine.  Currently it only allows the default audio device so applications like Zoom and Jabber only allow you to use that.   ... 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

Hello, Since IpadOs 16.2 stagemanager support extern displays with widescreen. De Micrcosoft RDP app doesn’t support it. It woult be pretty when the widescreen resolution will support too. ... View more

Cannot enter Full Screen on External display on iPad OS.   iPad Pro 12” M2 External Display Microsoft Remote Desktop App   Using Remote Desktop on External Display does not scale to entire window and will not enter full screen. ... View more

RD client needs a full screen support on external displays, or there will be too much empty screen space lefted ... View more

With iPadOS 16 beta released, iPads with M1 chip are enabled with Stage Manager supporting external display. RD Client is one of the best apps I have used on iPad. Can’t wait to see this app taking the full advantage of the full-display support on external monitor! ... View more