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://techcommunity.microsoft.com/t5/azure-virtual-desktop-feedback/copy-and-paste-from-microsoft-remote-desktop-to-mac-causes/idi-p/3947326 https://techcommunity.microsoft.com/t5/azure-virtual-desktop-feedback/microsoft-remote-desktop-for-mac-copy-and-paste-works-a-while/idi-p/3930905 https://learn.microsoft.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).
Windows App - Account Picker During Startup
Windows App is showing additional improvements to the overall VDI experience. As an Architect working for a consulting company, I have multiple clients with AVD environments I have to log into. One of the major benefits of Remote Desktop is that when opening, the window provides visibility to all signed in accounts. With Windows App, when opening the application, I'm in the most recent account. To benefit us that work in multiple environments, allow us the capability to choose which account I want to work in when opening the application. If Windows App only has one account associated, it can default to that account. But if there are two accounts present, allow the user to choose which one they want to go into at the onset.
Certificates are cached too aggressively in RD Web Client
We use the https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-web-client-admin (Latest version 1.0.27) Normally it works really well, but then once a year we have to update our SSL Certificates. The problem is the Web Client likes to cache the old certificate and not get the latest certificate. This results in people getting the following error: Hitting F5, Ctrl F5 does not resolve this. The following are the instructions we have to give the AVERAGE USER to get them passed it: * Press F12 to open DEVTOOLS * Press F1 to open DEVTOOLS SETTINGS * Under Networking tick Disable Cache (while DevTools is open) * On the tab, refresh the page with F5. * Close the DevTools tab Luckily these instructions more or less work for every major browser. But I think you can see that no end user should have to do anything as crazy as this. This also makes the move towards certificates with a shorter life impossible. Can this please be looked into with urgency? (Note: I know this is the Azure Virtual Desktop Feedback, but It's what the feedback button in the web client links to. If there's a better place to provide this feedback please let me know)Frequent AVD Deployment Failures
Since June 2024, we have experienced occasional failures in AVD deployments. While most deployments succeed through adding session hosts to the host pool, there are instances where the deployment fails. Given this situation, we would like to request a change in behavior to reduce the burden of recreating AVDs when deployment fails.
Windows Mobile App on Apple Vision Pro and Bluetooth Keyboard
When using the Windows Mobile application (iPad version) on the Apple Vision Pro with the Magic Keyboard, there is an issue. If I switch to another application or window (for example, Safari) and use the keyboard, and then switch back to the Windows application, the keyboard no longer functions. I must click on the virtual keyboard icon, then click again to disable it before the keyboard can be used again.
macOS Windows App Bug Report
Hello, I have two bugs I would like to report to the macOS Windows app development team. When typing fast, it converts characters to other characters, e.g. "or iṡit all" I had typed "or is it all" Teams app microphone doesn't work until I quit out of Windows app and reopen it. Sometimes I have to do it multiple times. Sometimes I have to complete quit out of Teams inside the Windows app and reload it. Sometimes I have to restart the Windows app CloudPC. Sometimes I have to restart both my host macOS system and the CloudPC system.Something is preventing you from using Windows App right now.
After being auto-updated from Windows App version 2.0.327.0 to version 2.0.328.0, some of our users can't launch their Windows App anymore and get an error message says: "Something is preventing you from using Windows App right now." Since there is no way to control the update process, we could only let our desk users use MSRDC instead, as a temporary solution. For the frontline users, I could only pray that this problem will not take place until weekend. If any Microsoft person sees this post, please let the Windows App team know about this and fix this problem ASAP.Issues when using RD client on iPad with hardware keyboard
I’m using a 2022 iPad Pro m2 with Magic Keyboard on iPadOS 18, when I’m connected to my laptop, my keyboard doesn’t work at all unless I click the keyboard icon on the right side of the screen, which is usually for the onscreen keyboard and f-keys. I didn’t need to do this in the older versions of RD client, would be pretty annoying if a keyboard bar and a control dot have to pop up even I’m using a hardware keyboard. Also when I’m trying to type Chinese, it would use iOS’s Chinese input method instead of Windows Chinese input method, which is also really annoying and buggy especially in iOS 18 which the word selector wouldn’t show up at all. Would be really nice if Microsoft could solve these issues!
Bug: Microsoft Remote Desktop on Mac Hangs when copied a large file on remote desktop
I've found a bug that happens to hang Microsoft Remote Desktop on Mac quite often. With shared clipboard enabled (It might also reproduce without shared clipboard, but I didn't try it): On the remote desktop, copy a folder or solution that is fairly large. It doesn't need to be multiple gigabytes, but tens of MB usually can do the trick. Then, switch back to your normal desktop. Once I do this, my Microsoft Remote Desktop now pinwheels and hangs, and I must force quit it and restart it in order to access my remote desktop again.
