[UNSUPPORTED] KMS Activator - The Original - Plus 8007000D Unbricker and Anti-AV

Would it be posible the run the activator as a service on machine A (preferable win2k3 as this is my DC and is always on) and activate machine B (win2k8r2) and macine C (win7) over the network?

 

RTM in repo is usually what people use with BIOS mod/Daz loader

 

Good work Phazor.
tx for the tool

I doubt that you know me, but I once used to know stuff about Office 2010 licensing . Back then we believed that ZWT keygen has some faults in it that caused that persistent 8007000D error. Reading this thread, it seems that you found a way to circumvent this deadlock. I am curious to know more technical details.

*Note: Don't get me wrong. We all are greatfull to team ZWT for their wonderfull work.

 

He is keeping it under wraps his "secret"

 

I see. I don't like secrecy but I respect his decision. Maybe I analyse that persistent error myself and then make the solution available to public. I hope I can find enough free time. I think that it is a contribution that someone needs to make.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Secret Revealed

I am sorry guys, I was not able to make my office insist on that 8007000D error, so instead I chose another path.
Just take a look at the following archive. You will know for yourself
Note that there is only one batch file so you know where to start reading. (I know the beginning and the end of the file is a little bit strange, but it is the real thing, this is how it is!)
And also note that [...Moderated.....

 

Is it just a "should" or a "must" Mr. Super Moderator?

P.S. : I thought you guys would be happy. I was trying to help other developers to further improve their activators. I never intended to create a new one.

 

I think timesurfer said it in a friendly way. Furthermore, your help is really appreciated (even though I didn't understand the "trick" that solves the 8007000D in the batch )

PS: We have to see Phazor's opinion on this before going further

 

CODYQX4 is working on it right now, ask him.

 

Good News

OK guys, I think I found the root of the problem in ZWT keygen by analyzing the files in the archive that I posted yesterday.
For now go get some information on KMS machine extended PID. I'll post everything soon. Also I need some guys with persistent 8007000D to test the modded version of ZWT KMS Keygen to see if everything is OK with it or not. I hope this can help us resolve activators' problem.

 

We appreaciate your helpfulness but Phazor isn't having problems with that error which is the thread your in right now...lol

Shouldn't we post these inqueires in say cody's thread

It doesn't really matter just I know cody is one that needs help not Phazor. Phazor has nailed this problem pretty good or am I missing your point you are making?

Respect...

 

You need to login to view this posts content.

 

I have the persistent 8007000D concern with my 64 Bit Windows 7 Enterprise SP1.
The modded version of ZWT KMS Keygen worked perfectly on the second try!
Thank you.

 

Thank you for letting us know. I really like guys like you that gives us feedbacks. Thank you again. I am happy that we are able to help a good guy like you.

 

I've been playing with LocalHost 1 and it definitely works. I wanted to push it a little though, and thus I activated Windows 7 Enterprise with it, and after it was activated I continued on to "Fix Me Mode". This de-activated Windows and actually caused it to generate the 0x8007000D error when I tried to activate it again. I pushed "Fix Me Mode" a second time to see if it would fix it, but failed. Now the Windows 7 Enterprise VM is in a permanent error state of 0x8007000D.

As I said before, LocalHost 1 works perfectly, but I did this to experiment. If Phazor ever decides to release the method, it would be very good to know why this would happen in regards to giving the error and not being able to fix it. I would also be willing to test further "fixes" for this - if this is even needed.