Wyatt O'Day (Wyatt) has made 7770 posts.
We can't reproduce this. Tried on up-to-date Firefox and up-to-date MS Edge (a.k.a. Google Chrome). …
Covered in the FAQ. A hypervisor *is* a virtual machine. That's how it works. It's a ring-0 virtual …
Answer on Feb 8, 2022If you're using the latest TA, and it's says you're in a VM, then you're in a VM. We err on the side…
What version of TFS? What OS? What version, etc., etc., etc.
Or the activation response is invalid. Try again from the beginning: 1. check and save pkey 2. Gen…
Post on Feb 17, 2022Just pass that string in as a literal, rather than converting back and forth between a few different…
Answer on Feb 17, 2022The question is: why can the activation response file can be used more than once? Because the it's …
Post on Feb 17, 2022I'm picking up this thread again as I'm troubleshooting issues related to offline activation. I've…
It's whichever Windows update includes the latest “Let's Encrypt” CaCerts. You'll have to google…
Answer on Feb 14, 2022Apply all updates, including CA cert updates, then enable automatic updates on the computer. https:…
Updating TurboActivate is covered in our FAQ.
Post on Feb 3, 2022Correct. See the constructor for the TurboActivate object in C#: /// <summary>Creates a Turbo…
Post on Feb 3, 2022On MacOs 11.x or later, is the libTurboActivate.dylib already signed by you? No.
Post on Feb 3, 2022What is the parameter uint32_t handle of the TA_IsProductKeyValid() function? the GUID of the licens…
Post on Feb 3, 2022API\C\TurboActivate.h and there was no 10 years gap as you said, v3.3.3 — February 28, 2013 ok…
there's definitely a version of curl in there without runtime linking yeah? Yes.
Answer on Feb 14, 2022Extract the entire static library folder and don’t move or swap out any dependencies. All of them …
My guess if you’re using outdated TA and/or outdated integration files. https://wyday.com/limelm/…
Same answer as before. Showing scams for what they are is currently a lower priority than developin…
Easiest way (as described in the docs): put the DLL in the same directory as the running executable.…