Screen artifacts after upgrade to Version 10.8.2 (2057)
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
macOS 'native' app consuming too much memory/GPU (Apple Silicon)
Dear Microsoft, Ever since the launch of the Apple Silicon machines, macOS users have been using the macOS native app of Teams via Rosetta 2. Due to that, the application is consuming a great amount of memory when compared to the Edge PWA of the Microsoft Teams web app. In my day-to-day I can notice that the Microsoft Teams app is in total consuming 2,10GB, however, if I hop into a call that number increases to 3,10GB.. If the video camera is turned on it goes beyond 3,30GB. Besides memory, there's also the battery life component where teams are my highest energy usage app on my Macbook Pro 14" with the M1 Pro chip. due to that my battery life only lasts up to 5-6 hours maximum. Additionally, I noticed during a video call my M1 Pro (GPU) is being used by around 80-90% when using the webcam. I understand developing a 'Universal App' takes time but I would like to ask ahead of the 'Performance' event what are your plans for the macOS users because we have been enduring this for the last 2 years ever since the M1 machines come out. Could you possibly let us know of a possible Beta Preview version of a universal app or an up-to-date Electron version that supports performance improvements? Please point me in the right direction so I can upload logs/stats regarding performance to further help you improve the product and assist the development team if needed.
Mac Remote Desktop Crashing When Copying
Hopefully this is the correct place to post this now that the UserVoice website has been shut down. The latest versions of Remote Desktop for Mac have introduced a regular freezing problem when copying anything within a workspace. This is particularly bad in the Remote Desktop Beta, which we've currently abandoned, having used this for the last few years, and occurs quite regularly in the App Store version. Force quitting and then relaunching does at least retain the workspace, but until the force quit there is no interaction, just the blue spinning circle. This is on a 16Gb M1 MacBook Pro connecting to a Windows 2019 RemoteApp server.Microsoft Remote Desktop Beta for Mac Cannot Screenshare or Screenshot
macOS Monterey 12.0.1 on a new 14" M1 Pro MacBook 14" Microsoft Remote Desktop Beta (MRD Beta) will allow sharing of the Connection Center window in Zoom, Teams, etc. but not an active workspace, instead displaying a blank white screen on the remotely connected computer. Also, screenshots using any of the standard Mac keyboard shortcuts or using Preview will not display the MRD Beta in the screenshot/file created, instead showing whatever is behind the workspace window. All of the above works for MRD downloaded from the Mac App Store. Both the App Store and Beta versions have identical settings in System Preferences -> Security & Privacy -> Privacy. 'Allow apps downloaded from' is set to 'App Store and identified developers'.
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?
Microsoft Remote Desktop Client Mac crashes when joining a teams call on an Azure VD
Since the update to Version 10.7.8 (2006) of Microsoft Remote Desktop Beta and Version 10.7.8 (2006) of Microsoft Remote Desktop, every time I join a Teams call on my Azure Virtual Desktop through the client, the client immediately crashes as I enter the call. Running Mac OS Monterey v12.4 on a 2020 MacBook Pro 13 inch. Update 26th July @ 10:26am GMT: I have found this only happens when the camera is enabled. If the camera is disabled the call progresses correctly.
Black screenshot Remote Desktop Beta
Hi, I'm using Microsoft Remote Desktop Beta (Version 10.7.1 (1942)) with macOS 11.6 (20G165) I'm experiencing a problem when I want to take a screenshot inside a Remote Desktop session. The screenshot taken is always full black, wether I take it on the desktop or in the paper board. This problem has never happened to me before and it is very annoying. I tried using the former version of Microsoft Remote Desktop (not the beta) and the screenshot works as intentedBUG: Every 10-15mn session crash when using teams in rdp session (error in Network thread)
Hi, Both with Macos Remote Desktop (10.7.1) and beta client (10.7.2 - build 1962) my session crashes every 10 mn or so as soon as I use Teams within my remote session. It creates a crash reports in macos console every time under Microsoft Remote Desktop Beta. I am running macos monterey 12.0.1 (21A559) on macbook pro and the rdp session extends on my laptop and secondary display. The report contains: Crashed Thread: 28 network_thread 0x0x7fad3ea91cc0 Exception Type: EXC_GUARD Exception Codes: GUARD_TYPE_USER Exception Codes: 0x6000000000000012, 0x0000000000000002 Termination Reason: Namespace LIBSYSTEM, Code 2 Application Triggered Fault Thread 28 Crashed:: network_thread 0x0x7fad3ea91cc0 0 libsystem_kernel.dylib 0x7ff818dd8d86 os_fault_with_payload + 10 1 libsystem_kernel.dylib 0x7ff818dd9905 __darwin_check_fd_set_overflow.cold.2 + 31 2 libsystem_kernel.dylib 0x7ff818dc2984 __darwin_check_fd_set_overflow + 68 3 WebRTC 0x10595f149 rtc::PhysicalSocketServer::WaitSelect(int, bool) + 505 4 WebRTC 0x105966d0e rtc::Thread::Get(rtc::Message*, int, bool) + 846 5 WebRTC 0x105965cae rtc::Thread::ProcessMessages(int) + 286 6 WebRTC 0x105967849 rtc::Thread::PreRun(void*) + 73 7 libsystem_pthread.dylib 0x7ff818df1514 _pthread_start + 125 8 libsystem_pthread.dylib 0x7ff818ded02f thread_start + 15Remote Desktop Full Screen Orientation bug?
Hello, I have been experiencing an ongoing display issue for a couple months now attempting to render in full screen to a specific monitor in my setup. This is the monitor I use to drive my RDP connection(s) on a daily basis. I am curious to see if perhaps someone else has experienced this issue recently and (if so) is it still an issue. As mentioned below, I do have one immediate thing I can attempt this evening in the form of updating MacOS Ventura. Perhaps the update will correct the issue or it is a misconfiguration that is an oversight on my end. Either way, I wanted to go ahead and document the issue. As for anyone taking the time to read this, thank you kindly for your time. Issue Going fullscreen on external display forces the desktop to render in portrait. However, it is not a traditional portrait mode. The screen is just rotated 90 degrees clockwise cutting off portions of the display that extend beyond the height of the monitor resolution. The rest of the display is black where the desktop would normally be rendered. There are a few things to note: This cropped up several months ago in both RD and RD Beta. It does not happen when I am not docked. This happens regardless if the monitor in portrait mode is plugged into the dock or not. Fullscreen on my portrait monitor renders correctly for its orientation and resolution. Testing each monitor plugged into the Mac one at a time produces the same result Any attempts to grab a screenshot using MacOS or Snagit causes it to render correctly which would require something like a photo from my mobile device to display what I am seeing. Equipment M1 MacBook Pro Currently Ventura 13.0 I will update the OS tonight to see if it resolves the issue, but do note that it was functional on 13.0 at the time the issue began Switched to RD Beta v10.8.2 (2088) with the issue also occurring on the main client as well. OWC Thunderbolt Dock * Produced same results indecently of the dock for each monitor (1 plugged into the Mac at a time) Displays Left: Dell U3219Q (1890x3360 portrait) Fullscreen works no issue Middle: Retina Fullscreen works no issue Right: Dell U3219Q Fullscreen issue occurs Both displays are connected via thunderbolt cables to the thunderbolt dock and one thunderbolt cable from the dock running to the MacBook. This is also the power delivery Host Machine Windows 11 Pro 10.0.22621 Intel NUC 10 NUC10i7FNB Cor i7-10710u 64gb 2333 ram Intel UHD Graphics 1gb Ethernet is the primary adapter Both machines are connected via Ethernet Wi-Fi 6
