Microsoft Remote Desktop Mac client not working after upgrade to 10.8.0 error 0x3000064

emoy88 

To help us triage can you please collect some traces. Set the core log level to "Information", then start logging and repro the issue. Please send the logs to mailto:rdios@microsoft.com please. Thanks

I just downloaded it again and it worked!.  I think i installed the wrong version the first time 😕

Thanks!

I get the same error after installing the beta build.  I need to work!

John_Spencer tried this and got this error.

Hi Michael Hendrickson emoy88 RBT05 Roman_Mondek aureliendcsystems ,

Can you please try out the new beta build for version 10.8.1 at aka.ms/rdmacbeta and let us know if it resolves this issue? 

Thanks!

We are continuing to have problems with 10.8.0 on our University campus. The solution proposed today is not working for us. While away from the campus network and connected to the campus network using an always-on GlobalProtect configuration, attempts to connect to any host using its dns name are failing with a 0x204 error, but will connect when using the assigned IP address. They are essentially acting as if the host is turned off. However, attempting to connect to the same host, but with Cisco AnyConnect instead of GlobalProtect, allows us to connect, using DNS or IP address. We've set the defaults spring, with no luck.

Hi John,

Thank you very much for your reply. 

I confirm that both options work in my case.

Aurélien

Hi aureliendcsystems emoy88 RBT05 Roman_Mondek jazar01 and all,

We have triaged an issue and working on a fix! When connecting to an on-prem deployment gateway, the client by default will try to connect via WebSocket first. If the gateway doesn’t support WebSocket then the client will fall back to using plain https channel. Based on logs from users experiencing these error codes on 10.8.0, the issue seems to be happening during WebSocket connection where the client did not fallback properly to https channel and instead thows the error. 

The current options are:

1. As previously mentioned, download the last stable beta Version 10.7.9 (2011) from here: https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Faka.ms%2Frdmacbeta&data=05%7C01%7Crdios%40microsoft.com%7Cbda77ca204e246714d8f08dae261163a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638071203891715197%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=YFvNHTdKLnJOIpt7%2FtyOFr2Rhj1oHt0PTCoFFISESH8%3D&reserved=0 (As the app store doesn’t allow you to downgrade)
2. If you want to stick with 10.8.0 from the Appstore, type this in the Terminal:
   defaults write com.microsoft.rdc.macos ClientSettings.DisableOnPremWebSocketGateway true. 
   The setting bypasses the WebSocket connection attempt and simply connect with plain https channels. Note: Performance-wise WebSocket is expected to be faster than https channels.For deployment en-masse, if you can push policies to the managed macs, we would suggest this option (after verifying it works on your mac). However, if these are not managed macs, then we would suggest option (1) and waiting for an official fix to be pushed to the Appstore (likely after the new year).

Thanks

Same issue

I also have problems with 10.8.0, connecting over a GlobalProtect VPN to a server with a Gateway.

Normally the gateway will send me an Authenticator prompt (on my phone).

When running 10.8.0, the connection fails as soon as the gateway step is reached.

I have had to restore 10.7.0 and turn off automatic updates on my Mac.

MacOS Ventura 13.1   (M1 Mac Mini)