The idea is to support Linux desktops like Ubuntu and Fedora. Currently, only the web client is available for Linux, but many features are not available. ... View more

Hello,   The copy and paste functionality doesn't work anymore. It used to work; i have the feeling it stopped working since the last update of Microsoft Remote Desktop.   EDIT for clarification: Copy and Paste from remote machine to local machine does not work.   I tried: Setting (Edit PC > Devices & Audio) Clipboard mode to disabled, reconnected a machine and disconnected from the machine. Setting (Edit PC > Devices & Audio) Clipboard mode to Bidirectional, reconnected a machine. Setting (Edit PC > Devices & Audio) Clipboard mode to Remove to local only. Remove Microsoft Remote Desktop and reinstalled it. Deleted the running proces on target host named rdpclip.exe and restarted rdpclip.exe   Machine: iMac Retina 5k, 27 inch, 2017   Software: macOS Monterey version 12.1 Microsoft Remote Desktop for Mac, version 10.9.0. ... View more

The Remote Desktop Android app stopped working correctly with the Samsung S Pen Fold Edition on the Samsung Galaxy Z Fold4 after the latest Remote Desktop Android app update. When the pen nears the screen, it starts selecting everything it hovers over as if it was constantly touching the screen, making it virtually impossible to use. It worked fine before the latest Remote Desktop Android app update and it still works fine with others apps. ... View more

In the MACOS Sonoma system, there will be an audio redirection problem when using Microsoft Remote Desktop Beta（ersion 10.9.3 (2158)） or the official version（Version 10.9.2 (2147)）. The microphone in Windows is unstable, especially when having a meeting in Teams, and turning on auxiliary subtitles, my Teams cannot be recognized. My name is displayed as "Speaker 1" instead. Secondly, the microphone will appear that the microphone device is not working after a few minutes of speaking, making it impossible for participants to hear my voice. ... View more

In the Microsoft Remote Desktop MacOS app, if you want to login with a Microsoft Entra (aka Azure Active Directory) account, you will get an error message saying you must disable Network Level Authentication (NLA). The error code I get is 0x3107.   I am able to get around this error by editing the RDP config file and setting the enablerdsaadauth and targetisaadjoined values from "0" to "1".    It would be immensely helpful if this option could be added in the Microsoft Remote Desktop GUI. It looks like all the functionality is there, it just needs a GUI checkbox.   This option already exists in Windows Remote Desktop if you enable the "use web account" option on the advanced tab.   I realize this is not an issue for Azure Virtual Desktop, because the config is downloaded and set up automatically. But for everyone who is using Microsoft Entra that may need to provide instructions for users to set this up, the option would make life a lot easier. ... View more

Hello,   I use Microsoft Remote Desktop regularly on both Windows (Surface Laptop 5) and macOS (MacBook Pro M1 Pro), and the macOS client has some significant issues not present on the windows version. I was wondering if this is due to some misconfiguration on my end or the features just work better on windows. Here is a list of issues that I face in the macOS version of remote desktop but not on windows:   - Low quality audio and static noise on any sound coming from the remote desktop (including teams) - High latency in inputs when multiple monitors are connected (connected to the same network as compared with Windows) - Videos from any source (sharepoint, youtube, teams) do not play  - Degraded webcam quality in teams compared to native macOS   Thanks! I'm using the 10.9.6 beta version of the macOS client. Would be glad to hop on a call or give more information if necessary. ... 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

We are using the Microsoft RDP client for a lab product we are working on. On windows, we can encrypt the password and store it in the RDP client, thereby launching the user directly into the VM.   On Mac, there seems to be no way to pass in a password in the RDP file or via the command line. Are there any plans to add such a feature? It would be nice if our users didn't have to copy and paste the password in. ... View more

With the latest Samsung Galaxy One UI 6.0 the top bar in dex that auto hides is blocking functionality in the remote desktop android application. Even when the one UI top bar hides it will still block mouse clicks from registering in that region.   Also an additional issue is Win + Crtl + Left/Right Arrow no longer works to switch desktops in windows.    ... View more

This feature would be give the ability to AVD admins to bring a new image version live in a more controlled way.     ... View more

Really frustrating that saved Workspaces disappears in Microsoft Remote Desktop 10.9.0 (macOs 13.5.1). Not like this in previous MRD versions. ... View more

I previously replied to an older post (ipad-os-rdp-smart-card-using-function) requesting iPadOS RD Client support for smart card credential pass-through.  The original requested never replied to answer which smart card device they were using on iOS (iPadOS in my case). I utilize RD Client on my iPad Pro to access my Azure Virtual Desktop work environment but am severely workflow-limited without this smart card pass-through functionality (unable to utilize signing, encryption, and PIV certificates maintained on my smart card). Multiple smart card devices attempted:   - Thursby TSS-PK2 (firmware ver > 4.20)   - Bluetooth 4.2 Smart Card Reader (from twocanoes.com)   - FEITIAN iR301 Mobile Lightning Reader (from twocanoes.com) I can successfully use the above smart card devices individually on my iPad Pro (outside of RD Client) with the Safari web browser or integrated Thursby “Sub Rosa” iOS app but this leaves an incomplete workflow without full functionality.   Please consider adding this functionality to your road-map. ... View more

Hello, I am on a 2021 M1 16" Macbook Pro and when using Teams for a call on my Windows 365 machine and am directing the sound output to the Macbook Speakers, it only comes out of the right side speaker. However, all the rest of the Windows sounds and audio come out of both speakers. ... 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

Sehr geehrte Damen und Herren, bei meiner Remote Desktop App verliere ich bei jedem Start mein Workspace. Der Fehler trat das erste mal vor knapp 4 Wochen auf. Gibt es eine Möglichkeit den Cache am Mac zu löschen oder eine andere Alternative um mich zu meinem Cloud PC zu verbinden? Mit freundlichen Grüßen, Claudia Ruhrmann ... View more

Compared to the previous functionality, which provided a real remote desktop experience, this is now completely broken (v10.5.1) if you have an external display connected, where you are forced to use the iPad screen to control the remote session on the external display - which doesn’t even work properly for pointer/mouse devices (eg only touch screen allows you to reach the tiny Start button on the bottom left of a Widows host scaled up to 5k).   The only apparent workaround is to disconnect the external display.   Please either revert or make the new features with issues toggleable in settings, so that either the main iPad screen or the connected display can be used individually, as was the case in versions 10.5.0 and prior. ... View more

I had to reset my office identity on MBP recently, which caused me to reauth on the Remote Desktop Mac app. This was fine, but after that i saw that my Workspace feed settings was nuked/removed (i am guessing as a result of losing auth). A cause for re-auth should not reset other settings, it should prompt for auth, and preserve existing settings once auth is restored. ... 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

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