There are several local problems that can cause Chrome to block with ERR_TIMED_OUT during 'Establishing secure connection'.
If stop/start CryptSvc or running IE/Edge before starting Chrome fixes Chrome, then the regedit delete ...Root fix will likely work.
There is a scripted registry repair here, but it requires an admin powershell and turning on execution policy, which is not much simpler than Nover's regedit instructions above. It does have some additional checks and restores built in, so it's a little more robust, but does basically the
same thing. It's my script and will field questions posted there. For more details see the Best Answerat the top of the thread or the Chrome bug CR838707.
The essential part of the fix is deleting ProtectedRoots. It will get rebuilt automatically. Stopping CryptSvc is always temporary. It gets restarted from many places. When it restarts, ProtectedRoots gets rebuilt. I'm not sure deleting Root is needed,
but it gets rebuilt too, so deleting both is safe.
I'm not sure what the root cause is. It seems like it's either the permissions or inheritance of the registry key. Either way it's ok on rebuild. The fix could also be a side effect of the rebuild. The SystemCertificates/Root tree exists in several locations
in the registry, some shadow or inherit from others, so tracking down the real root cause has been elusive. The problem also impacts managed institutional environments and user profiles, in which case the per user fix above it not workable.
I'm not sure why the problem occurs. It happens after a Windows (monthly) update or after a fresh install and update. It only affects isolated users. It's been around since April 2018 (aka 1803) and persists with the 2018 Fall feature update (1809)
This MS community thread is the closest I've come to finding a Microsoft mention of 'this' problem. The Chrome team can't reproduce the problem, so it's not getting any official Google attention.
If you find others, let me know. Maybe if we can get enough attention, we'll see a real fix.
If you have 'this' failure mode, the registry repair is the only fix.