Glad to hear that.
But I do not find that surprising, as the related bug in the backend servers seems very obvious … and it can reliably be triggered. If the clock is head of UTC, due to the wrong time or the wrong time zone … your requests to some of the server will go to the end of the queue (and might timeout in times of high usage).
I find it more interesting that for some people the time (zone) adjustments will not resolve that “stuck in launch at XYZ” problem. That indicates that there are other issues.
I am pretty sure that a Process Monitor recording can help a lot of identify the cause. However, the files are large (some GB) and so hard(er) to share. If you want to see an example of a “smooth” launch then you can look here: