Updated the code to support even more output then any existing product key checker (including base 24 decoded value -> base 16 conversion)
Due to the fact that some people can't use the fwscanf_s in the statically linked build ..... all the fwscanf_s has been disabled now and used fwscanf instead! Sorry for any inconvenience caused. Change log : Version 1.0.3b - Fixed some if switch typo in the program - Replaced all the fwscanf_s with fwscanf to temporarily fix the problem
hmmm actually there is a weird situation that the x86 version won't work on x64 OS due to the fact that the secured function (fwscanf_s) only works in native mode (x64 in x64 OS)
:\ So why is every thread about Office 2010 has been moved another sub forum now? :\ And how about this thread?
Dude! it DO NOT work. "Fail to read key" v1.05 Not working... Edit Note: Tried the v1.0.3b and it read key but then it close suddenly....
So seems like fwscanf_s does not work on Windows 7 x86 (however it does work in Windows XP Professional SP3 x86 when I test it in VM) ......... so I decided to remove every fwscanf_s for x86 now ......
Update : Changlog for version 1.0.5a - All the secure function have been removed for the x86 build of version 1.0.5a now so you can use it for validation on x86 computer
Update : Changelog for version 1.0.5b - Fixed 2 typos in version 1.0.5b that makes the version 1.0.5a doesn't work for x86 build
It a PID checker windows and office keys lets you what type they are i,e. OEM: NONE SLP, OEM SLP, MAK, Retail e.c.t if you don't understand what any of these things mean then it is of no good to you.