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

The one that works on 64bits doesn't have any features since it was only a test to see if it would run. You will need to wait if you want to use it.

 

Wow this worked really well, I was reading about modifying the Vbox4 bios to activate a windows guest... then came across this. Worked first go and I didn't need to read a whole thread and manually find a slic - and modify my Vbox setup Thanks Phazor!

I've not heard of KMS before (Always used Daz's stuff to activate my Win7 installs 'cos I knew they worked for me)... I activated a Server 2008 VM using your app here. Would the KMS server running on it now be able to 'legitimately' activate my windows 7 clients? That would be nice 'cos the sole purpose of this VM is to serve WSUS, KMS as well would be cool.

Schnap

 

Worked like a charm, thanks!

 

Indeed the Phazor method is working radical on fourth try with notifications and no rearms became activated and 5 rearms. I can now use this to repair rearms for my IORRT

Thanks Phazor

 

flare4000
Thanks. Is there any word on when the x64 version will be ready? I only have a few rearms left

 

You need to login to view this posts content.

 

Phazor
just to let you know I have installed 7601.17514.101119-1850_x64fre_enterprise_en-us_VL_OEM_Enterprise-GRMCENXVOL_EN_DVD.iso
and used ZWT kms emulator alone (since you don't have x64 version ready yet).
the defauly enterprise GVLK is already installed by default of course so I only run:
slmgr.vbs /skms 127.0.0.1
and then open the keygen and run:
slmgr.vbs /ato
still I always got the annonying 0x8007000d error not matter how many times I ask for activation request (slmgr.vbs /ato).
but i fix this problem by setting the host name with the port number 1688:
slmgr.vbs /skms 127.0.0.1:1688
and then slmgr.vbs /ato wprked right away.
and my windows 7 enterprise sp1 x64 is now activated.

 

Tuvi123 -- After many tries (over 100), I was unable to duplicate your results on a virtual test machine. I consistently got the same error code (0x8007000D) that you initially saw. I even reinstalled the OS (same as yours - Win7-SP1 64bit VL OEM Ent) to no avail. Can you think of anything else besides explicitly specifying the port number that might have enabled your success? Btw, I did check in the registry and confirmed that the correct entry for the port number was created after running "slmgr -skms 127.0.0.1:1688" and I'm using the original ZWT emulator that always worked with SP0. So far, it would seem that the only difference between my tests and yours is the machine running them, and I'm using a VMware guest instead of your physical machine. Can you think of anything else you might have done?

 

Hoping for some 64-bit compatible magic...

Phazor -- My only installation of Win7 Enterprise is 64-bit, so I tried running your 32bit-only LocalHost_v1.0 on a 32-bit WinXP VM, hoping to contact your KMS emulator over the network to activate my fresh Win7-SP1 Enterprise installation. Unfortunately, this didn't work because your program stops short of running the KMS emulator when it detects no supported products running locally. Apparently your program must only allow for network activations as long as the local machine is also running a supported product.

If you get the time to change the logic in your program to allow running the KMS emulator on a 32-bit machine even with no supported products running locally, I can easily test whether the emulator is giving out valid activation responses. I even made a snapshot of my Win7-SP1 Ent VM at its virgin installation state (even with no VMware Tools installed) for future tests.

So far, I've had no success (as I already mentioned to Tuvi123) with the original ZWT emulator, which has always worked perfectly on SP0 installations. Interestingly, that emulator also works perfectly on existing SP0 installations (both physical and virtual) that were updated with KB976932 (SP1). It's only a fresh installation from the downloaded integrated SP1 image that seems to have activation issues with the ZWT KMS emulator. I've also tried several subsequent emulators based on that original ZWT release, and none seems able to activate this installation (or an earlier one that I discarded).

I'm stumped, but ready to test any further 64-bit solutions you might have. Thanks very much for your contributions to this community.

 

You need to login to view this posts content.

 

Tuvi123 -- Bingo!!! We have a winner! Something about the sysprep process did something that even a fresh installation from the downloaded integrated DVD image didn't do. The very first activation attempt was successful, with the standard 6-month extension. Subsequent attempts were hit-and-miss, but that has always been the case with this particular KMS emulator.

Thanks a million, Tuvi123. That's the magic I was hoping for

Note to anyone else using this procedure:
Since sysprep.exe isn't on the existing path, just type "sysprep\sysprep" at your administrator command line for Tuvi's Step #1 above, and then check the "generalize" checkbox in the dialog that comes up. Using the "/generalize" argument on the command line didn't seem to make any difference, although I think it would if it were combined with other command line arguments. It worked for me anyway.

 

tuvi123
Is it safe to assume that this method will work for any x64 product providing you use the correct product key?

 

I know it will on any volume edition but Phazor will correct the 64 issue then it will al be automatic again

 

Guppy.In.A.Big.Pond
glad I could help.
gmaslin
as timesurfer said, only on Volume edition (ie enterprise/pro vl/office2010 vl etc..)

 

tuvi123
Used your method on x64 Server 208R2. The "generalize" option was not recognized but the method works without it on my install. Kudos! If this method works for all VLK software, how does the slmgr.vbs know which application the key belongs to?

timesurfer
Your ever present guidance is invaluable to this forum, thanks again.

 

I totally reversed WZT KMS host.

You Got 8007000D Errors for many reason ...

- It emulate RPC but badly ( No RPC Endmapper, only run locally, not manage Request/Response correctly)

- Crypto in WZT KMS host is a "special AES algo" .... Really strange implementation .... Seem that WZT reversed it but strangely.
- This crypto is used to hash the response. At the end of each response, you can found this Hashed stamp. This stamp depend of Request Time, CMID, etc
- So many strange conditional loop in his code that something the hash is not good (01/01/1600 Timestamp in Eventlog)

Job is done but like a Donkey Monkey ...

 

ok so maybe post the code so others can fix it ?

 

To fix it, you need to be able to reverse it. Believe me, it's not so easy to understand & document near from 35000 lines of code

Just take a look with IDA at &01011DE8h in sppsvc.exe ... You will see some friendly AES stuff like in WZT KMS host

 

torjan:Win32/Meredrop
what de hell is this?
my ms sec essentials found a torjan in ur dwnld file