V2.1.1 is live. If the new KMSEmulator by letsgoawayhell is fixed properly (I can't create the condition to test myself) this release should be the death of permanant 80007000D's and therefore License Repair not needed to repair (it still has a use if you want to wipe the slate clean which I do since I test on a live PC different office scenarios).
ZWT KMS Keygen modification explained As you already know we always had that persistent 80007000D problem as an unresolved issue. Sometimes a rearm could solve the problem, some other times a reinstallation and there were even cases that people did not get anywhere with ZWT keygen. Yeah, we always knew that there was a problem in ZWT keygen that prevented the Office from activation. Time passed and Phazor started to develope an activation tool, and along the way he seemed to find the problem in ZWT keygen. But unfortunately he decided to keep it to himself. I got his tool and decomposed in into it's building blocks (i.e. files) and then shared it with you. In order to do so, I used Sysinternal's Process Monitor and Process Explorer to analyze it's behavior. Then I did a memory dump and finally got the files. After sharing it with you, CODYQX4 did a couple of tests on it let me know about them thru PM. In short, we conclude that fx.dat is a modiffied version of ZWT keygen that Phazor believed that can solve the problem. We could have stopped at that stage and just continue to use his tool. But we did not! We wanted to know the secrect. So I compared this file against original ZWT keygen, but almost everything was different! Then I looked into hex values and realized that both files are packed. So I unpacked both of them and then compared them against each other once more. There was little difference between them. Then I hade to check all the differences and decide which one is the important one. It took some time to read some documents on PE(portable Executable) and nail down the important difference. t is something called KMS machine extended PID. The value that is hardcoded into ZWT's keygen is: 55041-00168-305-190595-03-1033-3790.0000-2692009. I think that Phazor came into the conclusion that this ID is the source of the problem and removed it. He did some other modifications but I analyzed them all and the only thing that I my opinion is important is this one. So I took the actual keygen from ZWT and did as little modification as just removing this PID. I am gonna release a v2 in which all messages changes from WINDOWS 7 ... into KMS... coz it is not just limited to windows 7 If it is not as detailed as it should be or screenshots are needed to make it clearer, just let me know! I hope that this can help the community in one way or another coz I believe that each step paves the way for further steps.
KMS machine extended PID BTW, I gonna give you a couple of KMS machine extended PID examples and give you some info that I realized thru my readings. 55041-00168-305-190595-03-1033-3790.0000-2692009 55041-00168-305-246209-03-1033-7600.0000-0522010 55041-00168-305-100667-03-1033-6002.0000-2372009 That blue part of ID seems to mean: KMS Host That brown part seems to mean: Windows version is English That red part seems to be: Windows' Build
I didn't want to start a new thread for this particular inquiry. Has anyone attempted to alter the KMS lease time interval from 180 days? Or, is this not possible because of breaking the KMS licensing system without a way to repair it?
Thanks. I believe it is possible to alter the lease time request interval from every 7 days but wasn't sure if the period for activation to the leased client could be altered.
lease time request interval? 7 days? What are you talking about? Could you please give me a more detailed explanation? Is it sth about KMS asctivation that I am missing?