How To Enable Automatic Disconnection from Remote Access on Chrome

So, yeah, usually if you connect remotely through Google Chrome or Chrome Remote Desktop, it stays connected until you decide to disconnect. But sometimes, you forget or just want to make sure it automatically disconnects after a certain time—kind of weird, but I’ve hit that frustration myself. Maybe you’re running a shared computer or just want to avoid accidentally leaving a remote session hanging and eating up bandwidth. Luckily, there’s a way to set a timer so Chrome will auto-disconnect after a set period without you needing to do anything. Turns out, you can configure this either with the Registry Editor or the Group Policy Editor. Both methods basically let you set a maximum session duration in minutes, so it’s a handy tool for keeping things under control.

How to automatically disconnect from remote access on Chrome

Using the Registry Editor is the go-to if you want a quick, low-fuss way. It involves jumping into Windows’ registry and adding a couple of keys. Doing it this way helps because Windows actually stores a lot of policy stuff here, so it’s pretty reliable once you set it up. On the other hand, the Group Policy method is cleaner if you prefer a GUI but only works on Windows Pro or Enterprise editions. On a whim, if things act flaky, sometimes rebooting or even restarting the registry service can help, because Windows is weird about policy changes. Anyway, let’s walk through these two methods.

Method 1: Hack it with Registry Editor

This approach helps if you want a direct tweak that sticks around, especially if you’re comfortable with a little registry editing. It’s good because it applies at the system level and is less prone to accidental resets unless someone clears the registry.

Press Win + R to open the Run dialog.
Type regedit and hit Enter. If it asks for permissions, click Yes.
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies. If you’re applying to just your user, go to HKEY_CURRENT_USER\SOFTWARE\Policies.
Right-click on Policies, select New > Key and name it Google.
Right-click on Google, create another New > Key, and call it Chrome.
Now, inside Chrome, right-click, choose New > DWORD (32-bit) Value and name it RemoteAccessHostMaximumSessionDurationMinutes.
Double-click that new value, select Decimal as base, then input a number—anywhere from 30 (half an hour) up to 10080 (a week)—depending on how long you want the session to last.
Click OK, close the registry editor, and restart (or log out and back in).

That should apply the timeout. Basically, Chrome Remote Desktop or remote sessions will forcibly disconnect after the time you set. Not sure why it works, but on some setups, it might need a restart or even a reboot to kick in properly. In my experience, it sometimes takes a little nudge for the policy to register.

Method 2: Use Group Policy to set max session time

If you’re on Windows 10/11 Pro or Enterprise, Group Policy is a much cleaner way to go. It’s kind of like the GUI version of the registry but more user-friendly. Just be aware that in some editions, this feature is disabled or unavailable, so you’d have to use the registry method in those cases. Anyway, here’s the rundown:

Press Win + R and type gpedit.msc. Hit Enter.
Navigate to Computer Configuration > Administrative Templates > Google Chrome > Remote access. If you don’t see Chrome policies, you might need to download and install Chrome policy templates first from the official Google support pages.
Find and double-click on Maximum session duration allowed for remote access connections.
Set it to Enabled.
Input the number of minutes you want as the maximum session time—anywhere from 30 for a quick timeout, up to 10080 for a week-long session.
Hit OK to save.

This method feels more integrated and less hack-y, but again, only works if your Windows version supports editing policies directly. For home users, the registry tweak is your only real option.

How do I disable remote access altogether?

If you decided you want to just turn it off completely—say, no remote sessions allowed anymore—either go back into the Group Policy Editor or Registry Editor and disable or delete those specific policies/keys. In GP, just set the remote access policy to Not Configured or Disabled. In the registry, remove or set to 0 the RemoteAccessHostMaximumSessionDurationMinutes DWORD. Easy to do, but just make sure to restart Chrome or your PC after changes for them to take effect.

Does Chrome Remote Desktop have a built-in timeout?

Not really. Chrome Remote Desktop doesn’t have a native timeout feature in the settings. The best way to enforce a time limit is via these policy configurations. If you’re just looking for a timer within the app, that’s a no-go—so configuring the max session duration via Group Policy or registry is probably your best bet. Of course, on some setups, applying these settings might require a restart or re-log, but once they’re in, sessions should auto-disconnect after the set minutes. Kinda clunky, but… yeah, that’s Chrome Remote Desktop for you.

Basically, setting a max time is kinda a clever workaround because Chrome itself doesn’t natively have a session timeout option. This way, you can keep things predictable, especially if you’re sharing machines or managing multiple remote sessions.

Summary

Use registry tweaks to set a specific timeout if you’re comfortable editing reg files.
Use Group Policy if you want a GUI option and have the right Windows edition.
Remember to restart Chrome or your PC after making changes for them to take effect.
You can disable remote access entirely through the same paths.
Chrome doesn’t have native timeout options—these policies are the way to go.

Wrap-up

Honestly, it’s a bit annoying that Chrome Remote Desktop doesn’t natively handle session timeouts, especially for folks who just want things to end automatically. But messing around with the registry or Group Policy gives enough control to make it stop before going into full-on “leave it running forever” mode. Just keep in mind, these tweaks are kinda advanced, so save your registry or policies before tinkering. Hopefully, this saves someone a headache—and maybe even some bandwidth or security risks down the line. Fingers crossed this helps make remote sessions a little less open-ended.