How to Close Google Chrome Remote Desktop Remoting Host.exe

Eric DawsonByEric Dawson Updated Computers & Software

Remoting_host.exe is the background process behind Google Chrome Remote Desktop, and you can close it in under a minute. To close remoting_host.exe temporarily, open Task Manager, find Chrome Remote Desktop Host under Processes, and click End Task. For a fix that survives a restart, open an administrator Command Prompt and run net stop chromoting, or switch the Chrome Remote Desktop Service to Manual in Windows Services so it stops starting on its own. Uninstalling Chrome Remote Desktop Host through Control Panel removes the process for good. Each method below fits a different need, from a quick diagnostic close to a full removal.

What the Chrome Remote Desktop Host Process Does

Google’s Chrome Remote Desktop relies on remoting_host.exe as its core executable, the file that lets you control a computer from another device over the internet. File.info lists the legitimate copy inside C:\Program Files (x86)\Google\Chrome Remote Desktop\, at 73,200 bytes in 21% of occurrences, 72,024 bytes, and 13 additional variants.

This process runs silently in the background, without its own window, and it communicates over the local network or the internet whenever a session is active or listening for one.

Windows does not ship the file itself, but Chrome Remote Desktop cannot accept incoming connections or relay screen and input data without it. Task Manager lists the process as Chrome Remote Desktop Host, and Windows Services lists the matching entry as Chrome Remote Desktop Service.

Why You Might Need to Close Remoting_host.exe

The most common reason to close remoting_host.exe is a software conflict, most often with LockDown Browser, an exam proctoring tool that refuses to launch while any remote access process is running. Southeast Missouri State University’s IT support documentation walks students through exactly this scenario: LockDown Browser checks for remoting_host.exe before it will start, and finds that the check fails until the process is closed.

Diagnostic troubleshooting is the other common reason, since a temporary close through Task Manager lets you test whether Chrome Remote Desktop is interfering with something else before deciding whether to disable or uninstall it for good.

How to Close Google Chrome Remote Desktop Remoting Host EXE

Task Manager offers the fastest way to close remoting_host.exe, though the fix only lasts until the service restarts it.

Steps to End the Task

  1. Open Task Manager: press Ctrl+Shift+Esc, or right-click the taskbar and choose Task Manager.
  2. Go to Processes: click the Processes tab if it is not already open.
  3. Find the host: scroll to Chrome Remote Desktop Host, or a similarly named remoting process.
  4. End the task: right-click the entry and choose End Task.

Why This Is Only Temporary

Ending the task in Task Manager stops remoting_host.exe for the current session only, and the Chrome Remote Desktop Service can start it again the next time Windows boots or the service is triggered. Disconnect from any active remote session through the Chrome Remote Desktop interface before you force the process closed, since an abrupt end can interrupt a session in progress and risk losing unsaved work on the remote side. For a fix that lasts, use the command line method or the Services Manager method described next.

How to Stop Remoting_host.exe with the Net Stop Chromoting Command

Steps to Stop the Service

  1. Open Command Prompt as administrator: search for Command Prompt, right-click it, and choose Run as administrator.
  2. Run the stop command: type net stop chromoting and press Enter.
  3. Wait for confirmation: Command Prompt reports that the Chrome Remote Desktop service has stopped.

Restarting the Service

Typing net start chromoting in the same administrator window brings the service back whenever remote access is needed again. Chromoting is Google’s own name for the protocol that powers Chrome Remote Desktop, which is why the command uses that word instead of the longer service name. Because the underlying service is not disabled by this command, Windows can still start it automatically on the next boot unless the startup type is also changed in Services Manager.

Creating Batch Files to Toggle It on and Off

A pair of batch files turns the command above into a double-click shortcut for anyone who switches Chrome Remote Desktop on and off often. Save a text file as CRD-off.bat containing the lines @echo off and net stop chromoting, and save a second file as CRD-on.bat containing @echo off and net start chromoting. Right-click either file and choose Run as administrator whenever the service needs to toggle, since both commands still need elevated permissions to work.

How to Disable Remoting_host.exe via Services Manager

Setting the Chrome Remote Desktop Service to Manual in Windows Services keeps remoting_host.exe from starting on its own, which is the closest thing to a permanent stop that still leaves the software installed.

Steps in Windows Services

  1. Open Run: press Windows key+R.
  2. Open Services: type services.msc and press Enter.
  3. Find the service: scroll to Chrome Remote Desktop Service.
  4. Change the startup type: double-click the entry and set Startup type to Manual.
  5. Stop it now: click Stop, then click OK to save.

Once the service is stopped and set to Manual, the computer no longer accepts incoming Chrome Remote Desktop connections, and it shows as offline in the Chrome Remote Desktop app on every device that used to reach it. Switching the startup type back to Automatic and clicking Start reverses the change whenever remote access is needed again.

How to Uninstall Chrome Remote Desktop Host Completely

  1. Open the Start menu: click the Start Menu icon.
  2. Search Control Panel: type Control Panel and open it.
  3. Uninstall a program: select Uninstall a program under Programs.
  4. Find the host: locate Chrome Remote Desktop Host in the list.
  5. Remove it: click the entry and select Uninstall.
  6. Restart Windows: reboot the computer once the uninstaller finishes.

Confirming the Removal

Checking C:\Program Files for a leftover Chrome Remote Desktop folder confirms the uninstall actually removed the files, since some installers leave folders behind even after they report success. It is also worth opening the Windows Registry and checking under HKEY_LOCAL_MACHINE\Software for any Chrome Remote Desktop entries the uninstaller missed, though editing the registry by hand carries its own risk and is only worth doing if the folder check turns up leftovers.

What to Do if Remoting_host.exe Keeps Coming Back

Open Services Manager, find Chrome Remote Desktop Service, and check the Startup type column. Automatic means Windows restarts the service on every boot regardless of how many times net stop chromoting or Task Manager closed it before.

Switching that setting to Manual, as, is the step that actually breaks the cycle. If the process reappears immediately after it is ended in Task Manager, open Services Manager again and confirm the Startup type actually saved as Manual, since the change only takes effect once it is applied.

Which Method Closes Remoting_host.exe Best

Task Manager suits a one-time diagnostic close, the command line and Services Manager suit stopping the process for good without removing the software, and uninstalling suits anyone who no longer wants Chrome Remote Desktop at all.

Method Type Permanence Complexity
Task Manager End Task GUI Temporary Low
Command Prompt (net stop chromoting) Command line Temporary Medium
Services Manager GUI Persistent until the service starts again Medium
Browser extension disable GUI Minimal, extension only Low
Uninstall via Control Panel GUI Permanent Medium
Batch file toggle Batch script Temporary Medium to high
Registry or policy control Registry, admin Permanent, organization wide High

Every row above accomplishes the same immediate goal, closing remoting_host.exe, but only uninstalling and the registry and policy route survive an attempt to reinstall the software later. The rest simply wait for someone, or something, to start the service again.

A maker’s PDF manual is my preferred antidote to my tendency to treat a button as a solution and its aftermath as somebody else’s paperwork. For closing remoting_host.exe, “Which Method Closes Remoting_host.exe Best” favors the same restraint: stop the service and set it to Manual for a temporary need, leaving re-enabling simpler than uninstalling.

Is Remoting_host.exe Safe or Could It Be Malware

The same file name is sometimes borrowed by malware planted in Windows system folders, and security researchers flag remoting_host.exe as worth a second look precisely because it transmits and receives network data, which is normal for a remote access tool but also the behavior malware authors like to copy; file.net gives it a “27% dangerous” technical security rating, while file.info says 24% of experts consider it a possible threat. Checking the file’s actual location settles the question fastest.

A copy sitting in C:\Windows or C:\Windows\System32, rather than the Program Files folder, has no legitimate reason to be there and calls for a scan with a security tool right away. The same process sitting inside the Google Chrome Remote Desktop folder, at the file size range, matches what Google actually ships.

Why File Size Alone Cannot Verify Remoting_host.exe

File size alone cannot authenticate remoting_host.exe. Two reference listings both report 73,200 bytes, with file.net listing it as 16% of all occurrences; they assign different occurrence rates and record multiple additional sizes.

Reference listing Reported 73,200-byte frequency Other reported sizes and variants
file.net 16% of all occurrences 74,520 bytes and 23 other variants
Another reference listing 21% of occurrences 72,024 bytes and 13 other variants

Both listings include Windows 11, Windows 10, and Windows 7 reports. The shared 73,200-byte figure therefore identifies a reported size, not a definitive signature for a genuine Chrome Remote Desktop Host Process file.

A 73,200-byte result aligns with reported copies, but the conflicting 16% and 21% figures show that its frequency is not fixed across the two listings. Reported alternatives include 74,520 bytes in one listing and 72,024 bytes in the other, alongside 23 and 13 further variants.

Size checks should not stand alone when assessing a remoting_host.exe file. The comparison shows that more than one reported size exists, while the same reported size appears with different occurrence percentages.

Does Disabling the Extension Stop Remoting_host.exe

No, turning off the Chrome Remote Desktop extension in chrome://extensions/ only removes the browser shortcut for starting and managing sessions.

The remoting_host.exe process is tied to the separate Chrome Remote Desktop Service, so it keeps running until that service is stopped or disabled on its own through one of the methods. Toggling the extension off is a convenient way to hide the feature from the browser toolbar, not a way to close the process running underneath it.

How Organizations Can Block Chrome Remote Desktop with Admin Policies

Organizations can turn Chrome Remote Desktop off for every managed user through the Google Admin Console, without touching each computer by hand.

Setting the RemoteAccessHostFirewallTraversal policy restricts connections to a local network or VPN instead of allowing traversal across the open internet, and on Windows that same restriction is available as the registry key HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\RemoteAccessHostFirewallTraversal set to 0. Blocking the URL remotedesktop-pa.googleapis.com at the network level stops Chrome Remote Desktop functionality outright, and blocking remotedesktop.google.com as well closes the web based entry point too.

Curtain Mode, available on Windows Professional, Enterprise, and Server editions, hides the remote session from anyone standing at the physical screen, which protects privacy during a support session rather than closing the process itself. The RemoteAccessHostMatchUsername policy adds another layer on Mac, Linux, and Chrome devices by requiring the machine to be registered under a matching Google Account.

Frequently Asked Questions

Does Remoting_host.exe Restart After You Run Net Stop Chromoting?

It can, because net stop chromoting stops the running service without changing its startup type. If the Chrome Remote Desktop Service is still set to Automatic, Windows can start it again on the next reboot or when something triggers it. Setting the startup type to Manual in Services Manager, as, is what actually keeps it from coming back on its own.

Will Ending the Task in Task Manager Disconnect an Active Session?

Yes, and it can do so abruptly enough to lose unsaved work on the remote computer. Disconnecting through the Chrome Remote Desktop interface first ends the session cleanly, and only then is closing the process in Task Manager safe. Forcing the task closed while a session is still connected skips that cleanup step entirely.

Does Turning off the Chrome Remote Desktop Extension Stop the Process?

No, disabling the extension only removes the browser shortcut for starting and managing sessions. The remoting_host.exe process keeps running under the Chrome Remote Desktop Service until that service is stopped or disabled separately. Toggling the extension off hides the feature; it does not close the process.

Is Remoting_host.exe a Virus?

Not when it runs from the genuine Google Chrome Remote Desktop folder, though the name gets borrowed by malware often enough to be worth checking. Confirm the file path points to C:\Program Files (x86)\Google\Chrome Remote Desktop\ rather than a Windows system folder before assuming it is safe. A mismatch there is the clearest sign something else is impersonating the real process.

Do You Need an Administrator Account to Close Remoting_host.exe?

Only for the methods that touch the underlying service. Ending the task in Task Manager usually works from a standard account, but the net stop chromoting command, Services Manager changes, and uninstalling the software all require an administrator Command Prompt or an administrator account to complete.

Closing remoting_host.exe comes down to how long the closure needs to last. Task Manager handles a quick diagnostic moment, the net stop chromoting command and Services Manager handle a longer pause without losing the software, and uninstalling through Control Panel handles anyone who is finished with Chrome Remote Desktop for good. Whichever route fits, disconnect any active session first and confirm the file’s location before treating anything found in a Windows system folder as the real thing.

References

Sources read in September 2026.

Eric Dawson

I'm Eric Dawson, and I write The Money Watch from north Columbus, Ohio. Most of what I cover comes from my own life: renting, a 2014 Honda Fit, parking, computers, food and the bills behind all of it. I spent four years in an apartment-property office and eleven on a distributor's operations desk, reading leases and invoices. Where you need real information, I research the maker's or agency's own page and independent sources and report what they publish. I don't give tax, investment, legal or medical advice.