Same here, at first I thought it was Slack as that hung first. No idea what would be causing this, it doesn't seem to affect anything else so can only assume they're both requesting a resource or something incorrectly and causing a clash?
Remote Desktop for Mac - freezing issues with slack
I'm having issues on macOS Big Sur Version 11.6 (Intel Core i& Macbook Pro) and Microsoft Remote Desktop.
I get conflicts when using slack and the remote desktop together. I've found that Microsoft Remove Desktop causes slack to freeze and then RDP also becomes unresponsive. Is there some type of setting or hardware acceleration that could be causing this to happen? Note, I am underneath a VPN for whatever that may mean.
Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
13 answers
Sort by: Most helpful
-
misteryu 6 Reputation points
2021-12-10T22:20:49.78+00:00 I am also having this issue. I am running 12.0.1 Monterey, MacBook Pro 15 2019
-
Daniel Pervan 6 Reputation points
2021-11-30T13:12:22.337+00:00 We also have this problem. Running macOS 11.5.2. VPN doesn't matter.
Running Slack in the browser is our current temporary workaround.
-
Sergio Pantaleo 6 Reputation points
2021-11-18T09:14:54.36+00:00 I have the exact same issue. It happens all the times on Mac OS (Big Sur 11.6.1) when both Slack and Microsoft Remote Desktop are running. First is Slack to freeze, second is Microsoft RD.
I could partially reproduce it on Windows 10 when I'm connected over VPN, Slack freezes for a minutes or so, then it becomes responsive again.
On Mac OS once it freezes I need to forcibly close both Slack and Microsoft RD.
-
Fiona Lovett 1 Reputation point
2022-01-21T11:26:28.207+00:00 Just here to say I've also been having this issue for as long as I've been using RD and Slack together. It seems to happen most often if I Cmd-Tab straight from my RD session to Slack, but that's not always the trigger.
I am not running a VPN on my Mac.
Quitting RD releases Slack, so I only need to quit that one thing and restart it.
Glad I'm not alone, wish there was a solution.