That seems interesting, but what could we obtain of all of that?? And don't get me wrong, I'm asking because I don't know a thing about that, didn't understand what can we do with all that info. So, if you could explain me it would be very helpful, here or through a PM, it doesn't matter. Thanks in advance
Thanks unknownzd But, with all that info from the pidgenx.dll and the pkeyconfig.xrm-ms what would be the goal? I mean, I don't know if the idea is to be able to just correctly validate keys, or to find a way to bypass the activation, or anything else.
To find the related the public key and hence brute forcing a private key (people has brute forced out the XP private key just in 10 hours using P3, actually that was the way of how XP keygen created) .... and hence finding a OEMBypass key which has never been found before (but well I won't make program into public or here ..... instead I will give out a OEMBypass key once I have found it)
Hopefully at this rate, all this reverse engineering of the code will result in an open source office app by xmas
BETA 4 is two or three things from release. Unless we slip in some new features or uncover major bugs in BETA 4, we are shooting to make BETA 4 the last toolkit release before final. These things are more annoyances than actual bugs, but it is part of us changing the code to WMI.
CODYQX4, you and your partners seem to have done some great work, making activation easier. I just can't get activation to work on my PC. I'm hoping I can get some help with activation. I've read the thread from front to back and tried the various links. Basically I can't seem to get out of the Compatibility Mode. I have this red bar on top of my Office program that says (Product Activation Failed). The thing is I was able to successfully activate using EZActivator. I did run the activator as administrator. I've changed my version of Office 2010 to Volume for Pro Plus. I've tried deleting the license keys and repairing using Office 2010. I've tried a complete uninstall using the MS Office 2010 Fixit tool and MS Office 2007 Fixit tool (because I upgraded from Office 2007) and CCleaner and with Windows Install Clean-up and I've deleted the Registry folders for Office in the HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER and I deleted the Office folders from c:\programs data and c:\program files and still it always goes back into failed Activation mode. Is there something I'm missing? I should note that there were some folders I couldn't delete in the registry. I followed the instructions on a link posted here several posts back, but they didn't work for me. Something about going into permissions and putting a check mark in a box under one of the tabs. Is there something I'm missing or maybe my version of Office is already activated and the red bar is just an inconvenience? I really can't tell at this point?
Right now, you are in notifications mode (nag mode). Reinstalls seem to persist sometimes. Now what version of Office 2010 do you have installed (not converted but physically installed). I recommend if you are going to reinstall to get VL Office (One less step in EZ-Activator), use Stannieman's channel changer to turn Retail to VL installer. When you are in notifications mode, sometimes activation fails every time. You can run toolkit license delete, then repair office (by opening it and letting it do what it needs, repat as necessary, you know it is fully repaired when the nag box and red bar pop back up). Now close office and run EZ-Activator and hope it works. To let you know, BETA 4 EZ-Activator can do some of this without your action (automatic) and much cleaner. The success rate seems to be quite high. Out of everytime EZ-Activator in BETA 4 has run automatic delete and repair, (it reattempts activation again after repair), it has not failed. I have yet for it to fail to activate office after trying all possible remedies. While it could fail, it has not in my extensive testing (Its been a long time for BETA 4) ever failed totally, and even if it does, it can revert your activation state via temporary backup. This is good because if you are in rearm mode before EZ-Activator, you can use a new tool called AutoRearm (As long as you have 2+ rearms). It does not activate office, rather, it takes a backup, rearms on boot if grace < 5 days, and when it runs the rearm count to 0 it restores the backup which gives you all the rearms back AutoRearm used. So, even if activation is a total failure with KMS after all these measures, you have one last resort. Problem with rearm mode is in Retail you get nags, but VL doesn't. You could always convert to VL (You can do this with License Add), then use AutoRearm. So I now have a method to use office except in one condition, EZ-Activator fails and you have less than 2 rearms (Most people try activation before any rearming though).
I totally forgot to say thank you to CODYQX4 and Bosh! +1 for both of you. I still hope one day it will be possible to activate Office 2010 unlimited. Best Regards, kokosmann
The failed activation mode is actually related to the inconsistency between the DigitalProductID and the key that you have used (I have got that a lot of time after using the modified MAK script) Anyway CODYQX4 how do you install the key when its cert is not supported @ all (for example install an MAK key on retail edition)
I had the same problem with ez-activator. I installed Office Pro VL, and had a MAK key, then i formated the HD and reinstalled windows, and the MAK licenses were by then used, so tried ez-activator, and couldnt get it to work. I dont know if it was the version of windows (x64 ultimate HP genuine), or the office version (original VL not converted) or something i was doing wrong. ezactivator would say its activated, but i would start word or excel and same red bar.. I even done a complete windows/office install again. And used the MS office 2010 removal tool too, but always with the same red-bar outcome. Anyways if you manage to get it to work, please let me know exactly what you did.
In EZ-Activator, if you use activated MAK it will leave it alone. If MAK is not activated it will replace with KMS. Also sometimes KMS activation fails. I don't think it has to do with MAK as I've gone back and forth.
Just to let everyone know that the Beta 4 is on it's final revision, probably tomorrow CODYQX4 will upload it. We'll include a list of the "Big Changes", so everyone can know (and enjoy ) the new features and improvements. My sincere Thanks to everyone that has helped us with this tool
hmmm actually it is better to you to dump the output (the last argument) of pidgenx function and apply it to the registry before installing the key ....... you should ask Bosh for that if he has supplied his PID checker for you ..... anyway my PID checker will get open-sourced soon in next week or in this month ...... so you can use it in your program if you want (well if you need me to convert it into C# .... I will try to help to do that after I have released the src code ..... coz I am a bit busy atm, messing around with the public key found in the base64 encoded xml file)