
Because the host is Windows 10 and the VM a Ubuntu or something similar. First of all, when downloading software, the automatic selection for the operating system would no longer work. But in this case I will loose the Endpoint Protection - and at the company it is sometimes good to have a feature like that (my opinion). Because if you close the browser and the policies are set…everything is lost and you need to login at the next startup.

This solution works but is not 100% good. Same as the refresh-button over here: chrome://policy. I’ve written a Windows Service which observes the registry path HKLM\\Software\\Policies\\Google, deletes the Chrome subkey (and all other subentries) if it is there and let Chrome call a Javascript function which refreshes the policies. Solution 1: Observing the Windows Registry Nice, but other Chrome installations are also affected by these policy settings.Īnd now? Using something other than Chrome or Chromium is not an option. Why do they do this? My guess is that they want to customize and secure the Chrome installation which comes through the client management. This is achieved by setting registry keys in: HKLM\\Software\\Policies\\Google\\Chrome And this is the reason for the strange/unknown behaviour of my browser.

So, the IT department can set machine-wide policies for Google Chrome.

I know the Chromium source code very well, but so far I was not familiar of anything about Windows Group-Policies and Google Chrome. So it definitely has something to do with the working environment. That’s not exactly productive and on my private Windows machine I can’t reproduce this behavior. Daily new login with two-factor authentication is a real pain and takes a certain amount of time. However, since a few days I had to find out every morning that I am not logged in on all pages (Google, Github, Stackoverflow, etc.). Initial situation: As a Google fan, I use obviously Google Chrome as my default browser. … the IT department changes Chrome policies so that Chrome becomes unusable or the usual user experience is lost?
