Microsoft Remote Desktop Error Code 0x204 Mac Monterey
Berry Spitsberg
I am able to remote into my Windows 10 PC fine from another Windows PC. However, when I attempt to remote in from my MAC OS running High Sierra 10.13.6 using the Microsoft Remote Desktop for MAC I get Error Code 0x204. Can anyone help?
On your mac; go to System Preferences -> Network
On the left pane please make sure that your VPN definition is upper than the Thunderbolt Bridge. Somehow Microsoft Remote Desktop app does not work if the VPN definition is below the Thunderbolt Bridge. After I moved my VPN definition as below, I could successfully rdp to my pc.
Bought a new MacBook Air with Apple M1 chip and migrated the MacBook from old to new. VPN and Microsoft RDP worked flawlessly on my old Mac, but didn't work at the new MacBook; exact same settings for VPN and RDP.
in Mac > Settings > Network you see the circle with three dots in the bottom left > set order .... (I have Dutch language, so not sure what it is in English) and change the order to have VPN on top, above wifi/Lan.
This worked for me!
THIS! After months of not being able to use my VPN on my M1 Mac, or even on my Intel Mac once I upgraded to Monterey (Mac OS12), I decided to search one more time on RDP error 0x204, and I found this solution and it fixes the problem. Once you have created the VPN connection and have it saved, and are able to start the VPN connection without any errors, yet RDP is failing with 204, open "Network Preferences..." and at the bottom of the left pane, select options, and then the choice to "Set Service Order...". I had to stop and start the VPN and it changed the order, then I set it again and it stayed in the correct order the second time, with the VPN listed above the WiFi (when it is connected), and my RDP once again works. A huge thank you to Krel-0470 for posting this solution.
I have been struggling with this problem for months, following all the indications found on the net, but to no avail.
Now, with this tip, I solved it quickly and well.
Thanks Krel-0470 for your valuable report.
Hi @Krel
I am having a similar issue. I used smart VPN (Dray tek). I remoted succfully by other pc but exception on mac (Monterey).
I used to change the service order but vpn config is invisibale on the list.
Pls upvote and help me fix that.
I figured it out this morning. When entering the PC name in the Remote Desktop App on my MAC, it worked when inputting the IP Address of my Win10 Pro PC rather than the actual PC Name. For some reason, the App did not recognize the PC Name, even though i confirmed it was correct and added/re-added countless times.
I faced the same problem now in 2024, and I confirm that using the IPv4 address of my remote PC when trying to remotely connect from my MAC instead of the computer name worked perfectly. Thanks! In your remote PC, go to Windows settings > Network & Internet > Ethernet > find your PC IP address scrolling down under "Properties"
I am having the same problem. I running Mac OS11 (Big Sur) on a M1 Mac mini. I am using Sonicwall Mobile Connect to connect to make the VPN connection to my PC at work and that is working. However, when I connect with Microsoft Remote Desktop, I get the 0x204 error. I have unchecked "Use system proxy configuration" and also unchecked "Use hardware acceleration when possible".
I was unable to access the Group Containers or locate the UBF8T346G9.com.microsoft.rdc file. It appears that this has changed in OS11 Big Sur. Also, the Network Utility no longer exists so I am unable to verify the port. Apparently this can still be done through the Terminal, but I have no knowledge of how to do this.
I am able to VPN in and use Remote Desktop from my home on Windows PC to get into my work computer, so I know that the computer at work is set up correctly and that my router at home is not blocking the connection.
I am having the same problem with the Remote Desktop app and the suggestions above. It does not seem to fall into the same structure. I need to access a RDS through my phone's hotspot through a whitelisted IP address. This address changes and I change the allowed IP each time, but the Remote Desktop app will not connect and I get error code 0x204.
I have the same mac computer and mac os. Seems that my mac side is ok since I can connect to a Windows 7 pc on the same network just not my Windows 10 Pro laptop. Just upgraded my key to pro to do this so I am quite disappointed.
Seems like my problem is on the Windows 10 side. I just checked and I can connect W10 to control W7 but not W7 (or Mac) to control W10.
I followed all the instructions to setup the W10 to receive connections. :(
I found Group Containers and UBF8T346G9.com.microsoft.rdc in (Macintosh HD > Users > > Library > Group Containers).
According to troubleshoot above I had to delete the folder, restarted application, still couldn't connect error 0x204.
I also try to connect using OpenVPN, I can see other networked devices and the server does respond to pings, so I'm almost certain it isn't the VPN.
Once in office I will try to check from local network without a VPN.
Note: It's worthy to mention that error code 0x204 may also appear on the iPad. Please check if you are using the latest version of the Microsoft Remote Desktop app. You can uninstall the app and reinstall the latest version and see if that helps in resolving the issue
There are five solutions to fix Microsoft Remote Desktop error code 0x204. You need to enable a remote connection or edit firewall settings on your Windows 10. Besides, you need to enter the IP address of Windows 10 instead of entering its PC name. Additionally, you can delete the Remote Desktop temporary files from Mac. If the issue persists, open port 3389 on both devices.
Actually, you have multiple options to remotely control another computer. For example, you can use Chrome Remote Desktop from Mac to Windows. Or if you are looking forward to finding free yet professional remote desktop software for Windows, you can use AnyViewer, which can provide you with stable and fast unattended remote access.
This error is triggered whenever you try to use your Mac to access your Windows computer using the Remote Desktop client. The user is not able to connect remotely to the target computer and gets this error instead.
Another reason why you might be getting this issue is because of your Firewall since it is in charge of monitoring all incoming connections to your Mac. If you need to connect to your PC multiple times, then you need to establish an exclusion for your Firewall to allow Remote Desktop. If it is a one-time occasion, you might consider temporarily disabling your Firewall and security software. However, remember to turn it back on immediately after the activity to ensure your device remains protected.
There are instances when the Mac error code 0x204 Remote Desktop occurs because of corrupted temporary files located in the Group Containers folder, preventing the client from functioning properly. Deleting the UBF8T346G9.com.microsoft.rdc folder should help resolve the error.
By default, Windows Firewall is not set up to whitelist the Remote Desktop Protocol. Hence, your Firewall will try to stop the connection every time you try to connect. So if you want to access your Windows files from other devices, you need to modify your firewall settings to allow Remote Desktop and Remote Desktop (Websocket).
Creating an offline invitation using Remote Assistance on your Windows computer is another workaround for this error. This can be a useful approach if the issue relates to specific network port restrictions. To do this:
If you are getting the error code 0x204 only on your Mac, then it is possible that the files related to the Remote Desktop Protocol have been corrupted, preventing you from establishing a connection with your Windows PC. Deleting the temporary folder should clear this issue. To do this:
The information provided in this article is intended for educational and informational purposes only. It does not constitute professional advice and should not be used as a replacement for professional technical support.
Welcome to this blog about configuring Azure Virtual Desktop session host with Microsoft Intune. The Intune settings catalog is growing very fast and now also AVD settings making it to the settings catalog.
The Intune settings catalog is the main place to find settings that are deployed to endpoints. You may see the settings catalog as the on-prem Active Directory group policy management.As mentioned more and more settings comes to the new way of managing endpoints. And now AVD specific settings are too.
RDP Shortpath is a feature of Azure Virtual Desktop that establishes a direct UDP-based transport between Remote Desktop Client and Session host. RDP uses this transport to deliver Remote Desktop and RemoteApp while offering better reliability and consistent latency. For a complete overview please check the Shortpath overview.
In the test, I added the default settings to the policy. Thereafter I started a Windows 11 machine in Azure (comes from a public network) and tried to open a session to AVD with the Remote Desktop Client.As you can see, the UDP ports are blocked by the Defender Firewall.
Watermarking, alongside screen capture protection, helps prevent sensitive information from being captured on client endpoints. When you enable watermarking, QR code watermarks appear as part of remote desktops. The QR code contains the connection ID of a remote session that admins can use to trace the session. Watermarking is configured on session hosts and enforced by the Remote Desktop client. (Source Microsoft)
NOTE: The official macOS remote desktop client, as the beta version, does not support water marking yet. The official client shows an error like below. The beta version, starts but shows a black screen only.
The screen capture protection feature prevents sensitive information from being captured on the client endpoints. When you enable this feature, remote content will be automatically blocked or hidden in screenshots and screen shares. Also, the Remote Desktop client will hide content from malicious software that may be capturing the screen.Earlier I wrote a post on how to enable AVD screen protection automated.
d3342ee215