Microsoft Remote Desktop Mac client not working after upgrade to 10.8.0 error 0x3000064
Hi,
I am using Microsoft Remote Desktop Mac client ( https://apps.apple.com/fr/app/microsoft-remote-desktop/id1295203466?mt=12 ) everyday to connect to remote app hosted on Windows servers.
I upgraded to 10.8.0 this morning and the app does not connect anymore. It throws error code 0x3000064
It fails both when using imported RDP file, and when using Workspace connection.
OS: MacOS Catalina 10.15.7
Regards,
Aurélien
55 Comments
- aureliendcsystemsBrass Contributor
Hi AndyLinker
I can confirm that the issue I reported 2 years ago on 10.8.0 has been fixed in version 10.8.1 (build 2048).
Maybe you can try the suggested solution : install an older version from https://aka.ms/rdmacbeta
And then report your case here if there is a regression between the current version and an old one.
- AndyLinkerCopper Contributor
Is this thread actually monitored by MSFT/Apple? This is an invaluable tool for business and not being able to use it is frustrating.
0x4 error - I can't escape it... Nothing on my server side changed - this worked yesterday and now does not. Uninstalling and re-installing the current version, an older version, a beta version? same outcome today. Dead in the water. I can connect to Win10 and Win11 clients, but not Windows Server (2019)
- keson-echCopper Contributor
This issue seems to be unresolved and it is becoming a pain in ....
The last version of Mac RDP client that worked was Version 10.7.9 (2011).
Since then nobody in our company can connect for longer than 10 minutes - while using any of the following official clients, until today, the Version 10.9.7 (2198) still does not work.
Have been waiting for a fix by MS for nearly two years and there still comes no solution.
It is very embarrassing to keep repeating to our users that they must not update their beta version of RDP clients.
Does anybody have even an unofficial solution?
Tested on all RDP Mac clients since 10.7.9 till todays 10.9.7, several Mac OS versions till latest Sonoma 14.4.1. The RDP sessions disconnects randomly several times a day. The last working client is rock solid, keeps connected for 24 hrs easily.
The same RDP client works great agains pure/plain RDP/TS servers, but does not work agains remote desktop gateway with a KEMP Load balancer.
If there is someone who needs more details for investigation, I can post any versions or logs available.
- Bosco688Copper Contributor
Same issue here.
Error code: 0x3000066
Target: Windows Server 2019 farm via Remote Desktop Gateway
RDP client on Mac: Version 10.9.4 (2161)
macOS: 14.1.1 (23B81)
Client version 10.7.9 (2011) is working. Problem starts with version 10.8.0 (2017).
Btw: the setting
"ClientSettings.DisableOnPremWebSocketGateway" = true;
does not help 😞
- JudiFlournoyCopper Contributor
Same issue for me. Latest RDP or even any earlier version as in 10.8.x do not work.
MacOS Ventura 13.5.2
Error code: 0x300005b
Interestingly, I can access the AVD if I go through the browser (Safari) from the same machine using this: https://client.wvd.microsoft.com/arm/webclient/
I do not have the McAfee firewall on.
Any suggestions?
- HHD_SoftwareCopper Contributor
Hi there,
same for me. After Update to Ventura 13.5 there is no connection to the RDP Clients.
- BViensCopper Contributor
I'm new to all of this. I've never used the RDP app before so this is my first set up and I got the Error code:0x3000064. I contacted tech at my job to see if they could give me some insight, they told me to google the code and I found this chat. I tried the suggestion above to download the old version of the app (10.7.9 (2011)) and then I got a different error code:0x3000066.
I'm not very tech savy, nor a fluent MAC user, but I'm just looking to see if someone can tell me what else to try so that I can make this work asap!
Thanks!
- emoy88Copper Contributor
John_Spencer the latest release, 10.8.4 (2108) still does not remedy the issue.
- emoy88Copper Contributor
John_Spencer Tried the latest release, 10.8.3, and still get the error.
- emoy88Copper Contributor
John_Spencer the latest release, 10.8.2 (2087) also does not remedy the error.