Google remote desktop keeps turning off

This article explains methods to fix Chrome Remote Desktop Not Working/Offline Or Stopped Working issue.

Chrome Remote Desktop, a Google’s Remote Desktop utility, has a clear edge over its competitors owing to its reliability, and easy to use application.

However, just like any other software, it is also prone to errors and issues.

If Chrome Remote Desktop is not working for you or it went offline, there are number of methods that you can use to fix this problem.

It is possible that causes of this problem might be a new update that has rolled out for Chrome or some problems related to your PC.

In this guide, we will go 5 methods to help you fix Chrome Remote Desktop not working issues.

Whether you are on Windows or macOS, you can follow these methods to solve Chrome Remote non-working issues.

Also Check: How to Right Click on Chrome Remote Desktop Session

1. Allowing Permission

For a computer to connect to another computer, the host’s computer requires permission from the user. If the permission is not granted, the user might end up facing this issue.

The window asking such permission is likely to appear while connecting to another computer. You should look for it. You can look for it in the taskbar. It might be minimised.

2. Remote Desktop Chrome Extension

If all of these fixes don’t work out for you, don’t worry you still got a solution.

If you have been using the Chrome Remote Desktop’s application, you can use the Remote Desktop’s Chrome extension to get rid of this issue once and for all.

Step 1: Download Chrome Remote Desktop Extension for Chrome browser.

Step 2: Once you are there, Select Add to Chrome. It will ask for permission once again, continue by clicking on Add extension.

Now you can use this extension to establish a remote connection.

3. Disable VPN

Sometimes, use of VPN with Chrome Remote Desktop causes issues.

So if you are using VPN that is connected on system level, it is recommended to disable it. After disabling VPN, try connecting to Chrome Remote Desktop again.

4. Uninstalling Google Chrome

There is a fair chance that uninstalling Chrome might get this issue fixed.

In order to do this, follow the steps below:

For Windows 11/10

Step 1: Right Click at the bottom left corner of the screen [On Windows 11, right click on Start button]. Then Select ‘Apps and Features’.

Step 2: Now Search ‘Chrome’ and uninstall it.

Step 3: Now visit this location in Explorer:

C:\ Users > [Username] > AppData > Local > Google

Step 4: Find a folder named ‘Google’. Open it and delete the folder named ‘Chrome’.

Step 5: Now all you have to do is download the Google Chrome again.

For macOS

Step 1: Right click on the Chrome icon in macOS dock and click on “Quit”.

Step 2: Open Finder and search for “Google Chrome”.

Step 3: Drag and drop the Google Chrome to trash.

Hopefully, this gets you rid of your problem, if not, we still have some other methods to get rid of this problem.

5. Disabling ‘Some devices cannot connect without a pin’ Feature

This feature lets users connect without any obstacles. If this feature is enabled, it might cause this problem, so we will try disabling this feature to see if it fixes it.

Step 1: Open Chrome and type ‘Chrome Remote Desktop’. Look for ‘This Device’.

Step 2: View/edit option might be under this tab: ‘This computer is configured to allow one or more clients to connect without entering a PIN’.

Step 3: Click on ‘Delete All’.

Step 4: Go to Remote Desktop application and look for ‘Remote Assistance’, then click on ‘Share’.

Step 5: A new code will appear on the screen. Use this code to connect.

Frequently Asked Questions

Is Chrome Remote Desktop secure and safe?

Yes, all the remote sessions are encrypted which implies that your data is safe.

Can Chrome Remote Desktop connect to a system that is sleep?

No, Chrome Remote Desktop cannot connect to a computer or device when it is not online.

Is Chrome Remote Desktop free to use?

Yes, it is totally free and available for all major OS such as Windows, Mac and Chrome OS.

Conclusion

While it is understood that Chrome Remote Desktop is a great application that offers great features for the cost of none.

But if sometimes, Chrome Remote Desktop does not work, you can easily fix it with aforementioned methods to get it back to normal working mode.

• Nothing concrete but some theories.

  Chrome uses QUIC for most of its traffic 443/udp encrypted and authenticated - instead of 443/tcp using HTTPS

  I cannot find a network diagram explaining exactly how this works so following is an ASSUMPTION

  • Remote Host with Chrome Remote Access enabled sitting in branch/office behind a router/firewall.
  • Has constant traffic out to Google or P2P to endpoint
  • UDP in use so stateful firewall may NOT be honouring "return" traffic
  • CONJECTURE - recent changes made in firewalls to fix the Slipstream NAT firewall bypass/pinholing issue MAY be a cause e.g. does QUIC udp have a means of maintaining connection state through a stateful firewall - or is it using the - expect some return traffic on some port to this machine approach that may have gotten sniped in the process of fixing the Slipstream issue?  good writeup on Slipstream here - //www.grc.com/sn/sn-792.htm]
    

  Chrome remote page - //support.google.com/chrome/answer/1649523?hl=en
  

  Spice [2] flagReport
  4 found this helpful thumb_up thumb_down

• I am having this issue as well. I had the first reports on Dec 2nd. I found on the Chrome extension store a user logged a review with the same issue, but until now you are the only other case. I have also uninstalled the Chrome remote desktop host program. When it is reinstalled it only functions for a little while. 

  I was thinking that this had something to do with Google Apps being retired at the end of the month. I can see the Native Messaging ...exe crashing while i am trying to get an endpoint online. I am running Gsuite for education and Trend Micro for AV. 

• Thanks for the follow up.   I completely uninstalled Sophos on one of the affected workstations to no avail.  Same experience... works for a while after uninstall/reinstall, but goes offline after a period of time.   This appears to be Windows specific as a few Mac users have reported no issues.

• I installed the program on my home network and it has been online since last night. I installed CRD version  87.0.4280.58 on Chrome 86.XX from the website in the same manner that I had previously. The Windows PCs on my work network are using CRD version 88.0.4324.9 on Chrome 87.XX. Another new install resulted in CRD version 87 install on Chrome 87. I will monitor, but i bet these installs will update to CRD version 88 and then go offline. 

  I am using a managed browser, I will check the release channels. Maybe there is something in the release notes.

• Appreciate the updates.  I gave up and installed TeamViewer for now on the two workstations that needed access.   We're in the middle of enrolling and distributing 3000 chromebooks ATM, so this one dropped down in priority... ;]

• Tony1216,

  Your situation was exactly the same, In fact, I could have authored your question.  Our daily firewall report began showing an application I had never seen before, QUIC just as Ken had mentioned in an earlier response.  We are using a Watchguard firewall and I simply denied the QUIC protocol in Application Control, and immediately Chrome Remote Desktop came back 'Online' and is staying online.  Phew.