The latest version does not understand CSVLK keys of Windows 8 and Office 2013, you'll update the program?
Any hope of support Office 2007 (and maybe even 2003. [I seen that you said you couldn't find the correct files]) Not that I do not enjoy your program but its not really the ULTIMATE PID Checker with products being unsupported.
Thanks a lot for this useful tool! I couldn't check the activation count for Retail keys (FPP) though. Is there any possibility to check whether a retail key has (and if yes, how often) been already activated? If you call MS, they can tell the date when the key was activated. I guess they use an internal tool, which wasn't leaked? Cheers
Activation count can be determined only for MAK (Volume activation). For other keys, there's simply no such information available (only MS-internally). There's no activation count for Retail keys, because they are only allowed to be used once at a time. Every new activation invalidates the previous one.
Interesting. Current version of TUPC is using pidgenx.dll from Windows 8 which is compatible with all products released after Longhorn 5365 (so it won't work with Office 2007 nor 2003) but I can make it work as a another profile after figuring how the old checking works. EDIT: So these are BRANDING.xml files but I still don't know which dll is used to perform the checking.
Still looking for the following pkeyconfig.xrm-ms files if anyone can help. Exchange Server 2013 SharePoint Server 2013
Whats the maximum amount of keys that can be processed by this tool? I have a 8kb text file with keys on separate lines and the program freezes after the first 30/40 keys. UPDATE I tried again, this time with Office 2010 keys. Was able to process list. Windows 8 keys, it freezes.