letsgoawayhell man I got another machine with the persistent 0x8000700D error (it's windows 7 pro x64 n en with office 2010 x64). I have installed office/windows on different machines so in order to reproduce the persistent error on another pc. couple of things I noticed so far: *again your modded keygen worked righat away while with zwt original keygen I keep getting 0x8000700D error no matter how many times I try to request activation. *when launching your modded keygen the regular window open and offer me a choice to "Allow" access to it (open 1688 port I guess) but regardless of my choice it still worked (even if I don't click "Allow") with zwt original keygen it does not even open that window to allow access to it. * I have done extensive tests (different windows/office editions/architecture). and just a question- is there a chance that the persistent 0x8000700D error happened more on x64 office with x64 windows? anway here is the Client Machine ID: Code: C:\Windows\system32> cscript "%programfiles%\Microsoft Office\Office14\ospp.vbs" /dcmid Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved. ---Processing-------------------------- --------------------------------------- Client Machine ID (CMID): c65b2273-a4db-420b-a257-4d5772a1f22c --------------------------------------- ---Exiting-----------------------------
Just keep in mind when you "brick" it, it has to be in a state where it could be reactivated. If your license status check (Check Ativation Status) shows nothing, and opening office triggers a repair things are not fixed up. It should show you in Notifications Mode and opening office should give you an activation nag but no kinds of repair/msi dialogs. What you have described I don't think will do much different then my repair, but I'm not sure. I don't see how messing with the PidGenX.dll has anything to do with it.
Thanks for the new tests and the new KMS CMID. That windows pops up when a program is trying to go to "Listening" state. It's a networking concept for a socket connection. Windows firewall pops that message up for NEW programs to give you the option to accept incomming connection (i.e. Unblock). Being new is determined by filename I guess. You added "Keygen.exe" before so you are not being asked again. You can verify that in windows firewall. And it working even without clicking on "Accept" because connections from your own computer (127.0.0.1) do not count as "incomming" connection and hence are not blocked by windows firewall. About x64, I have the same kind of feeling. I think it's because of x64 systems' CMID. I think they are somehow different from x86. Thanks again for all the hard work. They are really appreciated.
I can use as many KMS CMID you guys can provide me with as possible. If people give us KMS CMID and a feedback about whether original keygen or modded one was able to activate their Office, It will be really helpfull.
I found a way to get a lot of KMS CMID's. It is very helpful for test purposes. I am gonna do some tests. Will let you know about it soon. I'll post some info regarding KMS CMID soon. Let me perform some test right now.
Code: C:\Program Files\Microsoft Office\Office14>cscript //nologo OSPP.VBS /dcmid ---Processing-------------------------- --------------------------------------- Client Machine ID (CMID): 64b03639-30d8-4234-bc5d-67369a285a24 --------------------------------------- ---Exiting----------------------------- Persistent 0x8007000D error with Original Keygen. Successfull activation in 2nd attempt with Moddified Keygen v2.
Code: C:\Program Files\Microsoft Office\Office14>cscript //nologo OSPP.VBS /dcmid ---Processing-------------------------- --------------------------------------- Client Machine ID (CMID): 27000e2f-2275-4b33-af5e-07916b885894 --------------------------------------- ---Exiting----------------------------- Activated in 1st attempt with Original Keygen.
Are you by any change bricking+repairing office or using the fact rearming can change CMID? Because you can take a backup via toolkit of you being KMS Activated with 5 rearms, rearm, attempt activation, log the new CMID you get, rearm, reactivate attempt for another CMID, restore backup when out of rearms to reset rearm count, and on and on. It's much faster than a brick/repair. PS: If anyone thinks it would be useful I can add CMID detection to toolkit. It's very trivial to add.
Code: C:\Program Files\Microsoft Office\Office14>cscript //nologo OSPP.VBS /dcmid ---Processing-------------------------- --------------------------------------- Client Machine ID (CMID): 1df0ee30-ba3c-4b29-a156-8f865b73d02e --------------------------------------- ---Exiting----------------------------- Activated in 1st attempt with Original Keygen.
letsgoawayhell actually I did not added Keygen.exe before. I also think it's the x64 systems' CMID (because the persistent 0x8000700D error only happened to me with the 64bit version of office couple of times but never with x86) anyway I may be able to give you yet another CMID from a different system with the persistent 0x8000700D error.
Yes, this is exactly the method that I said. I am using rearming as the method to get new CMID's and reset rearm counts by restoring original tokens and reg keys.
Thanks, that will be really helpfull. I am pretty sure that modded keygen is able to circumvent that persistent error, right?
Code: C:\Program Files\Microsoft Office\Office14>cscript //nologo OSPP.VBS /dcmid ---Processing-------------------------- --------------------------------------- Client Machine ID (CMID): bf2af9e6-f9f1-4e6c-abf3-817ed7f24318 --------------------------------------- ---Exiting----------------------------- Activated in 2nd attempt with original keygen.
Code: C:\Program Files\Microsoft Office\Office14>cscript //nologo OSPP.VBS /dcmid ---Processing-------------------------- --------------------------------------- Client Machine ID (CMID): d396ec88-ab62-4781-b403-673c47f4f439 --------------------------------------- ---Exiting----------------------------- Activated in 3rd attempt with original keygen.
Code: C:\Program Files\Microsoft Office\Office14>cscript //nologo OSPP.VBS /dcmid ---Processing-------------------------- --------------------------------------- Client Machine ID (CMID): e8e9a76a-5ef8-4ab5-ae0c-58822baefa54 --------------------------------------- ---Exiting----------------------------- Activated in 1st attempt with original keygen.
Code: C:\Program Files\Microsoft Office\Office14>cscript //nologo OSPP.VBS /dcmid ---Processing-------------------------- --------------------------------------- Client Machine ID (CMID): 623d4cc5-19db-4659-abd5-0d38820638af --------------------------------------- ---Exiting----------------------------- Activated in 3rd attempt with original keygen.
letsgoawayhell Yes, this is confirmed and I double checked it. I have two machines with the persistent error and with zwt keygen I get the persistent error and with your modded keygen it works on first/second try. (actually on those machines I can't activate office at all with zwt keygen, I can try to rearm and it may help but I don't want to do that since your modded keygen works very well).
I think till now I was able to make some of my ponits about 0x8007000D error clear: It is about your CMID! And YES, rearming can help you most of the times because: rearming force your CMID to change! I'll post more info in the futute.
By that same logic, that is why my nuke and repair technique (which can be used without rearming and rearms are limited) works then right?