10.7.4 slow compared to 10.7.3
After upgrading to 10.7.4 on the Mac App Store, my remote desktop connection is very slow - clicks take several seconds to respond etc. I am using a gateway and a wired ethernet connection (getting 200Mbps down, 25Mbps up with the data center that hosts the machine I remote into). I am certain the issue is with 10.7.4 build on the App Store because I uninstalled and I manually downgraded to 10.7.3 client (https://install.appcenter.ms/orgs/rdmacios-k2vy/apps/microsoft-remote-desktop-for-mac/distribution_groups/all-users-of-microsoft-remote-desktop-for-mac) and the rdp connection is fast again. All the settings are identical between the 2 clients. I can also confirm if I run Parallels Desktop and use my Windows 10 VM and then use the native windows remote desktop client, it also runs fast. I've seen this before with previous builds though I don't recall which ones were fast/slow. I noticed in the release notes on the App Store that some changes were made with gateway load balancing but those seem to be detrimental in my case?
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.
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 (https://learn.microsoft.com/en-us/answers/questions/1379185/local-printer-redirection-to-remote-desktop-(for-m). 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.
Microsoft Remote Desktop for Mac Beta - shift+scroll(Mouse) doesn't work
When connecting to a Windows or Centos Server, the horizontal scroll operation using mouse wheel can't be recognized correctly. For example, when pressing and holding the "shift" key, scroll up and scroll down operations are both recognized as scroll down operation.
DevBox: Windows App Default to High-DPI Mode
Consider updating the Windows App to automatically detect when its being used on a high-DPI display and automatically enable High-DPI Resolution mode before connecting to the DevBox. Until recently, I didn't know the option in the Advanced menu existed and had just accepted that the Remote DevBox text was blurry. However, once enabling the High-DPI mode the text was nearly crystal clear! A much better experience. This indicates a discoverability issue. If defaulting it to on may impact latency, consider at least warning the user the first time they connect that the option is available for them to use.
