Old Windows 7 trouble activation 4.4.4.0Answered
We too were caught off guard on the migration to the newer version of Turboactivate. My fault for not staying current and expecting 8 year old dlls to remain functional. Not a huge problem as we just simply pushed out the DLL, DAT, and Turboactivate.exe files out using wyupdate.
I pushed out the new DLL and files and everything is working great for our Windows 11, 10 and 8 test platforms. However, I am receiving emails from one really old Windows 7 user.
The software is the same and dll calls are the same across the Windows platforms. If you run Turdoactivate.exe manually on the Windows 7 machine, the product returns as activated and successful. However, the internal application code fails to validate, activate or deactivate. Any ideas?
I am not seeing any error trapping on the internal application failed validation checks. I may need to check my code and place more debugging catches. I can try to setup a Windows 7 test platform and maybe catch a failure point.
I setup a Windows 7 Enterprise machine to test. Turboactivate.exe fails to activate. Internal application code fails to activate or validate or remove license.
Turboactivate.exe returns:
Activation Error
A problem occured when XXX tried to activate. Turboactivate failed to connect to the activation servers. etc…
To reiterate, the same internal application code and install files work on Windows 8, 10, and 11.
The Turboactivate.exe activates correctly on Windows 8, 10 and 11.
Turboactivate.dll version 4.4.4.0
Still more information is needed. See the FAQ. Error codes. Functions called. Parameters passed.
Also, Windows 7 is no longer supported by Microsoft. So you’ll need to go out of your way to update the CACerts on the machine.
Help me understand this please.
For testing purposes:
I create a brand new Windows 7 Enterprise install
I download the Turboactivate API from www.wyday.com/limelm/api
I add the Tuirboactivate.dat file from my account page.
I attempt to run the Turboactivate.exe under the /bin-windows/x86 directory.
Attempts to activate a license fail with the “TurboActivate failed to connect to the activation servers” message.
Is this not the gold standard for testing? Should this not always work?
Obvious things like internet connection is good and Windows firewall is disabled.
My list of broken Windows 7 users is growing. Previously they were working. The only change has been new DLLs, 4.4.4.0
I am getting a Windows system error that may be related to the Turboactivate failure. This event log occurs each time I try to activate the license.
“The certificate received from the remote server has either expired or is not yet valid. The SSL connection request has failed. The attached data contains the server certificate”
This would indicate that the turboactivate server is not responding as expected for this certificate request?
Update Windows 7 with all available updates.
Also see above. MS doesn’t support Windows 7.
Look, I understand Windows 7 is dead and I mean long dead. However, I have no control over what OS my users implement. I am obligated to provide services as advertised.
Your product, Turboactivate, is advertised to work with all versions of Windows from Vista to Windows 11.
I now have a population of users who previously had fully functioning software and now have nothing.
What would be great, is that during your testing of Windows 7 and your certification of Windows 7 functionality with Turboactivate, you could point me in a better direction than “Update Windows 7 with all available updates”
Can you tell me which TLS protocol is being used by Turboactivate certificate negotiation? TLS 1.0, TLS 1.1 or TLS 1.2
The specific Windows 7 error is Schannel Event ID: 36881
The specific Windows 7 error is Schannel Event ID: 36888
Currently TLS 1.2.
Like I said above: Update the CACerts. You can do this by applying all updates to Windows 7. Don’t hold any back.
Windows KB3004394 resolved the specific Windows 7 issue.
“Support for urgent Trusted Root updates for Windows Root Certificate Program in Windows”
I would have just run all the possible Windows updates as you suggested, but Windows update was non-functional on this fresh Windows 7 enterprise install until the above update was run. The above update also resolved the cert issue with Turboactivate 4.4.4.0