Chrome not applying system proxy settings until IE is launched

[CHiLL]

We have noticed a proxy issue with our Windows 10 1709 clients when using Google Chrome (tested on both v61 and v66). Chrome's proxy settings are managed by a GPO to use the system proxy settings. When a student logs into a desktop and launch Chrome, they can access normally blocked (by Smoothwall) content such as games, Youtube and other stuff. Whilst remaining logged on, the student launches IE11, Chrome will then pick up the system proxy settings and apply the filtering as normal.

 

Browsing to chrome://net-internals/#proxy on the machine before IE is launched shows:

Effective proxy settings
Use DIRECT connections.
Source: SYSTEM

 

Browsing to chrome://net-internals/#proxy on the machine after IE is launched shows:

Effective proxy settings
Proxy server: smoothwall.sjw.internal:8080
Bypass list: 
 https://fed.sjw.bham.sch.uk
 10.22.103*
 10.*
 http://*.sjw.internal
 https://*.sjw.internal
 
Source: SYSTEM

 

Internet Explorer's proxy settings are also configured in a GPO, and they are manually specified in User Configuration > Preferences > Control Panel Settings > Internet Settings > Internet Explorer 10 (Students).

 

I am completely baffled as to why Chrome won't pick up the proxy settings unless IE is launched. It should pick them up as per the GPO and use the system settings.

 

Anyone have any ideas?

[thebatman]

We noticed this issue a while back but didn't fined a good answer. What I have done for now as a stop gap is add the proxy settings to Chrome reg settings in GPO.

[ShellfishClive]

The issue lies with internet settings being linked to wininet.dll via Internet Explorer. If you change your proxy settings via GPO this file needs to be "refreshed" in order to work.

 

I've never been able to make a script to do it, I do have a C# full application that does it however it does alot of other things too so I can really share it.

 

I will look late this morning to see if I can make a small script that will do this and I'll post it here.

[TIOAOA]

We experienced something similar - fixed it by setting the chrome policy to point to the proxy instead of system settings

[Primus]

Yup same here - we set it using the Chrome GPO.

[CHiLL]

We experienced something similar - fixed it by setting the chrome policy to point to the proxy instead of system settings

We made this change this morning and it appears to have sorted the issue. Glad it isn't just me that's seeing this issue (even if I am a bit late to the party).