Ok, here we go: I had office installed in windows VHD MAK: Uninstalled office and reinstall retail with BBKQ8 key: Formatted VHD install Win7 and office retail with BBKQ8 key: Reinstall office with retail key (not activated): Restored the activation with EZactivator (had made backup a few weeks ago before the format): So after format , ID changes Restoring activation: ID same Uninstall MAK and install retail: different ID
letsgoawayhell I think a rearm is much more easy to change CMID, users have 5 rearms but they can reset it back to 5 whenever they want. waiting for your second part about CMID. CODYQX4 INID is changed. and of course a keygen for phone activation (INID/CID) is possible but require a really talented man to do this. (check a lot of INID's and CID's, check the activation files changes and figure out the algo -hard)
Yeah I know that Keygen would be hard, but all I'm trying to do is find out if somehow we can make the OID persist across a reformat, because someone can replay phone activation indefinitely if they can.
Lemme perfect the idea, we need to see if we can transfer a license from one computer to another. We already have a lot of permenantly activated Office suites around. but the thing is that we don't know how to transfer the license. Maybe if we can figure out a way to force InstID to be sth, then it is possible. But unfortunately my tests say that InstID is not even stored in your computer, it is calculated upon request from your hardware specs. and I am more than capable to force it to change on the fly but I can't force it to be a predefined one.
How did you change it on the fly? I reinstalled Office 2010 and it remained the same. It doesn't seem to be stored in the license store as I can brick and repair that over and over and it remain the same.
I am gonna disagree with you on that. My opinion is that an activation tool should make it's best effort not to use up a user's rearm counts. Simply put I am suggesting to everyone that: 1. Install Office. 2. Make a backup of your office licensing store 3. Try to activate your office with KMS keygen 4. If you don't like your KMS CMID (!!!) for any reason including the reason that it gives you persistent 8007000D error, simply restore your office license store to get new KMS CMID and go for activation. Note: In step 2, backing up the following registry key and restoring it is enough. Code: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OfficeSoftwareProtectionPlatform P.S. : I am gonna post some info why KMS CMID is so important in KMS activation process. And why changing it may let your Office out of that persistent error situation. And by the way guys, the new modded version solved a lot of practical problems and I am really satisfied with it but there is still some theoretical problems that might make your Office persist on that 8007000D error (and I am aware of that!). I am offering a workaround for the worst case scenario that even modded keygen is not able to activate your Office.
No, it is not stored at all. It is calcuated each time on the fly. Use Sysinternal's Process Monitor and then issue the following command and see for yourself how it is being calculated: Code: cscript //nologo "%ProgramFiles%\Microsoft Office\Office14\OSPP.VBS" /dinstid I restrict access to those registry entries and then InstID gets changed. Or I even change those values, it is equaivalent to change a hardware and hence the InstID gets changed.
I don't like using up rearms either, but are you saying restoring a backup is enough to fix the CMID issue? Because what I do in EZ-Activator is take a backup first, attempt activation, and if it fails restore the backup. Thing is, I restore a backup and CMID persists if it is already set, regardless if I restore full backup or just the registry. I test that the CMID is set by office attempting KMS activation, regardless of whether or not a KMS server, real or fake, is accessible. Another thing is even if KMS fails every single time with your fixed Keygen, a real KMS server works one shot without a hitch. I think one thing I can do to try and improve the EZ-Activator is if I force a repair (noting that successful activation will give 5 rearms, so I haven't burned one), take a second backup, since after a repair CMID is not set (though I have to remove the KMS Host so it doesn't attempt activation while repairing and get a CMID). So effectively take a backup of Office 2010 in notifications mode but without a CMID, so I can shoot for a new CMID a few times. ... and about the OID, I am not trying to enable transfer of license to different PC (that would be nice though), but rather to allow the same OID on the same PC, but after a reformat (keeping in mind the HW is the same but a new OID has been calculated), so that I can backup activation by nothing but Phone Activation (though my new backup method is one way to transfer license, a phone activation method would be more clean).
Yes, I read that. You are absolutly right. A legitimate KMS host let you always activate regardless of your KMS CMID. I am aware of that. As I already said I'll make everything clear soon as to why a specific KMS CMID may result in a persistent error with ZWT keygen (sorry I am busy doing some test right now).
The workaround you refer to is the backup/restore, right? Because if so it's already planned to become a new part of EZ-Activator, and I could add it trivially since it's just take a second backup and add a new loop in practice.
On a related note, if the CMID is the be-all end-all of persistent errors, next time I get persistent error, I'm saving backup with CMID intact to help my testing (it's hard to get things when you want it to fail).
Yes, the workaround is: 1. Install an Office (Your KMS CMID in null at this stage) 2. Export "OfficeSoftwareProtectionPlatform" regitry key 3. Issue an activation command. (A KMS CMID is generated in this stage for you) 4. If you don't like your CMID just click on your .reg file and restart ospp service. (Your CMID gets nulled again.) 5. Issue another activation command. (Another KMS CMID is generated for you here.) 6. Goto step 4. Important Note: "osppsvc" needs to be restarted because it only reads "OfficeSoftwareProtectionPlatform" regitry key when it starts.
Using a little batch file and a little patience you can get persistent error. I'll tell you how. Use the above workaround with a little modification. In step 4, try to attemp to activate Office, If it succeds then YOU SHOULD DISLIKE THE CMID and continue to next step. But if it failed you should try to activate again, if it failed say 10 (or whatever you feel like it!) times then you have a persistent error. I am using this technique to get like 1000+ CMID to use them in my test. They are being written in a text file. With current speed I think that I can get 1000+ in like 2-3 hours.
Well yeah, It's been a given in practice anyone doing a backup/restore is supposed to stop/start OSPPSVC as needed. and I'll make a little app for myself to help generate a bad CMID so I can test things better.
Great work man. Definetely valuable to me and everyone else who wans to perform some tests on Office activation processs. I have just a question. Phazor Keygen from toolkit, not fx.dat? Which one do you mean? lhstlnch.exe?