New
#511
Dang, I completely missed the word "retail" in his post. So it's good to know that a clean install won't interfere with the program's ability to extract keys embedded in the BIOS.
Hopefully the other niggles I mentioned can be fixed.
Also there's something I wanted to confirm - keys are checked 100% locally and never sent out, right?
Windows 7 key checking has always been slow...it's just the size of the configuration file that's extremely large - the only way to speed it up would be a more efficient XML search algorithm (rather than node iteration) - BTW the wait cursor should appear during the "Retrieving key..." process.
BTW: A new pre-release to fix some of the issues reported.
https://github.com/Superfly-Inc/Show...howKeyPlus.zipCode:Bug fix: Version check returning null error Exception wording added for valid keys with invalid configuration resulting in a null response for edition.
It does appear, but that doesn't provide any assurance that the program hasn't hung or something. Is adding a progress bar at all possible? I think it would really help improve the end user experience (UX).
Ok, so good news is it's no longer crashing. Bad news is I'm getting the same error on trying to check a key on 32-bit Windows as mentioned in that GitHub issue:
Is it extracting the 64-bit version of the DLL even when running on a 32-bit OS?pidgenx2.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0xc000035a.
Hi C,
Here is an odd one - I am running 10 pro Insider in hyper-v unactivated. and I wanted to get the generic key (to tell somebody how to upgrade to pro without reinstalling), and got the following. The host OS is Windows Pro N, although PC was originally 8 Core (normal) with a bios embedded 8 key.
I was surprised to see the Vista message.
Rgds
M.