Remote Desktop for Mac 10.9.4 often causes spinning wheel of death when copying from Windows machine
Starting in the last version or two, I frequently get the "spinning wheel of death" after using Remote Desktop for Mac to copy from the remote Windows client. This manifests when I switch back to the mac and try to switch to Slack -- Slack will be frozen for 30 seconds to several minutes with the colorful spinning pinwheel. Many people have been experiencing this issue, both recently and in the last several years: https://vyebmmo1fw.proxynodejs.usequeue.com//t5/azure-virtual-desktop-feedback/copy-and-paste-from-microsoft-remote-desktop-to-mac-causes/idi-p/3947326 https://vyebmmo1fw.proxynodejs.usequeue.com//t5/azure-virtual-desktop-feedback/microsoft-remote-desktop-for-mac-copy-and-paste-works-a-while/idi-p/3930905 https://pm6jzr2ps1.proxynodejs.usequeue.com/en-us/answers/questions/565240/microsoft-remote-desktop-freezes-constantly-apple Please look into this, it's a productivity killer. And if there's anything I can grab for you that will help (like a snapshot of a process using the Mac activity monitor) please let me know. EDIT: I just attached a sample and spindump of Slack (the macOS process that gets the spinning wheel of death after copying text on the remote windows machine).
Cannot sign into my DevBox through Windows app
Hi I have recently upgraded the device to macOS 15.0 Sequoia and also upgraded the RDP app to the latest Windows App. However, it seems that the passkey authentication stuck when I am trying to connect my devbox. My hypothesis is that the recent upgrade of company portal supported iCloud-based passkeys across macOS and iOS devices, which does not have to always prompt a QR code for iOS device w/ passkeys to authenticate. Could u pls take a look at this issue? I have tried with Azure DevOps on Edge Mac and it worked like a charm for this kind of scenario.Option to REMOVE mac Windows App menu bar icon
I am being sent to this form when I use formerly RD Client / Remote Desktop Client for mac - Help - Submit feedback. PLEASE add option to DISABLE menu bar icon for Windows App. I have too many icons and Windows App is just adding clutter. I am fine with the Dock icon alone, thank you.Unselecting "Use Mac shortcuts..." in settings does not work.
I have my mac keyboard settings set to use ctrl for copy and paste instead of the command key. No matter what setting I use in the Remote Desktop Client settings, it always passes command through to my virtual machine, whether I press command or ctrl. I simply want to pass my keyboard press directly through! This is very frustrating and makes using certain features in Visual Studio impossible as the only way to get to them is with a keyboard shortcut.Error code: 0xe06 on on Mac Client (not on Windows client)
I get the error message below when attempting to connect to my organization's AVDs from the latest AVD client for Mac. Using the Windows client on Parallels on the same Mac does not have any issue. Why does it seem that the Mac client has different security policies than the MS RD client for Windows? We couldn't connect to the remote PC because it is configured to use legacy RDP security with FIPS algorithms which are considered insecure. It is highly recommended that the remote PC be configured to use Network Level Authentication (NLA). Contact your network administrator for assistance. Error code: 0xe06
Years long issue of Date Modified on Mac set to 2076
Hi, I have not reported this before, as I had seen posts discussing the issue I will describe. I assumed the oddity would disappear, but it never did during the couple of years this has been going on. When I save a file to a shared folder, from within a remote PC desktop to my local disc on my Mac... the resulting file seemingly always gets a Date Modified set to 29 Nov 2076 at 09:54. It is a small irritation, but over the years, I have become pretty bitter of it persisting as it does. I am not a fan of Microsoft, and am reluctant to give feedback, as I see others have mentioned this without any effect. This has been across different laptops I have had, differens Mac OS iterations and obviously multiple versions of the Microsoft Remote Desktop App What is this kind of bug actually? Something is stamping those files with that one date and time, stuck in the future...Can't see my local printer on the connected Remote Desktop (Windows app on macOS)
I cannot see my printer on the remote desktop I connect to. The Printer redirection setting is enabled in the Windows app, and it worked with the same settings under an older iMac running Monterey. After upgrading to a MacBook Air M1, I can no longer see my printer when connecting to a Windows Server 2012 R2 system. Environment: Local Device: MacBook Air M1 running macOS 15.3.1 Remote Desktop Client: Windows App (11.1.2) from the Mac App Store Printer: EPSON L6290 with latest drivers and firmware Remote Server: Windows Server 2012 R2 Troubleshooting Performed: Confirmed printer redirection is enabled in the Windows app settings Verified that the printer works correctly with macOS Tested connecting to a Windows 11 laptop instead of the server, and printer redirection worked properly Previously used the same Windows Server 2012 R2 with an older iMac running Monterey and printer redirection worked correctly Downloaded an older version of the Windows App (older than v10.9.4) and was able to see the printer on Remote Desktop, but could not print (possibly due to Apple removed PSNormalizer in the Sonoma update) After some research on this issue, I discovered a Microsoft Learn post stating that printing from Remote Desktop broke after updating to macOS Sonoma (link). According to the thread, the problem was supposedly fixed in Windows App v10.9.4 (2160). Based on my testing, this fix appears to be partial: Printer redirection works perfectly when connecting from my MacBook Air M1 to my old laptop running Windows 11 with remote desktop enabled but not working when connecting to a Windows Server 2012 R2 Could this be a specific issue with Windows Server 2012 R2 that wasn't fully addressed in the v10.9.4 fix? Are there any workarounds available for this specific scenario with Windows Server 2012 R2, will there be fix/patch for the WIndows app? This is very important for me because of my job, and I hope this issue can be fixed with an app update, as our company probably won't update the server because of this.
