Chrome Remote Desktop failed installation on MacOS Ventura

Question

Chrome Remote Desktop failed installation on MacOS Ventura

This is an issue already mentioned in one of the previous posts of this community but it doesn't work apparently. So I am here to give the updated solution as the existing one seems to not accept any further reply.

First of all, here's the existing post:

Chrome remote desktop not working on Mac - Apple Community

The solution to this one will to first install an older version of CRD and then install the new one directly from the CRD website. For older version here's the official Google's hosted URL:

https://dl.google.com/dl/chrome-remote-desktop/chromeremotedesktophost-47.0.2526.18.dmg

[This is a Direct Download Link]

Have a good day!

Yogesh Aggarwal

[Edited by Moderator]

Mac Pro, macOS 13.6

Posted on May 30, 2024 9:31 AM

Reply

Answer 1

Top-ranking reply

YogeshDevAggarwal Author

Level 1

11 points

Jun 27, 2024 12:57 AM in response to RichardAVD

Hey this is a generic security warning which can be resolved by going into System Settings > Privacy & Security and then scroll down to bottom. There you will see a button saying "Open Anyway", click on that & it will open.

Reply

Answer 2

Jun 27, 2024 1:04 AM in response to Sky-Girl

Hey mate!

Simply download the older version of CRD from the link I have mentioned in the post & install it. You'll get a security warning like someone else is having here. I have already replied on how to solve it.

After that, the installer will open so just go through it & eventually you'll have an older version of CRD installed on you system. Keep in mind that it won't work just right now.

The next will be to download the newer version of CRD from its web app & then install it.

And ... you are good to go 😉!

Reply

Answer 3

Jun 17, 2024 10:14 AM in response to YogeshDevAggarwal

Hi, thanks for the suggestions.

The new CRD version also won't install on Sonoma 14.5 (using Firefox) and older version of CRD you linked won't open per image below (thought I would try your fix on Sonoma).

Irony is that all was working just fine until I did the update (which it forced me to).

Any other suggestions?

Thanks.

Reply