You can now right click and set the priority.īut that too much work. – remoting_host.exe (the Host Process (32 bits)) – remoting_desktop.exe (the Desktop Integration Process (32 bits)) It will switch you to the Task Manager Details tab. Right click on it and click on “Go to details”. You can check the detail and you will see that the location of those process are something like:Ĭ:\Program Files (x86)\Google\Chrome Remote Desktop\.8 In the Processes tab, they have the names If you don’t see those process in the Task Manager: and changing the priority to high (also with real time) fixed it. I had multiple issues, Chrome remote desktop freezing, Photoshop not refreshing etc. Now I can check my simulations remotely in a matter of seconds… instead of days. Go to Details tab in task manager and set priorities of remoting* executables to High.įor me that worked. Put the remote desktops executables higher on a priority list. If your CPU is busy doing something else (like running a simulation of some sort), it will postpone the processing for… quite a while. Namely, it takes some computing to compress video before it’s sent over the network.
The Culpritīelieve it or not, your CPU might be the cause of slow Chrome Remote Desktop connection. Hopefully this note-to-self can be useful to some other self. But! I found and solved the problems with slow Chrome Remote Desktop.
It would connect with no problems but then it would lag and stutter and most often, just freeze for quote a while. But sometimes it just wouldn’t work as expected. I’ve been using Chrome Remote Desktop quite happily for a while now.
0 kommentar(er)
