Hello JOO0001's aunt or uncle,
Thank you for your report of the issues experienced with the streaming install and the resolution found by patching _ssl.pyd with a version found in a more recent python. That was definitely very clever. Thankfully, we will be releasing an official fix to this problem later this month, and hopefully no one will have to perform any of these sorts of workarounds any more.
Unfortunately we are not in any better position on the follow-up login error in fusion, and we are still trying to identify a root cause so that we can consider solutions... with little successs.
Your indication that logging in with the Autodesk Desktop app works and lets you proceed to another problem is an interesting one since I believe both Fusion and Autodesk Desktop use a common component to manage authentication, and our diagnostic tool for these sorts of problem appeared to demonstrate the issue as well, however, I will pass that bit on to the developers in charge of the component to see if that gives them any hints.
Beyond that, we know that the sign in is failing because the SSL certificate provided by the host is triggering an invalid signature error on the client during certificate validation. However, we have collected the certificate from failing clients, and it is the same certificate provided to functioning systems everywhere else. Currently, we are pursuing a lead that the failure might be somehow related to Intel's Platform Trust Technology and we need to get hardware that supports this in order to validate. Incidentally, can you confirm or deny that Platform Trust Technology is present and enabled on the system in question?
Steven
