The error appears to be originating from an extension named “ProgrupaTools”. I’m not familiar with that extension, but does the error go away if you disable it?
As @jim_foltz says, your first step should be to disable the progrupa_tools extension and verify that the problem goes away. Then contact the developer to see whether they are aware of the problem and have an update to address it.
The rest of this post is technical - non propellor-beanie types can skip it
The stack trace says that the “progrupa_tools” extension was trying to contact a server to check for updates, and the connection timed out while waiting for the server to provide its SSL capabilities (the “read server hello A” part of the error message). The Ruby code of the extension would block while waiting for this timeout, and the blocked Ruby would block all of SU, causing the slow launch you observed.
That leaves the question of why the connection attempt timed out. I’m skeptical about @DanRathbun’s suggestion that OpenSSL might fail in SU 2017, as it is part of the core Ruby library not something Trimble developed. Also I’d think other extensions would fail if that were the cause. Based on some web research I see that some servers will silently ignore a client request when there is a mismatch between the SSL versions on the client and server, in particular if the client sets SSLv2 and the server wants SSLv3/TLS. Evidently there are man-in-the-middle attacks possible when using the v2 handshake. That’s a matter of setting a parameter in the extension’s use of OpenSSL, and would indicate a failure to keep it consistent with their own server.
Because the Ruby Core SSL library had bugs previously that Thomas is aware of, as (I think) he actually logged a bug in the Ruby Core tracker on it.
SketchUp had to do some non-standard things regarding SSL.
Like adding a “SSL_CERT_FILE” environment variable to SketchUp’s copy of the environment, that points at a SketchUp delivered certificate (.pem file.)
Users of system Ruby can update their installations to a higher patch level to get fixes to libraries (such as the SSL fix,) but with SketchUp it might require an updated application installer.
Anyway, Thomas knows more about it than we all put together.
Looking at the error log I assumed it must have been some built-in SketchUp PROGRam UPgrade Availability check (progr-up-a) checking for program upgrades on the server. Because it couldn’t contact the server it slowed the launch. I started to turn the internet off on my computer before starting SketchUp and it helped.
jim_foltz made me look at the extensions and I turned out however that it was an extension for users using Polish translation and disabling it did the job - Thank You jim_foltz
The version of OpenSSL shipped with Ruby up til version OSSL 1.1 is suffering from performance issues. The issue was resolved in OpenSSL version 1.1 and that was first adopted in Ruby 2.4. This means there are no version of SketchUp at the time of writing that isn’t affected by that OpenSSL performance issue under Windows.
