Nope, no changes on our side.
Use the latest version, and only after doing that provide enough information so we can help.
TA_E_INET_TLS errors
In the past week we've had probably 5-6 different users contact us receiving error code 36 (TA_E_INET_TLS) when we haven't had issues with this previously. Nothing has changed in our activation code. Any ideas on what could suddenly be causing this? Did you change something on your end recently that could be related to this issue? The only common denominator I've been able to identify between the users is they've all had the issue on their local PC. Note that these same users are able to install on one of their AWS/GC servers and have no issues.
Any help or ideas would be greatly appreciated!
Good to know. Thank you for the quick reply, Wyatt!
I am planning to update to the latest version of TurboActivate with our next update but initial testing (having a user replace their 4.1.8.0 TurboActivate.dll with 4.3.0.0) produced the same error code 36. Once I've had a chance to test the latest version to make sure everything still works I'll release an update to incorporate it. I don't see any script-breaking changes or other "gotchas" for Windows between 4.1.8.0 and 4.3.0.0 in the changelog so hopefully it should be a simple replacement.
I'm crossing my fingers the issue will go away once I've updated TA! If not, I'll try to provide more thorough information.