Windows 10 Edu 1803 ERR_Connection Timed Out

[stumot]

So we upgraded to Windows 10 a few months back and have had constant problems getting chrome to run as smoothly as it did on our windows 7 machines due to the fact that when users open chrome they are met with the "ERR_CONNECTION_TIMED_OUT" issue, we have updated some machines to 1809 to see if this fixes it, however still we are having this issue , we are using win 10 1803 Education edition and as I have said, some machines have been upgraded to 1809, all the fixes I have seen listed for this are to do with users taking ownership of keys in registry, however this solution is not very easy to implement as I believe it requires users to have elevated permissions in order to perform the registry fix, other browsers (IE and Edge) work stably so we are using them for the time being, but I was just wondering if anyone else is in the same boat with this?

 

p.s We are using the latest version of Chrome (72.0.3626.109)

 

Any ideas or troubleshooting tips would be much appreciated!

Edited February 19, 2019 by stumot

[TechBeard]

Hi

I’m having the exact same issue. I found pushing out a GPO that changes the logon for the Cryptographic Service https://www.google.co.uk/amp/s/www.fixyourbrowser.com/browser/google-chrome/establishing-secure-connection-google-chrome/amp/

Solves the problem BUT breaks things like driver installs and also weirdly stops our antivirus installing, so not an ideal solution.

Did you get any further with it?

 

- - - Updated - - -

 

Hi

I’m having the exact same issue. I found pushing out a GPO that changes the logon for the Cryptographic Service https://www.google.co.uk/amp/s/www.fixyourbrowser.com/browser/google-chrome/establishing-secure-connection-google-chrome/amp/

Solves the problem BUT breaks things like driver installs and also weirdly stops our antivirus installing, so not an ideal solution.

Did you get any further with it?

[stumot]

If I'm honest, I arent 100% but I believe it had something to do with trusted root certificate authorities and disabling them so that they couldn't be used to validate certificates, I believe the Group policy setting for this is in Public Key Policies/Certificate Path Validation Settings/Stores, it appears to have worked for us at the moment at least, hope that helps.