Universal KMS Activator (KMSA 6.0) Preliminary Tests

I agree. That would work.

The main thing is that there is something that makes it stop once it is obvious that something hinders the activation process.

I would say as a rule of thumb, if it doesnt work after say 10 consecutive requests then there is most likely something wrong with the setup.

The most attemps i ever needed to make was 4 if i remember correctly, however in 99.99% of cases it works 1st or 2nd try, so 10 tries seems to be a reasonable limit.

 

800700D means 'invalid data' and at least with Windows it can and does also occur if the system is still within the 180 days.

I never quite figured out why exactly this particular error happens, but since it goes away eventually i assume it is some momentary data-transmission error in the network.

(Because if Windows cannot establish the connection to the Host at all it says something like "KMS Host not available". This means when 800700D occurs the connection definitely stood, only the data-exchange was somehow incorrect.)

 

One reason why i like this method so much is because there isnt even any hacking involved.

• You install the GVLK that belongs to your edition

• You set the Host Machine Name to your own loopback

• You tell Windows to activate

• The Host tells Windows what it wants to hear and Windows complies


Result: Windows activates itself just like a Retail edition would activate via a Microsoft activation server.

No file patching, no memory patching, no whatever - the system itself stays 100% untouched in every regard.

Simple, clean, genuine, ingenious.

 

Well lets just say it is a 'variation', but yes, ZWTs code is still doing the talking to sppsvc.

(Thats why they are credited in the apps tooltip.)

Considering that somebody else had an access violation related error on a Server edition yesterday, im beginning to think that this is some memory management related issue unique to Servers. Actually im quite certain of that, because the 'cannot find ahost' clearly indicates that something prevents the app from working with its virtual environment which exists only in memory. Unfortunately i dont have any Server editions i could fool around with myself, but i will see if i can find out more and adapt if possible.

But first the question: Did you do anything special to your memory management, you know, like activating some function or feature or using some software i should be aware of? Anything non-standard that makes it differ from Client editions?

 

The app is not supposed to be run under XP.

It is for Vista and higher.

 

Well, i knew it was something with "G"...