Chrome Remote Desktop

What To Do If Chrome Remote Desktop Stopped Working

Updated on:  

Chrome Remote Desktop

Upon installation, Chrome Remote Desktop (CRD) is an RDP tool that enables users to remotely access data (like files and programs) via an internet connection. Just like many other remote desktop solutions, a code is required to link two computers and enable sharing options between them.

Unfortunately, sometimes users face issues like: Chrome Remote Desktop can’t connect, or Chrome Remote Desktop not installing… and this can be incredibly frustrating.

In this article, we’ll uncover several Chrome Remote Desktop troubleshooting issues (such as why Chrome Remote Desktop won’t connect), and how to resolve them.

Learn all about how to use this RDP on your Windows, Chromebook, macOS, Linux, Ubuntu, iPhone, iPad, or iOS device below.

Chrome Remote Desktop

Some Common Reasons Why Chrome Remote Desktop (CRD) Won’t Launch After Installation

There are a few reasons why your Chrome Remote Desktop not starting may occur. Below we’ll cover four of the main issues that users could encounter, regardless of whether their Chrome Remote Desktop not working (Windows 10 version), or Chrome Remote Desktop not working on macOS version.

Issue 1: Certain devices don’t use the PIN code function to connect.
Solution: Simply disable the option to resolve this issue.

Issue 2: The Chrome Remote Desktop (CRD) app doesn’t have “permission”.
Solution: Resolve this by granting permission/access to CRD.
(Note: Prior to using Chrome Remote Desktop, login as Administrator. Chrome Remote Desktop can’t function without a strong connection and sufficient bandwidth).

Issue 3: Connection issues with IPv6 servers.
Solution: Users can force computers to use IPv4 only when struggling with IPv6 server connection issues. Setting “IPv4-only” should resolve the problem.

Issue 4: Currently, Chrome OS on Chromebook is still in development.
Solution: If a user encounters their Chrome Remote Desktop connection not working, updating the OS to the latest version may help.

These solutions should help you resolve many of your CRD issues- even when using less common platforms like Ubuntu, Linux, iPhone, iPad, and iOS.

Chrome Remote Desktop Not Working: Disabling “Connect Without A PIN” Feature

The RDP Chrome Remote Desktop app provides an option that allows users to connect to a computer from a mobile device (TeamViewer can do this too, but it’s not free.) This feature makes accessing work or personal computers easy, regardless of where the user is.

Users must enable the “Some devices can connect without a PIN code” option in order to take advantage of this mobile feature. Unfortunately, this function can cause- you guessed it- more issues with Chrome Remote Desktop not connecting.

To resolve this issue, the first step is disconnecting, then attempting to reconnect again. See below for a step-by-step process:

Step 1: On the host machine (be it macOS or Windows), go to the official Chrome Remote Desktop website. Search for the name/title of the host device.

Step 2: Hit the View / Edit option (located next to “This computer is configured to allow one or more clients to connect without entering a PIN”).

Solve the Chrome remote desktop not working issue title

Step 3: Click Delete All. This removes all saved devices with current access to your host machine without requiring a PIN.

Step 4: From the Remote Desktop app, go to “Remote Support” and then click “Share”.

Step 5: A new pop-up window will appear, showing the PIN needed to connect with other devices. Enter the new PIN and verify the remote office is functioning as it should.

Google Remote Desktop Won’t Connect? Try Granting Permissions

An additional Google Remote Desktop not working issue may be due to the application lacking the necessary permissions. When utilities attempt to transfer control over a computer to another device, Windows will request permission automatically.

If the user can’t find the permissions window, it might be in the background of a currently open window.

Chrome Remote Desktop Not Starting Properly: Disabling IPv6

Many find that disabling IPv6 (Internet Protocol version) on their network adapter is a sufficient solution. Windows prefers IPv6 servers over IPv4 by default, but users can force their computer to use IPv4 servers if they’re having issues with IPv6 connecting.

Step 1: Open Settings -> Network & Internet -> Ethernet -> Change adapter settings.

Step 2: On the adapter you want to disable, right-click and choose “Properties”.

Step 3: Find the Internet Protocol Version 6 (TCP / IPv6) check box, then uncheck the TCP/ IPv6 checkbox).

Step 4: Hit OK and restart the computer.

Using The Chrome App

Google launched a website (functioning via an extension) in addition to its desktop connection app.

Chrome Remote Desktop App

The Chrome extension allows users to install, view, control, and modify a Chrome Remote Desktop native client from a web-based UI. While still in beta, this extension is considered much easier to operate.

Step 1: Visit the Chrome Remote Desktop website, and hit the Download button under the Remote Access Settings tab.

Step 2: When the extension store opens in a new window, hit Install.

Installing Chrome Remote Desktop Add-on to solve the issue

Step 3: Once the extension is installed, go back to the Chrome Remote Desktop site.

Step 4: Click the “New Extension” icon (displayed on your bookmark browser ribbon).

Step 5: Hit the remote support button to access other devices using a PIN.

Chrome Remote Desktop Is A Great Free RDP Solution

For most users, Chrome Remote Desktop is the easiest cross-platform RDP tool. While users might encounter issues here and there, troubleshooting is usually simple and fast.

While Chrome Remote Desktop might need a bit more effort to initiate properly, it boasts a reliable connection, and when issues do arise, they’re few and far between.