Microsoft Remote Desktop Mac Not Working
Marcelo Eichel
Using Mac OS X 12.6.8 and Remote Desktop 10.9.2. Beginning two versions back (10.9.0?), copy and paste works for a while after launching RD, but it eventually fails when copying from the remote machine to the local Mac. The failure manifests as a spinning beach ball in the application I'm pasting into. The paste operation eventually times out, but the quickest way to recover is to quit Remote Desktop and start the whole operation over again with the copy.
I can confirm this is happening in our organization as well. It doesn't matter if it's a single word or a 500 rows of information from a SQL query results. Both copy/paste results in a failure to paste the test from the remote desktop into Mac application and a spinning wheel/beachball.
I have been experiencing this issue for almost 2 years already, the only way I have found to restore the ability to copy-paste is by copy-pasting from the remote desktop to the remote desktop, and then trying to use this function from outside to inside the remote desktop (or the inverse). Not sure if this is exactly the same issue, but I think it is worth a try.
I've been seeing this same issue for the past few weeks. I'm using Mac OS 12.7 and RDC 10.9.3. It started when I updated RDC a few weeks ago and hoped that one of the bug fixes since then would have fixed it but the problem is continuing to happen. I get a beach ball when copying from a Windows environment and pasting the content into various Mac apps including Text Edit, Slack and Chrome. It happens at least once per day. It could work five times in a row normally and then suddenly, I get a beach ball and the app I'm trying to paste into becomes non-responsive for about 30-60 seconds. It will typically clear and then start working again for me.
This continues to happen and even seems to be getting worse. If it's significant, I'm nearly always copying from Microsoft SQL Server Management Studio on the Windows computer and pasting into an application on the Mac. I have seen the issue when pasting data copied from other applications as well, so it's unlikely that SSMS factors into the issue in any way.
I'm finding now that only some Mac applications get the spinning beach ball whereas others keep working. Slack is the biggest culprit. Simply clicking on the Slack application after having been using RDC will trigger the beach ball for a minute or two. While that's happening, I can usually use Chrome or other apps on my Mac. RDC also remains usable during this time.
I'm now using RDC 10.9.5 (2179) and the latest Slack app (4.36.136) and it keeps happening at least once per day when switching from RDC to Slack, whether or not I've explicitly just copied something or not from within the RDC client.
@DaveB_CT I've had Slack get the spinning beach ball as well, but at first I did not associate that with RDC because I wasn't pasting into Slack. This condition in every other application is triggered by trying to paste from the clipboard. I now think Slack is a victim of this RDC bug. I suspect the problem is still only clipboard related, so it makes me wonder what Slack is doing with the clipboard. Does it retrieve the contents every time it's brought to the foreground? Apparently it does; I just found this which offers a way (from Slack support) to disable this behavior.
Same issue. I average probably 2-3 hours per day on RD with frequent copies in/out of the client. I've had it happen when copying from RD to Chrome and Sublime. Today, I have gotten the beachball of death 4 times. MacBook Pro M3, everything up to date.
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:
I also have issues with the client on macOS. On the windows client you can specify the resolution and color depth that you want to connect and have a wide range of options. This allows you to be able to use the client in low bandwidth situations.
The macOS client is unusable in low bandwidth situations since you have very limited options when it comes to setting the resolution and color depth. The resolution defaults to "default for this display" and it cannot be changed, which is 4K in my case. Lowest color depth is 16 bit which is too high.
I'm having similar issues with my new machine (MacBook Pro M3 Max) when multiple monitors are connected. Every 10-15 seconds, video and input for the RDP connection will freeze for a few seconds. No issues with my previous i9 MBP, and I've ruled out connectivity or other possible issues.
Hi, having similar issues when I have dual monitors connected. My mouse and keyboard that are connected through my docking station (same station that the monitors are plugged into) does not work when I have the Remote Desktop app opened across both screens. When I change the App to only be displayed on one screen the keyboard and mouse work.
Describe the bug
I set up 3 finger swipe down for keyboard shortcut "Crtl + W" (or ^ W). When I trigger it in Microsoft Remote Desktop 10 client, it triggers successfully (I have feedback setup as well), but only the key "W" goes through. So each 3 finger swipe down results in typing a "W" instead of closing the current tab (via Ctrl W).
Additional information (e.g. StackTraces, related issues, screenshots, workarounds, etc.):
I looked up this issue and found this Github issue which indicates it should be fixed by v2.353. I'm running v3.086 and have enabled "Shortcut sending compatibility mode", but am still not able to get it to work.
Note: Before bug reporting, please make sure you have the latest version of BetterTouchTool and that you have already tried to restart your system :-). If you encounter a crash, please attach a crash log from the macOS Console.app from the "User Diagnostic Reports" section.
Still experiencing this same issue.
I used to love BTT when I had my old mac. I spend much of my day working in Amazon Workspaces doing development for work. Therefore, I bought a new BTT license with the goal of creating many automations that would help my workflow.
However, I am experiencing the same issue as described above, namely that modifier keys are not passed through to the remote machine.
e.g.
two finger tip-tap-right mapped to Ctrl-C only passes in "C". This is the same issue with all modifier keys.
It seems that the same bug has been opened for many different remote desktop applications and use cases. See below:
Thanks for the quick response and explanation. Unfortunately, neither of those two workarounds solved the problem for me. Out of curiosity, why is it able to send the non-modifier keys if it's unable to handle programmatically created events?
I think I might have found some obscure way to send the events in a way that is handled correctly by at least the Microsoft Remote Desktop :-). I'll need to do more testing though as it's currently pretty fragile.
I got a Mac Studio (Sonoma) couple of days earlier and for the last 2 days I am trying to connect to this machine using Microsoft remote desktop (MS RD) from my another Mac air ( Ventura) . Both the machines are in the same network for testing purpose. I did all the set up like having the latest version of MS RD downloaded, enabling the Remote Login, Remote Management and port forwarding in the SP router etc. I am able to ping this machine from the other laptop also I could use the ssh command to connect to this machine using the terminal. I can connect to this machine using VNC but not with MS RD. I tried everything I can. Any one could help or suggestions. FYI there is a reason I need to user MS RD else I could have used other apps including Apple Screen Share.
Also Screen Sharing is lousy at copy & paste with 3rd party VNC servers. Works great Mac to Mac, but as soon as you try to connect with a Windows, Linux, or other 3rd party VNC server, copy & paste becomes an issue. TigerVNC client does a better job of copy & paste in a VNC environment.
We have users in the company I work for that often use Microsoft Remote Desktop Connection to Windows systems running in the cloud. Most of the company is on Ventura (Sonoma has not been approved by the company IT just yet; need to get all the company mandatory software working first to keep the lawyers happy).
So if Microsoft RDC is not working on Ventura, then I would look for either issues with the Windows system accepting RDP connections, or something in common with the Macs, such as company Anti-Virus software, or company mandated firewalls, etc...
Thank you all for the quick response. Forgot to mention the Mac Studio (Sonoma) will eventually be accessed from windows machines. Only for testing purpose I just used another mac in the same network . I did try VNC but the performance is too slow especially when accessed from a Windows machine. I will have to make MS RDC work somehow ,since 2 users might simultaneously login in to the Mac Studio from a windows machine.
It does work when i go to the office start Pix4D & open raycloud, go home and take over the machine.
I would really like to see a solution which enables me to start Pix4D & specially raycloud from home without 1st going to the office start Pix4D & open raycloud.
Hi, thanks for your insight.
Can you explain me why it works when raycloud is active on the workstation and I take it over from home through windows remote desktop, it shows the 3d graphics no problem.
But when I close Pix4D or start a new session everthing works untill I need to open raycloud.
Also using Agisoft, 3D graphics through windows remote desktop, No Problem.
Hexagon 3D Reshaper, 3D graphics No Problem.
I dont know what viewers or codes those other softwares use but Pix4D uses OpenGL which is one of the better optimized viewers, it runs better and faster than DirectX. OpenGL is what is causing the problem because RDP does not allow OpenGL viewing. I am not sure if changing the group policy will help fix that.
d3342ee215