Chrome remote desktop access windows 10#

This creates an additional security boundary between websites.

When you enable site isolation, content for each open website in the Chrome browser is always rendered in a dedicated process, isolated from other sites. Google’s site isolation feature improves security for Chrome browser users. This is how Google describes the Strict Site Isolation feature in a support page: Chrome already has a built in sandboxing technology and this feature puts even stronger security boundaries between websites than Chrome’s existing sandboxing technology. windows-10-general prevent this you can enable Strict Site Isolation / Strict Origin Isolation on Google Chrome on both host and remote machines. Seeking to see if anyone has experienced this, and hope to get some suggestions on what I could look into to find out why this might be happening.

Chrome remote desktop access windows 10#

All PCs used (both host and remote) are Windows 10 Professional with latest updates, and are on a WorkGroup and not a domain. Only common factor I see is the network VPN configuration. This situation is experienced on multiple PCs, both host and remote. So I feel like using the Chrome Web browser (and Edge) causes the RDP to 'stall'. I then quit the RDP session, and reconnect, and all is OK. I find my RDP access is quite good, and not have issues, but quite often when I open Chrome my session freezes and unable to get any response from the remote PC. I am not 100% certain of this, but this problem appears to occur often when using Chrome or Edge browser on the remote PC I am accessing. I have a LAN to LAN based VPN, and also use a software VPN client on some occasions. I use Remote Desktop to access PCs via a VPN.

Just posting this question as I have been experiencing this problem for some time and waning to see if this is an issue others have come across.